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.
Nginx UI – Access and modify the Nginx configurations files without CLI
21–30 of 61 posts
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#22Weird. 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.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#23NginxProxyManager is the preferred choice in the Unraid (home server) community - good to have another contender to help nginx n00bs like myself.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#24There are also more feature rich control panels:
For some use cases, these can feel bloated, so I understand there could be room for a more minimalistic option.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#25"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.
Solaris had zones, which are similar to LXC or OpenVZ, which Linux had almost as long ago. But neither Solaris zones nor LXC/OpenVZ envisioned the sort of container in which this application is being delivered.
(The key insight here is that "containerization" in the modern sense is about norms/expectations/practices and an ecosystem of tooling around a particular design that's convenient for certain use cases; it's not about a technical facility in the OS.)
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#26Weird. 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.
Always run `nginx -t` before reloading to test the new config.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#27Looks 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?
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#28Is there any security model for this? Or does having access effectively give you complete root control?
Presumably you can set the file root to anything you want.
Maybe do script injection by doing some fancy file loading? Not sure how much nginx config language allows.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#29Earlier quoted context omitted.
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.
Only if you have zero discipline.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#30Looks 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?
I imagine that if you are creating a web interface, with the associated risks it carries (login, vulnerabilities, permissions), the interface should have some advantages over just going into the terminal and editing the same files in the same way.
In fact, by reading the motivation of the project in the README, it seems that the problem it solved was the authentication part of it, and replaced it with... no authentication?