-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey Matteo,
On Sunday 26 Sep 2004 13:04, Matteo Settenvini wrote: > Sure, it's a good idea to remove expecially the "DEPRECATED" section... Yup, it's been in there for about ~6 months at least, send it to sylocon heaven ;-) > as for the rest, I don't know. I explained a possible solution to > Mathieu, which basically used /etc/savannah/hosts.conf just as a table > to point to all the vhost specific configurations (like : I'd strongly disagree with anything more than a global site config touching /etc. Think webapp-config, with virtual host users having access to /var/www/site only - they cannot touch /etc ;-( > /etc/savannah/host0, /etc/savannah/host1, etc). That permitted, in my > view, to have a program "sv_all" in the backend that just iterated over > the table calling the other sv_* programs as needed (for example: > "sv_all --update-conf" does it for each entry of hosts.conf). That would > have simplified crontab entries and system administration with a > catch-all command. It depends I guess on the situation at hand, but with Gentoo, it would be nice, if say a /~user could install a webapp, or an virtual user could install in their /var/www space, or ... :-) > The php "include" in the frontend of savannah.conf.php could have been > determined by looking in hosts.conf for a line matching, e.g. $PHP_SELF > (?). Hmm.. yeah, if this is what your saying: have a site config actualy in the /include/ space? :-) Or just below it.. > The modifications in the configure script to automatically move the > old conf to the new format should've been trivial. *cough* autotools *cough* ;-) We could get most of it down to a 5 line configure.in, a few Makefile.am/in's, and not much manual labour. > Anyway, Mathieu pointed out that the only thing we really need is to set > the right env variable inside apache conf and to modify the crontab > accordingly, and he's afaik right (although i've not had the time to set > up a vhost configuration on my test machine yet). So the only thing left > is to write an ebuild carefully. Yeah, that's one, but in reality there are a few more for different situations with site specific configs, content, etc, etc. If we had more of a framework than a plant in / package, these things will be really easy. Best, Elfyn - -- Elfyn McBratney beu on irc.freenode.net/savannah.[non]gnu.org PGP Key ID: 0x456548B4 PGP Key Fingerprint: 29D5 91BB 8748 7CC9 650F 31FE 6888 0C2A 4565 48B4 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBVrLZaIgMKkVlSLQRAsc6AJ0Y+1cbqHo1ARR8fN8so0bx0Js60QCgoIX0 ne1lXVEASX0D2bLCIDK1RVM= =hj85 -----END PGP SIGNATURE-----
