-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding new parameter for web server base path #1171
Comments
@notFloran : What is the impact of such enhancement in the Web UI code ? |
@nicolargo I don't know, I will try to make a POC and see if that broke something |
@nicolargo We need to update the wiki https://github.com/nicolargo/glances/wiki/Reverse-proxy-to-the-Glances-Web-UI Since the 2.11 :
and
are useless |
Done ! Can you have a look on the Wiki and check that the configuration is fine ? |
For the issue I see the following problem:
So we can have the following setup:
Currently to connect to the server we execute : With the new |
nginx config is ok, for apache I have not tested but it seems ok |
@notFloran completely agree with your last comment. Concerning the Glances 3.0 roadmap, i am not sure that the Restful API will replace the XML/RPC. The bandwidth consumption between a server and a client is *10 between the RPC and the Restful. Before switching, i have to find a way to optimize and reduce the bitrate. |
It would be nice if a parameter existed to specify a web context for glances when it's running as a web server (-w), so that listening URL would be http://localhost:port/context. Something like:
It would make Apache or Nginx configuration much easier when glances must be executed behind a proxy. Right now it's possible to make it work, but it's pretty tricky and doesn't work for everyone.
Thanks a lot for the great work, glances is great!
The text was updated successfully, but these errors were encountered: