Taher Shihadeh dijo [Tue, Apr 01, 2008 at 01:39:16PM +0200]: > Hi Shane. > > 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. > > You'll be using another computer to develop whatever application you > are working on, so this shouldn't be a problem.
Frankly speaking, this seems like a very flawed argument. Cherokee-admin is a nice tool. But denying the user the ability to modify the configuration file on his own, using the same tools he has always used for any other Unixy daemon... Is a big demotivator. The need to use cherokee-admin makes the whole program (even if it is not - even without even looking at it!) seem fragile and Windows-like. Using a helper administrative script should be an option, but not the only way. -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
