I'm using this <a href="https://www.digitalocean.com/community/tools/nginx" rel="nofollow">https://www.digitalocean.com/community/tools/nginx</a> that I find it pretty good
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).
This appears to be a simple UI wrapper over the nginx CLI more than a config generator (like what DigitalOcean has). It's basically an assortment of text boxes for editing the config and then buttons for applying it.
There are also more feature rich control panels:<p><a href="http://ajenti.org/" rel="nofollow">http://ajenti.org/</a><p><a href="http://vestacp.com/" rel="nofollow">http://vestacp.com/</a><p>For some use cases, these can feel bloated, so I understand there could be room for a more minimalistic option.
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.
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.
If you use this, you lose the ability to version control, which is the most important feature of text files.<p>I'm not against generating configuration, but that should not require an always-running instance.
"Containerization is now state of the art and therefore the application is delivered in a container."<p>I wouldn't say it is "state of the art". Solaris had containers in 2004/2005.
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.<p>If anything this tool makes editing easier and may lead to more misconfiguration.
IMHO, 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:<p><pre><code> sudo vi /etc/nginx/...</code></pre>
Neat! Felt a little nostalgic seeing reading the title as it was a somewhat big emphasis as the "next thing to do" when I was part of the NGINX Amplify team.<p>In case you didn't know, the configuration parsing library we created for the NGINX Amplify agent is open source under Apache 2.0:<p><a href="https://github.com/nginxinc/crossplane" rel="nofollow">https://github.com/nginxinc/crossplane</a> (credit to @aluttik who was the primary author)<p>It parses an NGINX configuration files into JSON and vice-versa.
From 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?