Omeka S, the open source platform for publishing digital collections of libraries, archives and museums, serving items, media and public sites over HTTPS from first boot.
This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.
| Product | Cloud | Operating system | Version | |
|---|---|---|---|---|
| Omeka S on Ubuntu 24.04 LTS | Azure | Ubuntu 24.04 | Standard | View · Guide |
Omeka S is a web publishing platform built for galleries, libraries, archives and museums. It keeps one shared collection of items, item sets and media, each described with Dublin Core and other linked data vocabularies such as the Bibliographic Ontology and FOAF, using resource templates your team defines. From that single collection you can build any number of independent public websites, each with its own pages, navigation, theme and selection of items, and every resource is also published through a REST API that speaks JSON LD.
It suits cultural heritage institutions that want their digital collections on infrastructure they control, university libraries and digital humanities projects that run several exhibition sites from one catalogue, and archives that need standards based metadata and an open API rather than a closed hosted service.
cloudimg delivers Omeka S fully installed from the official 4.2.1 release, with Apache 2.4 serving it over HTTPS, PHP 8.3 through PHP FPM on a local socket and a MariaDB database bound to localhost. The Omeka S installer, which creates the first administrator and is open to anyone until it has run, was completed when the image was built and is refused by the web server, so it is never reachable on your VM and there is nothing to set up before you sign in.
Nothing shared ships in the image. Your VM generates its own administrator password, database password and HTTPS certificate on first boot and writes them to a root only file, and the web server stays closed until that finishes. Password reset links always point at the VM's own address rather than a hostname supplied by a browser, uploaded files are stored and served but never executed, and only SSH and HTTPS are reachable from outside. Backed by 24/7 cloudimg support.