Changeset 66 for trunk/README
- Timestamp:
- 04/24/03 18:50:10 (6 years ago)
- Files:
-
- 1 modified
-
trunk/README (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/README
r63 r66 5 5 6 6 - Module::Build for installation 7 - other prerequisite modules as detailed in PREREQUISITES7 - other Perl modules as detailed in the PREREQUISITES file 8 8 - a webserver (such as Apache) 9 - a Postgres database dedicated to the OpenGuides installation 9 - a Postgres or MySQL database dedicated to the OpenGuides installation 10 11 12 13 If while following the instructions below or while trying to use your 14 OpenGuides install you see an error that you don't understand, please 15 consult the TROUBLESHOOTING file. 16 17 10 18 11 19 Unpack the distribution (using for example 'tar' or 'WinZip'), and set … … 20 28 The very first of these commands asks a number of questions regarding 21 29 the installation. 30 31 32 "Skip OpenGuides configuration?" 33 34 Answer "n" to this question unless you really know what you're doing. 35 It's mainly there for developers. 36 37 "what type of database do you want the site to run on? postgres/mysql" 38 39 Answer either "postgres" or "mysql". 22 40 23 41 "What do you want the script to be called?" … … 55 73 optionally install a simple stylesheet with the OpenGuides distribution. 56 74 57 "What's the name of the postgresdatabase that this site runs on?"75 "What's the name of the database that this site runs on?" 58 76 "And the database user that can access that database?" 59 77 "And the password that they use to access the database?" 60 78 61 You should create (or ask your ISP/sysadmin to create) a Postgres 62 database specifically for the use of OpenGuides. If you have more63 than one OpenGuides installation, for example if you run guides for 64 more than one city, each installation will need its own database.79 You should create (or ask your ISP/sysadmin to create) a Postgres or 80 MySQL database specifically for the use of OpenGuides. If you have 81 more than one OpenGuides installation, for example if you run guides 82 for more than one city, each installation will need its own database. 65 83 66 TODO - support MySQL and SQLite as well (this is really going to be67 pretty trivial). 84 TODO - support SQLite as well (requires faffing with install scripts, 85 bit messy but CGI::Wiki already supports this so won't be hard) 68 86 69 87 "What's the wiki called?"
