For reference, I’m sharing here the version I’ve been working on, which has recently been significantly improved through quality pull requests and contributions (all the credits for enhancements really goes to contributors, see all details in the repo).
It is based on some different choices, but it also has a bunch of nice features (e.g. allow for downloading themes and modules via docker compose variables).
Hi Sebastian and Gioco,
I am new to Omeka S and looking to host a production db powering a vite/react frontend in Azur (Omeka) and Cloudflare pages (frontend), and would love to have a chat regarding maintenance of a docker image - hoping to fork an image and leverage your expertise as much as possible. Wondering what the real world maintence requirement has been like over the years, and how best to optimise that process. May I get in touch with you for a call to discuss our project and soak up some of your knowledge?
Congratulations on your Dockerized Omeka S instance. Nice work.
Since we’re all sharing our Docker stacks here, I’m happy to advertise ours as well.
It contains Omeka S, various modules, capabilities for IIIF (including external IIIF-servers) and Solr-powered Advanced Search.
We’re using this Dockerized Omeka S as a local development environment that resembles our production stack. Feel free to check it out and draw inspiration from it.
I would also like to thank @giocomai since our first Dockerized Omeka S was based on his image, which was very insightful and allowed us to make great progress in the beginning. Later on, I’ve decided to rewrite the Docker file etc. from scratch since that allowed for more flexibility and customization to our situation.
Best regards,
Maarten Coonen
Maastricht University Library
p.s. we’re currently in the process of upgrading to Omeka S 4.1.1, so please checkout the branch omeka-upgrade-4.1.x if you need that version.