> El mar, 11-08-2009 a las 11:46 +0200, Alvaro Lopez Ortega escribió: >> No. Cherokee will have no problem what so ever to handle those virtual >> servers. >> >> The only down side would be that the current cherokee-admin interface >> isn't polished to work with such a big list of virtual servers. For >> instance, a search box for live-filtering the virtual server table >> would come really handy in this case. Beside that sort of potential >> GUI improvements, everything is alright. > > Perhaps maybe a list of vservers page by page, with "previous" and > "next" buttons, :-). > > Regards. > > --
<no coffee yet> I guess for this special case would be nice cherokee-central-admin server and servered by the cherokee web server on the cherokee-central-admin, then launch each cherokee with a new parameter -WHATEVERLETTER http://cherokee-central-admin so each cherokee read the config from that server. Then this bing us with a new config for each cherokee so it can read the config from the central server on each change. and for that amount of vservers something like http://lists.octality.com/pipermail/cherokee/2009-January/009600.html but for keep cherokee.conf updated on the cherokee-central-admin </no coffee yet> Saludos Going for coffee .. Leonel _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
