[deleted]
Nginx UI – Access and modify the Nginx configurations files without CLI
11–20 of 61 posts
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#12From what i gather, this is a Deployment & editor software for nginx specifically.
At work I've setup a pipeline using Azure Devops (also done it with Gitlab) that achieves the same thing. And I'm guessing it can be done with the other popular build & deploy tools such as Jenkins and .
So i wonder, who is this for?
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#13I'm using this https://www.digitalocean.com/community/tools/nginx that I find it pretty good
Oh sweet! Didn’t know about this. Would have definitely helped when I was getting my Django app working on DO and was using NGINX for the first time.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#14"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.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#15This 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.
I don't really understand how a tool that enables configuration changes outside of the version controlled loop can improve an IaaC setup. It gives you a shortcut that you may end up taking, making it easier than modifying by hand some configuration via an SSH connection.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#16"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.
"State of the art" doesn't really indicate age. It just means that there's nothing better. I'd be interested in learning about anything that's better than containers.
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#17"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.
"State of the art" doesn't really indicate age. It just means that there's nothing better. I'd be interested in learning about anything that's better than containers.
state of the art
/ˌstād ə(v) T͟Hə ˈärt/
phrase of state
the most recent stage in the development of a product, incorporating the newest ideas and the most up-to-date features.
incorporating the newest ideas and the most up-to-date features.
"a new state-of-the-art hospital"
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#18IMHO, I might as well just use Vim. Maybe this has a use case, it's not for me. I literally need to type just one line and and press enter:
sudo vi /etc/nginx/...Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#19Earlier quoted context omitted.
"State of the art" doesn't really indicate age. It just means that there's nothing better. I'd be interested in learning about anything that's better than containers.
state of the art /ˌstād ə(v) T͟Hə ˈärt/ phrase of state the most recent stage in the development of a product, incorporating the newest ideas and the most up-to-date features. incorporating the newest ideas and the most up-to-date features. "a new state-of-the-art hospital"
newest =/= new
something can be quite old, but if nothing has replaced it, it's still "newest" and "most up-to-date"
Re: Nginx UI – Access and modify the Nginx configurations files without CLI
#20IMHO, I might as well just use Vim. Maybe this has a use case, it's not for me. I literally need to type just one line and and press enter: sudo vi /etc/nginx/...
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.