Sure, it's a good idea to remove expecially the "DEPRECATED" section...
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 : /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. 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 (?). The modifications in the configure script to automatically move the old conf to the new format should've been trivial.
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.
Matteo Elfyn McBratney wrote:
Hello,As part of the Gentoo webapp'isation, it would make life a lot easier if there weren't so many per-site values in these files. I'd like to suggest movingas many of them as possible into a table in the db so they don't requirefilesystem/shell access (think mass virtual hosting with only ftp - no ssh,scp, etc).I think the frontend-only ones could go straight away, but we'd need an easymigration path and access to the old sys_ variables, first. One question: procedural or Oo? ;-) Sound ok for a Savane meets Gentoo branch? Elfyn
_______________________________________________ Savane-dev mailing list [email protected] https://mail.gna.org/listinfo/savane-dev
signature.asc
Description: OpenPGP digital signature
