Changeset 1129 for trunk/INSTALL


Ignore:
Timestamp:
Jan 15, 2008, 12:51:31 AM (14 years ago)
Author:
Earle Martin
Message:

The section about installing into a private directory really belongs in INSTALL, not TROUBLESHOOTING.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/INSTALL

    r1104 r1129  
    88
    99For details about installing multiple OpenGuides sites on a single
    10 server, see further down this file.
     10server, or installing OpenGuides into a directory that isn't where
     11your system Perl library is, see further down this file.
    1112
    1213* Basic installation
     
    217218
    218219This refers to turning titles into links which bring up a list of referring
    219 pages. This was the convention with older wikis, but is not intuitive.
     220pages. This was the convention with older wikis ("C2" refers to the original
     221wiki at http://c2.com/cgi/wiki), but is not intuitive.
    220222
    221223  "Do you have a Google Maps API key to use with this guide?"
     
    394396have to make sure that you fix this up after an upgrade.
    395397
     398* Custom install locations
     399
     400If you wish to install the OpenGuides modules in a private directory,
     401you will need to specify this when you run the Build.PL.
     402
     403If you are using version 0.20 of Module::Build, do:
     404
     405  perl Build.PL install_path=lib=/path/to/my/modules/ \
     406                install_path=script=/path/to/my/bin/ \
     407                install_path=arch=/path/to/my/modules/auto/ \
     408                install_path=libdoc=/path/to/my/man/ \
     409                install_path=bindoc=/path/to/my/man/
     410
     411Or for earlier versions of Module::Build, do:
     412
     413  perl Build.PL config='sitelib=/path/to/my/modules/'
     414
     415If any or all of the modules required by the OpenGuides scripts are in
     416a private directory, then you'll need to tell the scripts where to find
     417them. See the section above about munging in a custom lib path.
     418
     419----------------------------------------------------------------------
     420
     421Important note for those using SQLite:
     422
     423The user your CGI is running as must have write access to not only the
     424database file itself, but the directory that the file is in, in order
     425that it can write a lockfile. If it doesn't have write access to the
     426database file, you'll see errors like "Unhandled error: [DBD::SQLite::db
     427do failed...".
     428
     429----------------------------------------------------------------------
    396430
    397431* Multiple installations
Note: See TracChangeset for help on using the changeset viewer.