Hi Sean, On Tue, Sep 15, 2009 at 02:48:05PM +0200, sean finney wrote: > the way i parsed that, i read "these packages use the 'drop a symlink in > conf.d' method". you'll also see a reply from me in that thread where i > mention a "webapps-common" package, but you'll also notice that that was > something like 2 years (eeks!) ago now. Ah, I did see your reply as well, but somehow wwwconfig-common and webapps-common got merged into the same thing in my brain, which is where the confusion came from. > this was the primary goal of webapps-common (i.e. a parallel to > dbconfig-common). i say "was" because i lost most of my interest in > running this as a pet project on my own and there haven't been any > takers-on for adopting and/or co-maintaining it. there were a couple > folks with some passing level of interest, but maybe once they saw the > (admittedly horrific) code they ran screaming :) > if you're feeling adventurous, you can try the latest webapps-common from > the svn repo (svn://svn.debian.org/svn/webapps-common/webapps-common/trunk), > which is packaged and i believe is "mostly" working, but the quality and > complexity levels are a bit dubious :) there's some documentation shipped > in the package and it works very similar to dbconfig-common if you're > familiar with that. I see... Do you still think that there's a need for webapps-common? Are you still interested? If there were other people interested in getting involved would that re-seed your interest? We have a lot of work to do on the Moodle package at the moment, which may be a good way to re-work on this. I don't really want to adopt it completely myself, but we could switch Moodle over to it as a proof of concept, perhaps, and I could help (and maybe some others on the moodle package team too, although of course I can't volunteer *for them*) > On Tue, Sep 15, 2009 at 01:33:33PM +0200, Penny Leach wrote: > but if you want something that will work right now in unstable, you're > probably best off picking an arbitrary subdirectory name, dropping the > apache conf in /etc/<pkg> and symlinking it to /etc/apache2/conf.d/, no > debconf questions asked (or maybe one: "enable this webapp?"). Yep, definitely dropping into /etc/apache2/conf.d (or better, surely /etc/apache2/sites-available and then sites-enabled) But what about "what url do you want your site to live at" for writing a virtualhost? I don't really like the endpoint being a /webapp directory on the default hostname... and possibly also ServerAliases or redirects (like www.sitename should redirect to sitename (or the other way around)). I can probably get really fancy and think of some other cool options too, like enabling SSL and other stuff, that is overkill right now but some sort of consistent approach could work towards. Cheers, Penny -- /* --------------------------------------------------- Penny Leach | http://mjollnir.org | http://she.geek.nz GPG: 8347 00FC B5BF 6CC0 0FC9 AB90 1875 120A A30E C22B --------------------------------------------------- */
Attachment:
signature.asc
Description: Digital signature