On 28-abr-09, at 19:34, Miguel Angel wrote: > Chris Darnel said: > > The functionality could be similar to the extensions in Firefox where > you click a link to install. > > Wow, simple, but very interesting idea. > +1 for it!! :)
This sort of functionality has been in the To-Do list for a long time now. First time we talked about this idea we named it as 'Cherokee- Admin Wizards support'. If you ask me, I don't think that template system would actually work. In my opinion it underestimate the complexity of the process. Setting up Drupal, GlassFish, Gallery2 or RedMine is fairly simple for a person, but it can be basically be impossible to do with a plain template. Allow me to explain it. Let's take -for instance- Wordpress. The first thing would be to know how the user want it to be installed. Does he want it to be installed inside the /blog directory? Would he prefer it to be installed in a different virtual server: blog.example.com? The set up can differ quite a bit between both scenarios. Besides, we would have to ensure that the current configuration already support PHP, otherwise our auto-magic configuration would fail miserably. And here we have a new challenge: is PHP configured already? There might be a information source but not a "Extension PHP" rule. We'd have to figure it first. In case there weren't an interpreter we would have to look for one: is it installed in /usr/bin, is it in /opt/php, where the heck is it? Aside, is it php or php-cgi? So, my point is.. a template system wouldn't probably scale to handle many of the most common scenarios our users face on a regular basis. IMHO, we ought to implement something slightly smarter, so it can handle fairly complex setups (eventually, we'll have to squeeze all its power). I'd love to know what you guys think of it. Thoughts? Ideas? -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
