Custom Query (298 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 298)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#34 fixed References to trac Earle Martin Dominic Hargreaves
Description

http://openguides.org/page/information could do with a pointer to trac.

#35 fixed Reference to hosting offers Earle Martin Dominic Hargreaves
Description

Somewhere appropriate (maybe http://openguides.org/page/software?) add information on people who are offering openguides hosting for those who cannot run their own installation. Currently I know of crschmidt in the US and me (dom) in the UK who are willing to do this.

#36 duplicate Separate out installation of the OpenGuides software from installing a guide bob Ivor Williams
Description

Currently, the install of OpenGuides is tricky, and doesn't allow a great deal of flexibility:

  • Running more than one guide on the same host
  • Upgrading the software

It is proposed that the install process be split into two distinct steps:

./Build install # install the software, run as root

./Build guide # Ask all the config questions about setting up a guide

# Set up the wiki.conf, CGI and database tables, run as www-data

Thus a CPAN(PLUS) or Debian apt-get install will only install the software, and not any guides. This exact mechanism can be used for software upgrades with the minimum of human effort.

As a side effect, the test suite will need revising, as the answers to the config questions about databases will not be known at this point.

Currently, the test suite is run against all the supported database drivers found (MySQL, pg, SQLite). These are destructive tests that are run against the databases concerned, and could have a devastating effect if run against the real production database.

I propose that instead, there are two options for running the test suite, either minimally via an SQLite throwaway database (the default), or running the tests against the full range of databases on the target machine - a full test. To do this will involve another new build target:

./Build testconfig # probe system for database drivers, and get authentification info

Once testconfig has been run, the test suite will run against all test databases, and the schemae and test data will be torn down on completion, and also at the beginning if the databases appear non-empty.

A full test with testconfig against all database platforms is recommended before shipping releases.

Note, this change will also insist on making DBD::SQLite a prerequisite module.

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.