This repository hosts a Dockerfile for easily deploying Omeka S with Docker. The core idea of these images is that they take care only of Omeka S core: you will need to take care of the config files, modules, and themes.

In order to update, you normally just need to change the tag of the relevant image if you're taking this from Docker Hub, or update the relevant line in the Dockerfile if you build this image yourself.

You can configure the database connection using environment variables instead of editing the database.ini file directly:

Recent versions are available directly from Docker Hub https://hub.docker.com/r/giocomai/omeka-s-docker

Check out the relevant tags. At this stage, the latest Omeka S Omeka S 4.1.1 is kept reasonably updated.

In this repository, you will find also a "docker-compose_traefik_example.yml". Adjust the lines where you find "FIXME" and, after adjusting relevant details in the database.ini file you should be good to go with a deployed Omeka S.

In your omekas volume, you will have a config folder, and inside it a database.ini file.

Its contents should be something along the lines of:

user     = "secretstring"
password = "secretpassword"
dbname   = "secretstring"
host     = "omekas_db"

(obviously, fix these lines with the values you used in your docker-compose.yml)

If you use this in deployment, you'll probably want to have a look also at the local.config.php file in the same folder.

You will also find a "docker-compose_local_example.yml". Adjust the lines where you find "FIXME", update your database.ini as shown above, and you should be good to go with an instance of Omeka S on your local machine at the 172.20.0.1 address.

You can automatically download and install themes by setting the OMEKA_THEMES environment variable. This should contain one or more URLs (one per line) pointing to ZIP files of valid Omeka S themes.

The ZIP archives are expected to contain a single folder at their root (as most Omeka themes do). These folders will be extracted into the themes directory inside your persistent volume.

In your docker-compose.yml:

services:
  omeka:
    image: your-image:latest
    environment:
      OMEKA_THEMES: https://github.com/omeka-s-themes/default/releases/download/v1.9.1/theme-default-v1.9.1.zip

When the container starts, it will:

1. Download the ZIP file from the URL.
2. Extract it into /var/www/html/volume/themes/.
3. Set the proper file permissions.

If the theme is already present in the themes directory, the download will be skipped.

You can also automatically install modules by setting the OMEKA_MODULES environment variable. This should contain one or more URLs (one per line) pointing to ZIP files of valid Omeka S modules.

The ZIP archives are expected to contain a single folder at their root. These folders will be extracted into the modules directory inside your persistent volume.

In your docker-compose.yml:

services:
  omeka:
    image: your-image:latest
    environment:
      OMEKA_MODULES: |
        https://github.com/Daniel-KM/Omeka-S-module-Common/releases/download/3.4.66/Common-3.4.66.zip
        https://github.com/Daniel-KM/Omeka-S-module-EasyAdmin/releases/download/3.4.29/EasyAdmin-3.4.29.zip

At container startup:

1. Each ZIP file will be downloaded.
2. Its contents will be extracted into /var/www/html/volume/modules/.
3. Permissions will be set accordingly.

If a module is already present in the modules directory, the download will still proceed unless you implement further logic for skipping.