/docker-ojs

Open Journal Systems (OJS) is a journal management and publishing system.

Primary LanguageShellGNU General Public License v3.0GPL-3.0

OJS (Open Journal Systems) - PKP - Container/Docker

IMPORTANT:
This repository is still beta, so it should be used with care in production settings - please provide feedback early and often about your experience.
We are actively working to release a stable version soon. Keep tuned.

Open Journal Systems (OJS) is a journal management and publishing system that has been developed by the Public Knowledge Project through its federally funded efforts to expand and improve access to research.

The images in this repository are built on top of Alpine Linux and come in several variants (see Versions).

This repository is a fork of the work formerly done by Lucas Dietrich.

How to use

If you want to run it locally (or in your own server), first you need to install docker (docker-compose is also recommended).

For all available versions, we provide a docker-compose configuration file so you can start an OJS stack (web app + database containers) with a single command.

  1. Clone this repository in your machine (if you don't like git, download and unzip it):

    $ git clone https://github.com/pkp/docker-ojs.git

  2. Go to the directory of your OJS version of your choice:

    $ cd versions/3_2_0-1/alpine/apache/php73
    TIP: Map your config
    In production sites you would like to change the default configuration.
    The recommended way is uncommenting the environment variable sections in your docker-compose.yml and set the environment variables properly.
    More info at "Easy way to change config stuff"

  3. Run the stack:

    $ docker-compose up

    Docker-compose will pull images from docker Hub and do all the hard work to rise a functional OJS stack.

  4. Access http://127.0.0.1:8081 and continue through web installation process.

    Note that the database connection needs the following options:

    • Database driver: mysqli (or "mysql" if your php is lower than 7.3)
    • Host: db (which is the name of the container in the internal Docker network)
    • Username: ojs
    • Password: ojs
    • Database name: ojs
    • Uncheck "Create new database"
    • Uncheck "Beacon"

    And the "Directory for uploads:" acording to your docker-compose "/var/www/files"

    TIP:
    To go through the OJS installation process automatically, set the environment variable OJS_CLI_INSTALL=1, and use the other .env variables to automatize the process.

Building local images

Each version folder also includes has a file called docker-compose-local.yml.

This compose won't ask dockerHub for the required images, it expects you build a docker image locally.

This is useful if you don't want external dependencies or you like to modify our official Dockerfiles to fit your specific needs.

To do this...

  1. Go to your preferred version folder and and build the image as follows:

    $ docker build -t local/ojs:3_2_1-4 .

    If something goes wrong, double-check if you ran the former command with the right version number or in a folder without the local Dockerfile.

  2. Once the image is built, you can run the stack locally telling compose to use the local yaml file with the -f/--file option as follows:

    $ docker-compose --file docker-compose-local.yml up

Versions

Different OJS versions are combined with different versions of PHP (5 and 7), and different web servers (Apache HTTP Server, nginx).

Currently, not all these combinations work! We are mostly focused in Apache2. PR are welcome

All version tags can be found at Docker Hub Tags tab.

(If no webserver is mentioned in the tag, then Apache is used).

Environment Variables

The image understand the following environment variables:

NAME Default Info
SERVERNAME localhost Used to generate httpd.conf and certificate
OJS_CLI_INSTALL 0 Used to install ojs automatically when start container
OJS_DB_HOST db Database host
OJS_DB_USER ojs Database
OJS_DB_PASSWORD ojsPwd Database password
OJS_DB_NAME ojs Database name

Note: OJS_CLI_INSTALL and certificate features are under construction.

Special Volumes

Docker content is efimerous by design, but in some situations you would like to keep some stuff persistent between docker falls (ie: database content, upload files, plugin development...)

By default we include an structure of directories in the version folders (see ./volumes), but they are empty and disabled by default in your compose. To enable them, you only need to uncomment the volume lines in your docker-compose.yml and fill the folders properly.

When you run the docker-compose it will mount the volumes with persistent data and will let you share files from your host with the container.

Host Container Volume Description
./volumes/public ojs /var/www/html/public All public files
./volumes/private ojs /var/www/files All private files (uploads)
./volumes/config/db.charset.conf db /etc/mysql/conf.d/charset.cnf mariaDB config file
./volumes/config/ojs.config.inc.php ojs /var/www/html/config.inc.php OJS config file
./volumes/config/php.custom.ini ojs /usr/local/etc/php/conf.d/custom.ini PHP custom.init
./volumes/config/apache.htaccess ojs /var/www/html/.htaccess Apache2 htaccess
./volumes/logs/app ojs /var/log/apache2 Apache2 Logs
./volumes/logs/db db /var/log/mysql mariaDB Logs
./volumes/db db /var/lib/mysql mariaDB database content
./volumes/migration db /docker-entrypoint-initdb.d DB init folder (with SQLs)
/etc/localtime ojs /etc/localtime Sync clock with the host one.
TBD ojs /etc/ssl/apache2/server.pem SSL crt certificate
TBD ojs /etc/ssl/apache2/server.key SSL key certificate

In this image we use "bind volumes" with relative paths because it will give you a clear view where your data is stored.

The down sides of those volumes is they can not be "named" and docker will store them with an absolute path (that it’s annoying to make stuff portable) but I prefer better control about where data is stored than leave it in docker hands.

This is just an image, so feel free to modify to fit your needs.

You can add your own volumes. For instance, make sense for a plugin developer or a themer to create a volume with his/her work, to keep a persistent copy in the host of the new plugin or theme.

An alternative way of working for developers is working with his/her own local Dockerfile that will be build to pull the plugin for his/her own repository... but this will be significantly slower than the volume method.

Last but not least, those storage folders need to exist with the right permissions before you run your docker-compose or it will fail.

To be sure your volumes have the right permissions, you can run those commands:

$ chown 100:101 ./volumes -R
$ chown 999:999 ./volumes/db -R
$ chown 999:999 ./volumes/logs/db -R

In other words... all the content inside volumes will be owned by apache2 user and group (uid 100 and gid 101 inside the container), execpt for db and logs/db folders that will be owned by mysql user and group (uid and gid 999).

Built in scripts

The Dockerfile includes some scritps at "/usr/local/bin" to facilitate common opperations:

Script Container Description
ojs-run-scheduled ojs Runs "php tools/runScheduledTasks.php". Called by cron every hour.
ojs-cli-install ojs Uses curl to call the ojs install using pre-defined variables.
ojs-pre-start ojs Enforces some config variables and generates a self-signed cert based on ServerName.
ojs-upgrade ojs Runs "php tools/upgrade.php upgrade". (issue when config.inc.php is a volume)
ojs-variable ojs Replaces the variable value in config.inc.php (ie: ojs-variable variable newValue)
ojs-migrate ojs Takes a dump.sql, public and private files from "migration" folder and builds and builds a docker site (beta)

Some of those scripts are still beta, you be careful when you use them.

You can call the scripts outside the container as follows:

$ docker exec -it ojs_app_journalname /usr/local/bin/ojs-variable session_check_ip Off

Upgrading OJS

The update process is easy and straightforward.

  1. Stop the stack with the old OJS version (for instance "pkpofficial/ojs:2_4_8-5").

    $ docker-compose stop

  2. Set the new version in docker-compose.yml.

    Replace the old version: image: pkpofficial/ojs:2_4_5-2

    with the new one: image: pkpofficial/ojs:3_2_1-4

  3. Start the container with the new OJS version. It will pull a new image of your OJS scripts.

    $ docker-compose up

  4. Run the upgrade script to upgrade the OJS database and files. Easiest was is connecting to your OJS container with docker exec and run ojs-upgrade with this single line:

    $ docker exec -it ojs_app_journalname /usr/local/bin/ojs-upgrade
    TIP: Discover your container name?
    You can see the name of all your containers with docker ps -a. The ones related with OJS will be something like ojs_app_journalname.
    Use grep to filter as follows: `$ docker ps -a

Before the upgrade you will like to diff your config.inc.php with the version of the new OJS version to learn about new configuration variables. Be specially carefully with the charsets.

WARNING: May I upgrade directly to the last OJS stable version?
It depends on your initial version. The recommended upgrade route is:
2.x > 2.4.8-5 > 3.1.2-4 > 3.2.1-4 > 3.3.x-x

Apache2

As said, right now the only avaliable stack is Apache2, so configuration files and volumes are thought you will work over an apache.

If you want to know the fastest method to set your own config jump to the next section "Easy way to change config stuff".

For those who like to understand what happens behind the courtains, you need to know that during the image building we ask the Dockerfile to copy the content of ./templates/webServers/apache/phpVersion/root folder in the root of your container.

It means, if you like to add your specific php settings you can do it creating a PHP configuration in ./templates/webServers/php{5,7,73}/conf.d/0-ojs.ini and build you own image locally.

There are some optimized variables already, you can check them within each version directory, e.g. /root/etc/apache2/conf.d/ojs.conf with your virtualhost or /etc/supervisor.conf... or, now you know what Dockerfile will do, you can add your own.

Again: Note that template's /root folder is copied into the Docker image at build time so, if you change it, you must rebuild the image for changes to take effect.

Easy way to change config stuff

If you don't want to keep you own local images, you can use the ones we build in dockerHub and map your config files in your docker-compose.yml.

So if you like to change something in (for instance) your php settings, you only need to created create a ./volumes/config/php.custom.ini outside your container and uncomment the volume in your docker-compose.yml.

Check the volumes section for a list of folders and files we think could be useful to overwrite or extend to fit your needs.

Restful URLs (aka. clean URLs)

By default the restful_url are enabled and Apache is already configured, so there is no need to use index.php over url.

SSL

By default at the start of Apache one script will check if the SSL certificate is valid and its CN matches your SERVERNAME, if don't it will generate a new one. The certificate can be overwritten using a volume mount (see docker-compose.yml file).

Note: This feature is under reveiw and could change in future.

SSL handled by an external service

If you have an external service in front handling SSL connections (often referred as SSL offloading or SSL termination) you need to add a new line containing PassENV HTTPS in ojs.conf, inside the main <VirtualHost *:80> section.

How could I help?

Update the compose configurations and Dockerfiles

If you want to join the docker-ojs (aka. docker4ojs) team you will like to contribute with new Dockerfiles or docker-composes. To do this, you will need to clone this project and send us a PR with your contributions.

Before we follow, let us clarify something: Versions of this project fit with OJS tag versions, BUT... if you take a look to PKP's repositories, you will notice the tag naming syntax changed at version 3.1.2-0. We moved from "ojs-3_1_2-0" to "3_1_2-0".

So, to avoid keeping in mind at what momment we changed the syntax, in this project we only use the modern syntax, so you cant/must refer every version with the same notation.

Said this, let's talk about how we generate all this versions:

The files for the different OJS versions and software stacks are generated based on a number of template files, see directory templates.

You can re-generate all Dockerfile, docker-compose(-local).yml, configuration files, etc. calling the build.sh script.

# generate a specific version
$ ./build.sh 3_1_2-4

# generate _all_ versions
$ ./build.sh

Add a new stack to the list

Let's say we like us to distribute a "nginx" stack. We have our hands full but you know docker and nginx so... ¿how could you contribute?

  1. Be sure the version number is in the versions.list file (ie: 3_2_1-0).

  2. Create the required files and folders in the templates folder.

    Basically you will need:

    • A Dockerfile template for each php version you publish (ie: dockerfile-alpine-nginx-php73.template)
    • A generic docker-compose.yml template (templates/dockerComposes/docker-compose-nginx.template)
    • A folder with all the specific configurations (templates/webServers/nginx/php73/root)
    • Extend exclude.list with the stuff you want to be removed.

    This is the hard work. Take apache as a reference and contact us if you need indications.

  3. Edit build.sh to add your version to the proper variables.

    For the nginx exemple (over alpine) it should be enough extending the webServers array:

    webServers=(  'apache' 'nginx' )

    Modify the script if you need it to be smarter.

  4. Run build script to generate all versions again:

    $ ./build.sh

  5. Test your work running docker-compose with local dockerfiles.

  6. Commit a PR with your new build.sh and templates (ignore the versions folder).

License

GPL3 © PKP