Live data from Hacker News

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

github.com

51–60 of 61 posts

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

#51

Earlier quoted context omitted.

Generally speaking, a UI DOES have a use case - when you can't be bothered to learn the configuration language and its keys / values / nuances. The UI can help you create a sane and safe config, instead of having to scour the internet for - potentially outdated - information. Mind you, I've had more trouble with that with Apache given how they changed their config files around on multiple occasions.

I'd argue that if you are neither willing nor able to learn nginx's config file format, you should not be configuring nginx. The default config has example blocks with comments anyway. If that's not enough, nginx maintains current documentation. But if you're configuring a web server (or anything, for that matter), you should take some time to learn how to configure it.

This. I never understood the "every idiot can do it gui server" thing, just because everybody can doesn't mean everybody should.

Have we already forgotten how Microsoft Exchange singlehandedly launched an entire spam industry?

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

#53

how many cooks does one need in the kitchen, to continuously re-configure a single nginx server? His described use case seems like a strange setup.

And you'd think there'd be some automated pipeline that would deploy and reload nginx configs. That would be usable by all environments, from lab to prod, and would go through code review. A UI anyone can just go in and switch stuff for prod seems like a weird solution to the use case.

Nonetheless they had a problem, they fixed it and they shared the solution when they could've just kept it.

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

#54

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…

Yeah, it's a bit early for this to hit HN.

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

#55
post #46

Earlier quoted context omitted.

I have over 100k uniques daily, 7 servers and I also change nginx config manually via ssh.

But why? Even if you don't use kubernetes or docker images, you do wanna have it in code right? Having something like ansible would do the same thing but allows you to have your config backuped by git and allows you to recreate the env without any issues. How do you keep your mean time to recovery low? How do you document your setup? How do you automated tests if you change your config manual?

Why not?

I have done this for 10+ years and it's still working flawlessly, I don't see a reason to add more complexity to something that is working fine for my needs. I don't have to change config often, maybe once a year or so.

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

#57
post #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 n…

Delivering applications in chroot/jail had some momentum circa 2003. The tooling was on par with current docker if chosen wisely, but surely not on the level of vagrant/docker-compose/docker swarm/kubernetes.

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

#58

10 years young me would have liked having something like this. Nowadays any manual configuration is a big no-no. All my configuration parsing and building happen in the CI pipeline in an automated manner.

It can give beginners a place to start. Until you have that critical base of understanding it can seem very frustrating starting from scratch.

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

#59
post #4

I'm using this https://www.digitalocean.com/community/tools/nginx that I find it pretty good

Nice, I love stuff like this. I can then take the generated files and pull them apart for understanding knowing that they are "working" examples.
Post reply on HN