- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 561
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
Docker container only for UI #234
Comments
Hi, in nginx-ui, we need to execute some commands directly in the same environment with Nginx like to restart or reload it. If using a separate container just for the UI, we cannot control, test config files or get the running status of nginx. |
Could you possibly add the GUI as a Docker mod to the NGINX and SWAG containers? |
bump. this would be useful for those who already are running nginx images and prefer not to switch. I use In case of a different image only for the UI, a form of communication of the UI and the separate nginx would be necessary. I think of shared volumes or network calls. Shared volumes are ok if one only needs to read and write to configuration/log files, not execute commands. I don't know if nginx provides any type of RPCs or APIs for command execution, and even if it does that would pose a security risk. Why having a shared mount between a nginx-ui UI container and a different nginx container is not enough? Maybe the only option is what @schmittyd sugested. |
It would definitely! For example I wan't to use my own Nginx because I need the RTMP module and I can not "build it into" this existing Nginx-UI container. The RTMP module requires Nginx to be build from scratch to include the community RTMP module. #856 |
Is your feature request related to a problem? Please describe.
I want to include just the UI in my Docker compose as I already have a SWAG container which has NGINX, Certbot and php.
Describe the solution you'd like
A separate container just for the UI.
The text was updated successfully, but these errors were encountered: