Hi all,
We are looking at deploying OMP, and with a vital tip shared by MJ Suhonos (PKP), I've been able to verify with a local test deployment of the current OMP:
Presuming path/site structure for your deployment is something like:
URL:
http://omptest.mysite.com/Path: /var/www/omptest.mysite.com/ (Linux) or
Path: C:\wwwdocs\omptest.mysite.com\ (Windows)
1. Check out the omp files from the anonymous PKP CVS repository as per the instructions at:
http://pkp.sfu.ca/ojs_downloadcvs -d :pserver:anonymous@lib-pkp.lib.sfu.ca:/cvs login
cvs -d :pserver:anonymous@lib-pkp.lib.sfu.ca:/cvs co omp
If the contents of the "omp/" folder are below the path, the URL will become:
http://omptest.mysite.com/omp/2. Check out the core PKP libraries
This can be done in several ways, below is one for Linux (and a semi-equivalent for Windows).
* Linux: Check out the core PKP libraries alongside the OMP files and symlink the folder in.
cvs -d :pserver:anonymous@lib-pkp.lib.sfu.ca:/cvs co pkp
ln -s /var/www/omptest.mysite.com/pkp /var/www/omptest.mysite.com/omp/lib/pkp
* Windows: Check out the core PKP libraries inside the "omp/lib" folder.
cd C:\wwwdocs\omptest.mysite.com\omp\lib
cvs -d :pserver:anonymous@lib-pkp.lib.sfu.ca:/cvs co pkp
3. Set the permissions on the "public/", "cache/" and "config.inc.php" files recursively.
* Linux: Presuming your webserver user is "www-data" and the "working user" is "myuser":
# chown -R myuser.www-data /var/www/omptest.mysite.com
# chmod -R g+w /var/www/omptest.mysite.com/public
# chmod -R g+w /var/www/omptest.mysite.com/cache
# chmod g+w /var/www/omptest.mysite.com/config.inc.php
Note that in this scenario, the user "myuser" owns all the files below the web root for the site, which also need to be readable (and directories executable) by the webserver user "www-data".
4. Navigate to the index page of the site and complete the install.
e.g.
http://omptest.mysite.com/index.php--
I've left out an important step with respect to the creation of the database user, but I'd like to add a feature "request" to the ideas forum, regarding the installation form having fields for database administration credentials, so that installation can happen automatically without the need for MySQL/PostgreSQL commandline/querying (provided the installer has the database root permissions and is comfortable putting them into an installation form for software.)
JT.