Why would you want a UI anyway? Unfortunately, to be a web developer,
you will have to have some kind of understanding of a few things like a
server-side language, SQL, webserver configs, javascript, maybe CSS,
etc. A UI is avoiding the problem. If you find the nginx configs to
complicated (and I definitely don't), then maybe the answer is a
suggestion to change the configs for readability, not scriptability.

On 07/05/10 4:09 AM, Ziyad Saeed wrote:
> agree that hierarchy in inf will be ugly.
> you have to be a guru in regular expressions to create a UI for the
> current nginx configuration format. with xml, json yaml etc their are
> plenty of libraries that can read and right them easily.
> Or Nginx can provide an api that i can use to read and write
> nginx.conf files. that's for Igor to decide.
>
>
>
> On Tue, May 4, 2010 at 9:57 PM, Michael Shadle <mike503@gmail.com
> <mailto:mike503@gmail.com>> wrote:
>
> the syntax right now is great. very structured and simple. (my only
> complaint is how location blocks work, partly is syntax and partly is
> just how it works) otherwise i think it is great.
>
> anything can be scripted and anything can have a UI thrown onto it.
>
> i don't see how inf or xml or anything would make it any easier to
> have to make a UI for different location blocks, rewrite rules, other
> complex, and other freeform, non-cookie-cutter kind of configuration
> items.
>
> besides, infs are one-dimensional, creating a hierarchy on that would
> be ugly and hard to read.
>
> On Tue, May 4, 2010 at 3:48 AM, Ziyad Saeed
> <myschizobuddy@gmail.com <mailto:myschizobuddy@gmail.com>> wrote:
> > nginx.conf file in inf format or any other template based format
> would have
> > been the easiest thing to do. perhaps future version of nginx
> can go down
> > this route.
> >
> > On Mon, May 3, 2010 at 9:12 PM, Michael Shadle
> <mike503@gmail.com <mailto:mike503@gmail.com>> wrote:
> >>
> >> I have a php command line script that builds separate conf
> files in one of
> >> my servers and does simple string replacement.
> >> Also remember you can use includes so you can leave the main
> nginx.conf
> >> alone and have it include stuff from another directory you
> write out..
> >>
> >> On May 3, 2010, at 6:24 AM, Luca De Marinis <loop@interact.it
> <mailto:loop@interact.it>> wrote:
> >>
> >> On Mon, May 3, 2010 at 3:07 PM, Ziyad Saeed
> <myschizobuddy@gmail.com <mailto:myschizobuddy@gmail.com>>
> >> wrote:
> >>>
> >>> So I store the configuration in a database or xml file or
> whatever, and
> >>> then generate the conf file from it.
> >>> thank you.
> >>
> >> Also, using a templating system with a scripting language (say,
> erb + ruby
> >> or whatever you're comfortable with) or the good old m4 may be
> viable, and
> >> probably simpler to use and implement. This is very easy and
> very convenient
> >> if you have to generate lots of different configurations (say,
> for n virtual
> >> hosts, or n virtual hosts on n servers) but which all share a
> limited number
> >> of prototype configurations.
> >> Bye
> >>
> >>>
> >>> On Mon, May 3, 2010 at 3:14 AM, Gabriel Evans <me@gabevans.com
> <mailto:me@gabevans.com>> wrote:
> >>>>
> >>>> There's no API that I know of, unless you want to make your
> own module.
> >>>> You could try having a separate directory for virtual hosts
> included and use
> >>>> a database to store and generate the configuration. It'd be a
> lot easier
> >>>> than trying to interpret the configuration as well.
> >>>>
> >>>> On Sun, May 2, 2010 at 4:21 AM, Ziyad Saeed
> <myschizobuddy@gmail.com <mailto:myschizobuddy@gmail.com>>
> >>>> wrote:
> >>>>>
> >>>>> Inorder to make a simple UI for editing nginx.conf. I need a
> way to
> >>>>> edit nginx.conf without having to open it up in a text
> editor. Does nginx
> >>>>> have an api that i can use to edit information that is
> inside nginx.conf.
> >>>>> This will help newbies add virtual host information and edit
> parameters via
> >>>>> a UI.
> >>
> >> _______________________________________________
> >> nginx mailing list
> >> nginx@nginx.org <mailto:nginx@nginx.org>
> >> http://nginx.org/mailman/listinfo/nginx
> >>
> >> _______________________________________________
> >> nginx mailing list
> >> nginx@nginx.org <mailto:nginx@nginx.org>
> >> http://nginx.org/mailman/listinfo/nginx
> >>
> >
> >
> > _______________________________________________
> > nginx mailing list
> > nginx@nginx.org <mailto:nginx@nginx.org>
> > http://nginx.org/mailman/listinfo/nginx
> >
> >
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org <mailto:nginx@nginx.org>
> http://nginx.org/mailman/listinfo/nginx
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx