#36: Separate out installation of the OpenGuides software from installing a guide ------------------------+--------------------------------------------------- Reporter: ivorw | Owner: Type: enhancement | Status: new Priority: normal | Version: 0.51 Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by dom):
Incidentally, my Debian packages have always abstracted guides and the software install. The package sets up a default guide for people but it's easy to add more guides (this is done with a symlink farm when installing as a CGI (ie a symlink to /etc/openguides/$guide/wiki.conf and symlinks to /usr/lib/cgi-bin/openguides/*.cgi from the site's cgi-bin. When mod_perl is [ticket:6 supported] we can just use the OPENGUIDES_CONFIG environment variable (already [changeset:621 supported])).
In my opinion the functionality you describe in ./Build guide should instead be a script - not something that relies on having the source package around. Any user should, given appropriate file permissions, be able to set up a guide.
I've written openguides-setup-db (attached) for this purpose on Debian. It doesn't actually configure it for you but just does the db setup, but this would be a good place to start (renamed openguides-setup or oven ogadm newguide for a more generalised command-line tool).