Live data from Hacker News

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

github.com

31–40 of 61 posts

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

#31

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 tho…

what's the goal of that? Which person needing to configure nginx does not know how to edit text?

Without getting into a debate of whether or not it's a good idea for an inexpert person to be configuring nginx, GUIs can alleviate the need to remember specific terms or syntax, and guide the user through the process in general.

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

#32
post #29

Earlier quoted context omitted.

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

Only if you have zero discipline.

People make mistakes. Relying on people to have perfect discipline and make no errors results in incidents in production.

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

#33

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 tho…

what's the goal of that? Which person needing to configure nginx does not know how to edit text?

If i have to edit text wither way, what's the point of UI?

It's just an extra thing to install, update, maintain and hack.

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

#35

"Containerization is now state of the art and therefore the application is delivered in a container." I wouldn't say it is "state of the art". Solaris had containers in 2004/2005.

Surprised nobody else has mentioned the irony of delivering this - a tool designed to help you hand-edit configuration on a pet server - in a container.

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

#36

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 tho…

what's the goal of that? Which person needing to configure nginx does not know how to edit text?

- better discoverbility of keywords

- less error prone

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

#38
Their user case seems a bit weird to me. If a new application is deployed, can you not make changes to the nginx config locally and redeploy it? That way everyone has access and it'll be part of the usual merge request -> review -> merge flow.

If anything this tool makes editing easier and may lead to more misconfiguration.

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

#39

I just loved it, docker is a good choice but I would've love to have non-docker version as well.

Well, the Dockerfile says exactly how to start the software and how to install all the packages etc. locally, so why not use that? :)

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

#40

Weird. Not sure why i would like to update/change a live config. That would probably not mean that there is an Infrastructure code in git.

Well i have 1M+ users and still ssh into the VMs and live-change nginx configs. Once in a while the reload fails because i messed up something.

And your solutio is to log into a VM through ssh instead of fixing it?

I don't mean this as offending but my personal action is to fix the underlying issue.

If you add more tests etc. you will have to do that less often until it doesn't is the norm anymore.

Post reply on HN