On Tue, 13 Jan 2009 19:04:15 +0100, Alvaro Lopez Ortega
<[email protected]> wrote:
> On 13-ene-09, at 17:32, Gunnar Wolf wrote:
>> Paul Bartell dijo [Tue, Jan 13, 2009 at 06:05:09AM -0800]:
>>> Wow. Or better yet, make a compatibility layer so that people can use
>>> .htaccess files for various url rewirtes etc, without having to have
>>> admin access to the machine. or. giving more than just the admin
>>> access to the web interface. (hosting environment anyone?)
>>
>> Umh... A bit unlikely, I'd venture to say. Cherokee has moved away
>> from the multiple configuration files stand towards a centralized (and
>> centrally managed) configuration file. In any case, this tool would
>> _aid_ a sysadmin into integrating an Apache config file (or a
>> .htaccess file, if Iván considers my idea as meritable) into Cherokee
>> - And quite possibly, the conversion won't be complete.
>>
>> The Apache internals are _way_ different from Cherokee's - And of
>> course, a config file (or config snippet?) convertor will only get you
>> so far.
> 
> I have been working in a "Wizards" functionality for Cherokee admin.  
> It ought to ease the pain for the most common cases. I mean, if you  
> can get the most spread packages set up with a few clicks, most of the  
> people would be simply delighted.

nice!! this script could be easily being migrated to python 

> 
> There is another idea on the same line. If we thought of the current  
> configuration as some sort of Assembler language, some higher level  
> grammar could be built on top of it. Users could deal with very high  
> level primitives (think of some sort of M4) and a translator script  
> could build the final configuration file.  I must say that I have  
> mixed feeling about this, actually. I suppose that people who are  
> working with plain text configuration files would like it, although I  
> still think that cherokee-admin is the way to go.

for most tasks cherokee-admin is the adequate tool, but there are some
cases in which you have to make some batch processing and need to edit the
cherokee.conf file directly. 
I personally don't like M4 for configuring files that are readable it adds
another layer of complexity to something that should be inherently simple.
I would like to have wizards and batch processing tools.



> 
> --
> Octality
> http://www.octality.com/
> 
> _______________________________________________
> Cherokee mailing list
> [email protected]
> http://lists.octality.com/listinfo/cherokee

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to