Hello,

Few months ago I started to explore the possibility to write a higher level
python API : https://bitbucket.org/yml/cherokee-admin-api
I wrote a bit about this experience :
* http://gwadeloop.com/blog/gwadeloop/archive/2010/05/20/cherokee-admin-api/
*
http://gwadeloop.com/blog/gwadeloop/archive/2010/06/08/cherokee-admin-api-part2/

I stop this effort because I found this approach to be  fragile.

Regards,
--yml


On Sat, Dec 18, 2010 at 9:35 AM, Alvaro Lopez Ortega <[email protected]>wrote:

> On 18/12/2010, at 00:49, Patrick Breitenbach wrote:
>
> > I see a lot of notices to avoid manually editing the Cherokee
> configuration file and instead use the GUI. However, it's frequently
> necessary to script a deployment (shell script, fabric, etc) so I'm
> wondering if anyone has best practices for that?
>
> As far as I'm aware of, the best choice so far is the Config.py parser we
> use on Cherokee-admin:
>
>  http://svn.cherokee-project.com/browser/CTK/trunk/CTK/Config.py
>
> --
> 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