-
Notifications
You must be signed in to change notification settings - Fork 197
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
web interface for administration #149
Comments
The command library used to talk to the proxy is here: https://github.com/sozu-proxy/sozu/tree/master/command You need to open the unix socket used for communication with sozu, then the messages are sent as JSON objects separated by a null character. The |
What kind of informations we need to display on this interface? |
a lot of things that are not there right now, like the number of concurrent connections, the requests per second, the bandwidth. It could also display the actual configuration (domains, certificates, backend servers, etc). |
Hello, I started to explore sozu today, and this might be a good issue for me to start contributing. Just to be clear I would do this on my spare time and I still have a lot to learn so I might take me some time. They are many framework out there. I've started to experiment with nickel, iron, actix and rocket but I 've no idea yet about which one would fit the best (pick one). Although I need clarification about what i required here exactly. What you need is a restfull API to perform the command already available via sozuctl, not writing the UI, right ? |
this could be integrated in sozu's main process now. I'm not sure integrating a large web framework would be the key here, a simple status page for now would be enough |
the
sozuctl
command line can already be used to manage the proxy, but administration through a web interface could be useful.The command library should be easy enough to plug in a separate application with a web API built with rocket or something else.
The text was updated successfully, but these errors were encountered: