Live data from Hacker News

Nginx UI – Access and modify the Nginx configurations files without CLI

github.com

1–10 of 61 posts

Re: Nginx UI – Access and modify the Nginx configurations files without CLI

#2
This is certainly a good effort but I've yet to use a web ui to manage web server configs, especially these days when we're moving most of the configuration to code and version control. We usually deploy changes to a test server to test the changes and then move on to production.

Re: Nginx UI – Access and modify the Nginx configurations files without CLI

#3
post #2

This is certainly a good effort but I've yet to use a web ui to manage web server configs, especially these days when we're moving most of the configuration to code and version control. We usually deploy changes to a test server to test the changes and then move on to production.

Adding a UI doesn’t require you to take config out of your IaaC setup, it could Increase accessibility to logs, monitoring, security warnings, versioning, etc, that your IaaC might be strongly lacking. There are weaknesses to IaaC that a tool like this may supplement.

Re: Nginx UI – Access and modify the Nginx configurations files without CLI

#6
Looks basically like a web-based text-editor. More effort needs to be put into adding UI controls for modifying common settings, or at least some macros for adding settings to a config file. (e.g. insert a common setting at cursor location). Better yet, hide editing the config file in an "advanced" mode, and allow UI controls (checkboxes, input boxes, and dropdowns) for editing parts of the config. (that's what I thought this was going to be).

Re: Nginx UI – Access and modify the Nginx configurations files without CLI

#10
post #3
post #2

This is certainly a good effort but I've yet to use a web ui to manage web server configs, especially these days when we're moving most of the configuration to code and version control. We usually deploy changes to a test server to test the changes and then move on to production.

Adding a UI doesn’t require you to take config out of your IaaC setup, it could Increase accessibility to logs, monitoring, security warnings, versioning, etc, that your IaaC might be strongly lacking. There are weaknesses to IaaC that a tool like this may supplement.

That’s true if the UI is a read-only dashboard. If the UI can affect behavior then you don’t have IaaC anymore.
Post reply on HN