Suggesting to improve the configuration

[GoogleCodeExporter]

Dear Cherokee Team,

I might be totally wrong but I believe that the structure of cherokee.conf
is not clever. I would suggest you to separate the virtual host
configuration into separate files. Additionally, I believe that it would be
better to drop the incremental number in the config file (ex vserver!10!...
vserver!20!...) and let Cherokee manage these numbering by itself.

At the present, maintaining a large amount of vhosts is very very time
consuming if it has to be done by cherokee-admin or by hand using
cherokee's current vhost config scheme. Just as most other ISP we are using
some perl scripts which manage the addition, removal and changes of vhosts
automatically. Generally most webservers follow the same kind of config
structure, so it was very easy to port our scripts (ex ISPCP or CPanel) to
nginx or lighty but Cherokee makes it very difficult.

Yes, it's possible to include config files from a whole directory, but a
script has to pay attention to the number, make sure a number doesn't get
generated twice, and so on.

Using the current config structure it's also impossible to include a config
file on per vhost basis. include = /etc/cherokee/advanced.conf is fine but
it will apply to the whole server. Something like vserver!10!include =
/etc/cherokee/advanced.conf is unfortunately not possible. As a result,
rules that may apply to 1000 vhosts cannot be included as a single file but
it has to be copied 1000 times. That's aweful.

Thank you.

Original issue reported on code.google.com by nlublov...@gmail.com on 26 Nov 2008 at 7:45

[GoogleCodeExporter]

Agreed, we talked about this on the mailing list. I think Cherokee config 
should be
based on nested tags (xmlish) or stanzas (INI). The best I think would be to 
use an
existing format: http://www.yaml.org/, and additionally admin should 
fully-support
includes, possibly imposing some structure on includes such as requiring each 
vhost
to live in a separate file such as $CHEROKEE_CONF_ROOT/vhosts.d/vhostname.conf

Original comment by ericd...@gmail.com on 1 Feb 2009 at 3:10

[GoogleCodeExporter]

this would be indeed very helpful. I am writing a deployment script at the 
moment and
to generate the vhost entries is quite a pain in the a**!

Original comment by lauber.p...@gmail.com on 23 Apr 2010 at 8:59

[GoogleCodeExporter]

see 
http://www.reddit.com/r/programming/comments/a6p93/any_reason_the_webserver_cher
okee_i
snt_more/c0g3lw0 for a (valid I think) critique of Cherokee's conf format.

Original comment by ericd...@gmail.com on 23 Apr 2010 at 5:02