Nothing you should not be familiar with
Installation
------------
Please review this document and the RELEASE document prior to installing OJS.
If you encounter problems, please also see the FAQ document in this directory.
To install OJS:
1. Extract the OJS archive to the desired location in your web
documents directory.
2. Make the following files and directories (and their contents)
writeable (i.e., by changing the owner or permissions with chown or
chmod):
* config.inc.php (optional -- if not writable you will be prompted
to manually overwrite this file during installation)
* public
* cache
* cache/t_cache
* cache/t_config
* cache/t_compile
* cache/_db
3. Create a directory to store uploaded files (submission files, etc.)
and make this directory writeable. It is recommended that this
directory be placed in a non-web-accessible location (or otherwise
protected from direct access, such as via .htaccess rules).
4. Open a web browser to <http://yourdomain.com/path/to/ojs/> and
follow the on-screen installation instructions.
Alternatively, the command-line installer can be used instead by
running the command "php tools/install.php" from your OJS directory.
(Note: with the CLI installer you may need to chown/chmod the public
and uploaded files directories after installation, if the Apache
user is different from the user running the tool.)
The installer also offers a "manual installation" option that will
display the SQL statements necessary to create the OJS database but
not execute them.
5. Recommended additional steps post-installation:
* Review config.inc.php for additional configuration settings
* Review the FAQ document for frequently asked technical and
server configuration questions.
A secure deployment can be best achieved by using the following policies:
* Dedicate a database to OJS; use unique credentials to access it.
Configure this database to perform automated backups on a regular
basis. Perform a manual backup when upgrading or performing
maintenance.
* Configure OJS (config.inc.php) to use SHA1 hashing rather than MD5.
* Configure OJS (config.inc.php) to use force_ssl_login so that
authenticated users communicate with the server via HTTPS.
* Install OJS so that the files directory is NOT a subdirectory of
the OJS installation and cannot be accessed directly via the web
server. Restrict file permissions as much as possible. Automated
backups of this directory should be roughly synchronized with
database backups.
http://pkp.sfu.ca/ojs/README
OJS in one hour
http://pkp.sfu.ca/files/OJSinanHour.pdf
edit;We are going to have filled up the recent posts section at this rate!
There is a working demonstration of it at;
http://pkp.sfu.ca/ojs/demo/present/
Installation
------------
Please review this document and the RELEASE document prior to installing OJS.
If you encounter problems, please also see the FAQ document in this directory.
To install OJS:
1. Extract the OJS archive to the desired location in your web
documents directory.
2. Make the following files and directories (and their contents)
writeable (i.e., by changing the owner or permissions with chown or
chmod):
* config.inc.php (optional -- if not writable you will be prompted
to manually overwrite this file during installation)
* public
* cache
* cache/t_cache
* cache/t_config
* cache/t_compile
* cache/_db
3. Create a directory to store uploaded files (submission files, etc.)
and make this directory writeable. It is recommended that this
directory be placed in a non-web-accessible location (or otherwise
protected from direct access, such as via .htaccess rules).
4. Open a web browser to <http://yourdomain.com/path/to/ojs/> and
follow the on-screen installation instructions.
Alternatively, the command-line installer can be used instead by
running the command "php tools/install.php" from your OJS directory.
(Note: with the CLI installer you may need to chown/chmod the public
and uploaded files directories after installation, if the Apache
user is different from the user running the tool.)
The installer also offers a "manual installation" option that will
display the SQL statements necessary to create the OJS database but
not execute them.
5. Recommended additional steps post-installation:
* Review config.inc.php for additional configuration settings
* Review the FAQ document for frequently asked technical and
server configuration questions.
A secure deployment can be best achieved by using the following policies:
* Dedicate a database to OJS; use unique credentials to access it.
Configure this database to perform automated backups on a regular
basis. Perform a manual backup when upgrading or performing
maintenance.
* Configure OJS (config.inc.php) to use SHA1 hashing rather than MD5.
* Configure OJS (config.inc.php) to use force_ssl_login so that
authenticated users communicate with the server via HTTPS.
* Install OJS so that the files directory is NOT a subdirectory of
the OJS installation and cannot be accessed directly via the web
server. Restrict file permissions as much as possible. Automated
backups of this directory should be roughly synchronized with
database backups.
http://pkp.sfu.ca/ojs/README
OJS in one hour
http://pkp.sfu.ca/files/OJSinanHour.pdf
edit;We are going to have filled up the recent posts section at this rate!
There is a working demonstration of it at;
http://pkp.sfu.ca/ojs/demo/present/