On 01 Apr 2008, Nikolai Kondrashov escribiówrote: > > 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.
Agreed. When I said 'minimal environments' y meant 'embedded environments', not 'minimal configuration'. cherokee-admin is new since release 0.6, so it figures any shortcomings will be solved/enhanced. For example a few days back, thanks to a question sent to this list, Alvaro noticed that the number of threads wasn't managed through cherokee-admin. He sumbitted changes to cherokee-admin the same day. I don't remember right now if it's allready in 0.6.1, but I'm quite sure I've seen the modification in SVN. We do monitor whatever is said here. Don't hesitate to ask for improvements. > 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. Well... there is always the info provided at http://www.cherokee-project.com/doc/internal_configuration.html Documentation, however, could and should always be improved. Work in progress there ;) > Of course providing a possibility for hard-coded configuration would satisfy > our needs, but, having possibility to generate the configuration file is > much nicer. I don't think I quite understood you here, sorry. If by generating the config file you mean having nicer documentation on the internal format, what is this hard-coded configuration you talk about: using cherokee-admin as is, improving some missing features...? Regards, Taher -- [EMAIL PROTECTED] http://unixwars.com _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
