On 11-jul-09, at 07:42, Ayron Jungren wrote: > I remember having issues with this from switching to Cherokee. I > volunteer to write a Python mod_rewrite-to-Cherokee translater/lexer/ > compiler/whatever you want to call it/etc. that integrates with > cherokee-admin.
First of all, allow me to make it clear: Cherokee will not support Apache configuration files. Having said that, I'd like to say that I'm *all* for integrating a converter (as long as it works well enough). So, any effort of writing one is more than welcome. :-) Personally, I think that's the best option: It'd allow to make migrations easier (which of course is a very interesting feature) and the same time that it would not make Cherokee depend on a configuration format that is neither user-friendly nor easily machine- readable (and that would basically make cherokee-admin imposible). > On Sat, Jul 11, 2009 at 1:22 AM, Anoop Alias > <[email protected]> wrote: > > I second that. > > The one big thing that would lead to the adoption of cherokee in the > mass hosting market would be an apache compatible rewrite rule parser. > > The Litespeed web server had a tremendous adoption rate because it > was apache compatible -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
