Hi Nikolai,
Right now, cherokee-admin reads, and generates the file cherokee.conf at
/etc/cherokee/
It's a plain text config file with a simple formatting designed to be fast
and simple to parse.
I paste here an snippet of my config for you to see how does it look like:
[---------------------------------------------------------------------]
vserver!leemelo.com!directory!/icons!handler!theme = firefox3
vserver!leemelo.com!directory!/icons!handler!user = 0
vserver!leemelo.com!directory!/icons!handler!date = 1
vserver!leemelo.com!directory!/icons!handler!size = 1
vserver!leemelo.com!directory!/icons!document_root =
/usr/share/cherokee/icons/
vserver!leemelo.com!directory!/!priority = 4
vserver!leemelo.com!directory!/!only_secure = 0
vserver!leemelo.com!directory!/!handler = scgi
vserver!leemelo.com!directory!/!handler!error_handler = 0
vserver!leemelo.com!directory!/!handler!check_file = 0
vserver!leemelo.com!directory!/!handler!pass_req_headers = 0
vserver!leemelo.com!directory!/!handler!balancer = round_robin
vserver!leemelo.com!directory!/!handler!balancer!1!interpreter =
/sites/leemelo.com/www.leemelo.com/leemelo/scgi.sh
vserver!leemelo.com!directory!/!handler!balancer!1!host = localhost:3033
vserver!leemelo.com!directory!/!handler!balancer!type = interpreter
vserver!leemelo.com!directory!/!document_root =
/sites/leemelo.com/www.leemelo.com/
[--------------------------------------------------------------------------]
2008/4/1, Nikolai Kondrashov <[EMAIL PROTECTED]>:
>
> Taher Shihadeh wrote:
> > The idea behind cherokee-admin is that it should always be an option
> to
> > avoid the configuration hassle. For minimal environments
> cherokee-admin
> > should be used on another machine and then copy the resulting
> > configuration file to the embedded device.
>
> I agree, but there should also be an option to have as complex
> configuration
> as needed.
>
>
> > You'll be using another computer to develop whatever application you
> are
> > working on, so this shouldn't be a problem.
>
> OK, what about automatically-generated configuration? Our project, for
> instance, allows specifying Web-server listening port through our
> management
> interface (which allows configuring a huge amount of other things, also),
> which is currently done by processing environment variables in
> read_config_embedded.c.
>
> We will need the ability to configure other Web-server parameters, very
> probably, which could easily be accomplished through a configuration file
> generation both at run time and at build time. And without proper
> configuration file documentation I will need to dig into source code.
>
> Of course providing a possibility for hard-coded configuration would
> satisfy
> our needs, but, having possibility to generate the configuration file is
> much nicer.
>
> Sincerely,
> Nick
>
> _______________________________________________
> Cherokee mailing list
> [email protected]
> http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
>
_______________________________________________
Cherokee mailing list
[email protected]
http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
