Omeka, verified and packaged by Elestio
7.6K
OMEKA Open-source web publishing platforms for sharing digital collections and creating media-rich online exhibits.
Deploy a fully managed omeka on elest.io if you want automated backups, reverse proxy with SSL termination, firewall, automated OS & Software updates, and a team of Linux experts and open source enthusiasts to ensure your services are always safe, and functional.
Before starting your Docker Compose stack, make sure to complete the following steps:
Create the necessary directory for files:
mkdir -p ./files
Set the appropriate permissions:
chmod -R 777 ./files
Create the database configuration file:
nano ./config/database.ini
Add the following content to the file:
user = "root"
password = "your-strong-password"
dbname = "omeka"
host = "db"
port = "3306"
;unix_socket =
;log_path =
Save and close the file.
Here are some example snippets to help you get started creating a container.
version: "3.3"
services:
omeka:
image: elestio/omeka:${SOFTWARE_VERSION_TAG}
restart: always
ports:
- "172.17.0.1:9543:80"
volumes:
- ./files:/var/www/html/omeka-s/files
- ./config/database.ini:/var/www/html/omeka-s/config/database.ini
db:
image: elestio/mysql:8.0
restart: always
ports:
- "172.17.0.1:12832:3306"
environment:
- MYSQL_DATABASE=${DB_NAME}
- MYSQL_ROOT_PASSWORD=${DB_PASSWORD}
volumes:
- ./mysql:/var/lib/mysql
pma:
image: elestio/phpmyadmin:latest
restart: always
links:
- db:db
ports:
- "172.17.0.1:38557:80"
environment:
PMA_HOST: db
PMA_PORT: 3306
PMA_USER: ${DB_USER}
PMA_PASSWORD: ${DB_PASSWORD}
UPLOAD_LIMIT: 500M
MYSQL_USERNAME: ${DB_USER}
MYSQL_ROOT_PASSWORD: ${DB_PASSWORD}
depends_on:
- db
| Variable | Value (example) |
|---|---|
| SOFTWARE_VERSION_TAG | latest |
| ADMIN_EMAIL | [email protected] |
| ADMIN_PASSWORD | your-strong-password |
| DB_USER | root |
| DB_PASSWORD | your-strong-password |
| DB_NAME | omeka |
| DB_HOST | db |
| DB_PORT | 3306 |
You can access the Web UI at: http://your-domain:9543
The Elestio omeka Docker image sends the container logs to stdout. To view the logs, you can use the following command:
docker-compose logs -f
To stop the stack you can use the following command:
docker-compose down
To make backup and restore operations easier, we are using folder volume mounts. You can simply stop your stack with docker-compose down, then backup all the files and subfolders in the folder near the docker-compose.yml file.
Creating a ZIP Archive For example, if you want to create a ZIP archive, navigate to the folder where you have your docker-compose.yml file and use this command:
zip -r myarchive.zip .
Restoring from ZIP Archive To restore from a ZIP archive, unzip the archive into the original folder using the following command:
unzip myarchive.zip -d /path/to/original/folder
Starting Your Stack Once your backup is complete, you can start your stack again with the following command:
docker-compose up -d
That's it! With these simple steps, you can easily backup and restore your data volumes using Docker Compose.
Content type
Image
Digest
sha256:1d4e1c026…
Size
4.5 GB
Last updated
4 months ago
docker pull elestio/omekaPulls:
5
Last week