Repository navigation
Releases
v2.7.3 — Typesense runs as an unprivileged user
Upgrading from v2.7.1 or v2.7.2 (only if you run the
searchprofile). Typesense now runs as uid 10002. Hand the existing root-owned volume over once, then start the new image:git fetch --tags && git checkout v2.7.3 docker compose --profile search build --pull typesense docker compose stop typesense docker compose --profile search run --rm --no-deps --user 0 --cap-add CHOWN \ --entrypoint chown typesense -R 10002:10002 /data docker compose --profile search up -d typesenseIf you skip the
chown, Typesense can't write its data directory and won't become healthy. The search index is kept.
Security
- Typesense runs as an unprivileged user (
typesense, 10002:10002) instead of upstream's root. This closes the DS-0002 finding raised against the Dockerfile added in v2.7.2. A freshtypesense_datavolume gets the right owner automatically.
v2.7.1 to v2.7.3 cleared every finding from the weekly scan (#60) that has an upstream fix. These are still open:
- mysql 9.7.4: 3 critical, 33 high and 67 medium, in the Go stdlib and Python packages bundled with the official image. No fixed image has been published yet.
- ckeditor4 4.20.1 (4 medium): ships with Omeka S core.
v2.7.2 — Typesense with Ubuntu security updates (#60)
Upgrading from v2.7.1: build the Typesense image (only if you run the
searchprofile).git fetch --tags && git checkout v2.7.2 docker compose --profile search build --pull typesense docker compose --profile search up -d typesenseThe search index is kept on its volume. Search is unavailable for a few seconds while Typesense restarts.
Security
- Typesense now has current Ubuntu security updates. Upstream doesn't rebuild Typesense images between releases, so 30.2 still shipped openssl
3.0.2-0ubuntu1.23and apt2.4.14. The weekly scan flagged 6 high and about 129 medium vulnerabilities in them. The new_docker/typesense/Dockerfilebuilds the same digest-pinned 30.2 release and addsapt-get upgrade. The image now has openssl3.0.2-0ubuntu1.30and apt2.4.15ubuntu0.1. The Typesense binary, entrypoint and user are unchanged.
Changed
docker-compose.yml: thetypesenseservice now builds from_docker/typesenseinstead of pulling the image directly.- CI checks that this build is in place and that its base image is pinned by digest.
- Dependabot now tracks the Typesense version in
/_docker/typesense.
Still open
- mysql 9.7.4: the outdated components are bundled in the official image (Go stdlib, and Python packages from MySQL Shell). No fixed image has been published yet.
- ckeditor4 4.20.1: ships with Omeka S core. Fixed CKEditor 4 versions are only available under a paid LTS licence.
v2.7.1 — patched container images (#60)
Upgrading from v2.7.0: rebuild the code images and the SPARQL image.
git fetch --tags && git checkout v2.7.1 docker compose build --pull php web sparql && docker compose up -d php web sparqlIf modules live on Docker volumes (the default), the rebuild doesn't change the
Common module that is already deployed. Patch it in place:docker compose exec php sh -c 'cd /var/www/html/modules/Common && composer update symfony/yaml --with "symfony/yaml:~5.4.54" --no-dev --no-interaction --optimize-autoloader'Data volumes are kept. php, web and sparql restart briefly.
Security
This release fixes the vulnerabilities in the weekly image scan (#60) that have an upstream fix.
- web: nginx
1.30.6-alpinenow uses the refreshed digest (brotli 1.2.1 fixes the critical CVE-2026-111497; also curl 8.23.0 and expat 2.10.0). The stage now runsapk upgrade, which installs libxslt 1.1.43-r4 and zlib 1.4. - sparql: the image runs
apt-get upgrade, which installs zlib1g1:1.3.dfsg+really1.3.1-1+deb13u1beforedebian:trixie-slimis rebuilt upstream. - php / web: the new
_docker/vendor-security-floors.txtraises a vendored PHP package when a module release ships it at a vulnerable version. Common 3.4.96 ships symfony/yaml 5.4.53. It is raised to 5.4.56, which fixes CVE-2026-109413.- Running
scripts/update-extensions.shreinstalls Common from its release zip, which puts 5.4.53 back. Run the composer command above again until Common ships a fixed lock.
- Running
Still open (no upstream fix yet)
- mysql 9.7.4: the Go stdlib and Python packages bundled with MySQL Shell are outdated. The newest image is still 9.7.4, with the same digest.
- typesense 30.2: the outdated Ubuntu openssl and apt packages are in the base image. The only newer releases are 31.0 release candidates.
Also since v2.7.0
- amira-mcp default pin v1.38.1 (was v1.37.0). Curator mode searches private texts, and curator notes on private material now inform the user instead of refusing. Public mode is unchanged.
- The deployed module releases are pinned: DRESearch v1.37.0, DRE-Visualizations v2.55.1, DRE-theme v2.50.1.
- The curator MCP and README docs are up to date.
v2.7.0 — curator MCP endpoint, API keys redacted from logs, refreshed AMIRA extensions
Upgrading from v2.6.x. No image rebuild is needed. Restart
webso the
new access-log format applies, then refresh the AMIRA extensions and the MCP
server:git fetch --tags && git checkout v2.7.0 docker compose restart web bash scripts/update-extensions.sh # AMIRA: modules and theme bash deploy/amira/update-amira-mcp.sh v1.37.0Data volumes are kept. The curator endpoint below is opt-in and stays off
unless you enable thecuratorprofile.
New
- Curator MCP endpoint (AMIRA, optional) at
/curator/mcp(#55). It runs
the same amira-mcp-server withAMIRA_ACCESS=curator: it crawls the Omeka
API with a service key, so it also sees private records, and serves them only
to curators holding a personal token. It is switched on with thecurator
profile, and is pinned on its own throughAMIRA_MCP_CURATOR_VERSION. Setup:
deploy/amira/README.md#curator-mcp-endpoint.- Its memory ceiling is
AMIRA_CURATOR_MEMORY_LIMIT, default 512M (#56). On
a 3.8 GiB host, take the extra memory from php
(PHP_CONTAINER_MEMORY=1408M);docs/PRODUCTION.mdexplains why.
- Its memory ceiling is
Security
- Omeka API keys are no longer written to the nginx access log (#55).
Omeka reads keys from the query string, so the default log format recorded
key_identityandkey_credentialfor every keyed request. The new
redactedformat masks any parameter whose name containsidentityor
credential. Apply it withdocker compose restart web.
Updated
- alpine 3.24.4 (was 3.24.3) for the build's tool-fetching stage and the
helper container thatscripts/backup.shandscripts/restore.shrun (#58).
AMIRA overlay
Extension pins moved to:
- DRESearch v1.36.0 (was v1.35.0)
- DRE-SEO v0.17.0 (was v0.16.0)
- DRE-Visualizations v2.55.0 (was v2.50.0)
- DRE-LinkedData v0.7.0 (was v0.6.0)
- DRE-theme v2.50.0 (was v2.48.0)
- amira-mcp default v1.37.0 (was v1.35.0), used when
AMIRA_MCP_VERSIONis unset
CI
v2.6.1 — omeka-s-cli 0.19.0
Upgrading from v2.6.0: rebuild the code images. The new omeka-s-cli is
baked into the php image:git fetch --tags && git checkout v2.6.1 bash scripts/rebuild-code.sh docker compose exec php omeka-s-cli --version # expect 0.19.0Data volumes are kept; php and web restart briefly.
Updated
- omeka-s-cli 0.19.0 (was 0.9.3). The image build and every module and theme update use this tool (#54).
- Large release ZIPs are streamed to disk instead of loaded into memory.
- Stalled downloads are aborted rather than hanging for up to 10 minutes.
- Only http(s) URLs and file paths are accepted as sources.
- Build retries the omeka-s-cli download (
curl --retry 5). A 504 on that download failed the smoke tests of earlier Dependabot PRs (#54).
Compatibility
- Every command and option this repository uses still exists, and
gh:and release-ZIP module sources still work. scripts/update-extensions.shreads themodule:listtable. Those columns keep their positions, and a new Author column is added at the end.- Visible change: modules and themes with no update now show
nounder UpdateAvailable instead of a blank.
CI covers the build and a live module download, but not update-extensions.sh. After upgrading, run it once:
bash scripts/update-extensions.sh --no-backupWith everything current it prints only "does not need upgrade" lines. On the AMIRA deployment it did.
CI
v2.6.0 — security scanning, update tracking and base image refresh
Upgrading from v2.5.1: rebuild the images. The refreshed base images
only reach your site once it runs the rebuilt images:bash scripts/backup.sh git fetch --tags && git checkout v2.6.0 bash scripts/rebuild-code.sh --pull docker compose build --pull sparql && docker compose up -d sparql # AMIRA with the sparql profile docker compose pull db && docker compose up -d dbThe site is unavailable for a few seconds while
dbrestarts. Data volumes
are kept.
New: security scanning and update tracking
Dependabot keeps image tags and action versions current, but GitHub's advisory
database covers neither Docker images nor GitHub Actions. Until now, nothing
flagged a known vulnerability in the images this stack runs (#50).
security.ymlruns on every push, every pull request, weekly and on demand:- Trivy scans every image the stacks run (php, web, db, typesense, and for AMIRA amira-php, amira-mcp and sparql) for vulnerabilities that already have a fix. It covers OS packages and the PHP libraries bundled in Omeka and its modules.
- It also scans the repository for committed secrets and Dockerfile problems, and audits the workflows with zizmor.
- Results appear under Security → Code scanning and on pull requests.
- The weekly run fails, and keeps a tracking issue open, while any image has a fixable high or critical vulnerability. Pull requests only warn.
untracked-pins.ymlkeeps a weekly issue for versions Dependabot cannot see that have fallen behind: Omeka S core, omeka-s-cli, APCu, and module/theme release URLs.- Notifications: Dependabot PRs and the tracking issues are assigned to the maintainer. In a fork, set the
ISSUE_ASSIGNEErepository variable and editassigneesin.github/dependabot.yml. - Dependabot cooldown: version updates now wait 7 days after a release before being proposed. Security updates are not delayed.
Updated
These combine Dependabot #45–#49 (#51):
- PHP 8.5.12 rebuilt upstream with Debian security fixes (new digest, same version). Fixable high/critical findings in the php image dropped from 172 to 1.
- MySQL 9.7.4 rebuilt upstream (new digest, same version).
- SPARQL endpoint: rebuilt
debian:trixie-slimbase with Debian security fixes. - Composer 2.11.1 (was 2.11.0) and php-extension-installer 2.13.2 (was 2.12.3). Both are used only while building the image.
AMIRA overlay
Extension pins moved to:
- DRESearch v1.35.0 (was v1.34.0)
- DRE-Visualizations v2.50.0 (was v2.45.0)
- DRE-LinkedData v0.6.0 (was v0.5.0): JSON content negotiation, ETag-only 304 responses, and
scripts/generate-dump.phpnow ships in the release archive - DRE-theme v2.48.0 (was v2.47.1)
- AMIRA MCP v1.35.0 (was v1.31.1)
On a volume-backed stack, run scripts/update-extensions.sh to bring the
running site's modules and theme to these pins. Its --dry-run compares the
pins with upstream, not with what is installed, so run the real update even
if the dry run reports everything current. Update AMIRA MCP with
bash deploy/amira/update-amira-mcp.sh v1.35.0.
Known remaining findings
The first scans still report fixable high or critical vulnerabilities in
images maintained upstream:
| Image | Findings |
|---|---|
| mysql | 36 |
| amira-mcp | 10 |
| nginx (web) | 8 |
| typesense | 6 |
| sparql | 4 |
| php, amira-php | 1 each (a library bundled in the Common module) |
They clear as the upstream images are rebuilt and Dependabot proposes them.
Not included
- omeka-s-cli stays on 0.9.3; upstream is at 0.19.0. That jump changes the tool the build and module updates rely on, so it needs its own testing.
v2.5.1 — MySQL 9.7.4, base image security updates and refreshed AMIRA extensions
Upgrading from v2.5.0: rebuild the images. The new base images only
reach your site once it runs the rebuilt images:bash scripts/backup.sh git fetch --tags && git checkout v2.5.1 bash scripts/rebuild-code.sh docker compose build sparql && docker compose up -d sparql # AMIRA with the sparql profile docker compose exec db mysqld --version # expect 9.7.4
rebuild-code.shalso recreatesdbon the new MySQL image; the site is
unavailable for a few seconds while it restarts. Data volumes are kept.
Updated
- MySQL 9.7.4 (was 9.7.2), a patch release on the 9.7 LTS line (#38).
- nginx 1.30.6-alpine rebuilt upstream with Alpine security fixes (new
digest, same version) (#39). - alpine 3.24.3 (was 3.24.2) for the build's tool-fetching stage and the
helper containerscripts/backup.shandscripts/restore.shrun (#37). - Composer 2.11.0 (was 2.10.3), used only while building the image (#43).
- SPARQL endpoint: Oxigraph 0.5.13 (was 0.5.12) (#41) and a rebuilt
debian:trixie-slimbase with Debian security fixes (#44).
AMIRA overlay
Extension pins moved to:
- DRESearch v1.34.0 (was v1.30.0)
- DRE-SEO v0.16.0 (was v0.15.0)
- DRE-Visualizations v2.45.0 (was v2.42.0)
- DRE-theme v2.47.1 (was v2.43.0)
- AMIRA MCP v1.31.1 (was v1.23.0)
On a volume-backed stack, run scripts/update-extensions.sh to bring the
running site's modules and theme to these pins.
DRESearch 1.34.0 can let visitors find Research items through a private full
text they cannot read, showing only a short excerpt. It is off until a profile
names item sets under restricted_fulltext in local.config.php. Reindex
Research items once before enabling it. See the module's
docs/profile-configuration.md.
Not included
- PHP stays on 8.5.12. The 8.6.0RC2 bump (#35) was closed: it is a release
candidate and the smoke tests failed on every stack.
v2.5.0 — read-only SPARQL endpoint and DRE-LinkedData v0.5.0
Upgrading from a release before v2.4.0? Rebuild, and check PHP first.
This release removes the interim CVE-2026-109619 settings that v2.4.0 kept in
uploads.inias a safety net. PHP 8.5.12 is the actual fix, and it only
protects you once your site runs the rebuilt image:bash scripts/backup.sh git fetch --tags && git checkout v2.5.0 bash scripts/rebuild-code.sh --pull docker compose exec php php -v # expect 8.5.12Already on v2.4.0 with
php -vreporting 8.5.12? Then nothing needs
rebuilding:git fetch --tags && git checkout v2.5.0is enough.
Security
- The
uploads.iniinterim mitigation for CVE-2026-109619
(session.upload_progress.enabled = 0,fatal_error_backtraces = 0) is
removed now that PHP 8.5.12 is the pinned runtime (#33). The file is
bind-mounted, so the change takes effect on the nextphprestart. Neither
setting affected Omeka S, so removing them changes nothing else.
Added
- An opt-in, read-only SPARQL endpoint at
/sparqlfor the AMIRA overlay
(#28). It serves the DRE-LinkedData dump through
Oxigraph and is switched on with
COMPOSE_PROFILES=search,sparql. Off by default; the base stack is
unchanged. See
deploy/amira/README.md.- Reloads itself. It loads each new dump into a fresh store, checks it
against the dump's SHA-256, and swaps it in only once the load is complete,
so a query never sees half a graph. A restart reuses the last good store. - Cannot slow the site down. It is capped at half a CPU and 256 MB, with
a quarter of the default CPU weight, so Omeka wins whenever they compete.
Queries time out after 30 s. A watchdog restarts the server if a query
escapes that timeout, which Oxigraph only enforces while reading the store.
Each connection is also closed after 60 s whatever it is doing, so a result
that keeps streaming cannot hold a slot (#36). nginx allows each visitor 60
queries a minute and 2 at a time, and the endpoint 4 at a time. Results are
sent uncompressed: gzipping them in the web container, whose quarter CPU
every page shares, held other requests back by over 2 s in testing. - No network at all. SPARQL's
SERVICEkeyword makes the server fetch
other URLs, and Oxigraph cannot turn it off. Even an internal Docker
network can reach the host's own ports, so the service runs with
network_mode: noneand nginx reaches it over a Unix socket. CI asserts
this isolation. - Behaves for browsers and catalogues (#36). Opening
/sparqlin a
browser leads to the Linked open data page. The service description
states the endpoint's publichttps://address. Each new store is
compacted before it is served.
- Reloads itself. It loads each new dump into a fresh store, checks it
Updated
- RDF, CSV and TSV responses are now gzip-compressed by the base
nginx.conf: Turtle, N-Triples, N-Quads, TriG, RDF/XML, the SPARQL result
types,text/csvandtext/tab-separated-values(#36). It applies to every
install, on the nextdocker compose restart web. AMIRA's/sparql
location opts out, as above. - AMIRA deployment: DRE-LinkedData v0.5.0 (the SPARQL endpoint setting,
advertised asvoid:sparqlEndpoint, and a query form on the Linked open
data page that runs only when a visitor submits it), DRE-theme v2.43.0,
DRE-Visualizations v2.42.0; Oxigraph 0.5.12 for the SPARQL endpoint (#34) - AMIRA README: a nightly
generate-dump.php --if-stalecron line, since the
endpoint is only as current as the dump - README: links to AMIRA, and
states the hardening accurately. nginx's master process and the optional
Typesense image run as root inside their containers; PHP runs unprivileged.
Verification
CI is green on e6591bc — validate plus smoke tests across the base, AMIRA
and immutable overlays. The AMIRA smoke test checks that /sparql answers
503 with CORS when the profile is off, sends browsers to the Linked open
data page, and keeps its internal service-description location private.
The endpoint has served https://data.africamultiple.uni-bayreuth.de/sparql
since 2026-10-22, now with DRE-LinkedData v0.5.0. Tested on that host:
- a runaway query held in memory was stopped by the watchdog at 60 s;
- an endless cross join was cut off at 32 s, after streaming 480 MB;
- Omeka's pages kept answering in under 0.2 s through both, and the next query
was answered at once.
v2.4.0 — PHP 8.5.12 security upgrade and the dre: vocabulary endpoint
Security release — rebuild as soon as you can.
This release upgrades PHP to 8.5.12, which fixes two critical
vulnerabilities that allow unauthenticated remote code execution
(CVE-2026-109618
and CVE-2026-109619,
both CVSS v4.0 9.2). PHP-FPM, which this stack uses, is an affected
configuration.Changing the pin is not enough on its own — your site keeps serving the old
image until you rebuild:bash scripts/backup.sh git fetch --tags && git checkout v2.4.0 bash scripts/rebuild-code.sh --pull docker compose exec php php -v # expect 8.5.12If the rebuild fails at
install-php-extensions, that ispecl.php.net
being unavailable rather than a problem with this release — it was
intermittently down for about 40 minutes on release day. Wait and retry.
Security
- PHP 8.5.11 → 8.5.12, pinned by digest and verified to carry
PHP_VERSION=8.5.12before being committed. uploads.inicarries two hardening settings added as an interim mitigation
for CVE-2026-109619 while the patched image was still being published:
session.upload_progress.enabled = 0andfatal_error_backtraces = 0.
They are deliberately still here. They cost nothing — Omeka S uses
neither feature — and they keep you covered if your rebuild fails partway and
the old image restarts. Oncephp -vreports 8.5.12 you can delete that
block; the only effect of keeping it is slightly terser fatal-error logs.- The advisory's suggested mitigations for CVE-2026-109618 are not applied,
anduploads.inirecords why:memory_limit = -1would let one request grow
past the container's memory cap and have the OOM killer take down the whole
php service instead of failing that request, andpost_max_size = 8Mwould
break 100M media ingest. That CVE is fixed by the upgrade alone.
Added
- The
dre:vocabulary is now served from AMIRA's own domain at
/ontology/dre, with content negotiation across HTML, JSON-LD, RDF/XML and
Turtle, plus abuild_dre_vocabulary.pygenerator and a.well-known/void
redirect. Replaces the singledre.owlfile.
Updated
- nginx 1.30.5 → 1.30.6-alpine
- mlocati/php-extension-installer 2.11.1 → 2.12.3
- composer/composer and mysql digest refreshes
- AMIRA deployment: DRESearch v1.30.0, DRE-Visualizations v2.39.1,
DRE-theme v2.42.0, DRE-SEO v0.15.0, DRE-LinkedData v0.3.1
Verification
CI is green on 669e8f5 — validate plus smoke tests across the base, AMIRA
and immutable overlays. The build log confirms it used
php:8.5.12-fpm-trixie@sha256:8b4b4a76…, not a cached 8.5.11 layer.
v2.3.0 — trusted-proxy hardening and in-place extension updates
Upgrading? Check two settings before you redeploy.
Serving the site directly over HTTP, with no reverse proxy (
NGINX_BIND=0.0.0.0)? Add this to.env:NGINX_TRUSTED_PROXY_CIDR=192.0.2.1/32That trusts no real peer, so no visitor can forge their address with an
X-Forwarded-Forheader. Until you set it, the default (172.16.0.0/12) applies. The one-click installer already writes it for HTTP-only installs.Behind a reverse proxy on a custom
10.xor192.168.xDocker network? SetNGINX_TRUSTED_PROXY_CIDRto that network, or better, the proxy's own address. Otherwise nginx ignores the proxy'sX-Forwarded-ForandX-Forwarded-Protoheaders. The login rate limit then counts every visitor as one client, and Omeka generateshttp://links. Proxies on Docker's default bridges need no change.If you update modules with
scripts/update-module.sh, switch toscripts/update-extensions.sh. On the default layout, modules and themes live on volumes.update-module.shonly rewrites the pins and rebuilds the images, which never reach those volumes, so the site would keep running the old versions.
Security
- nginx trusts one proxy address you choose instead of every private network. v2.2.0 accepted forwarded client addresses from all of
10.0.0.0/8,172.16.0.0/12and192.168.0.0/16. The newNGINX_TRUSTED_PROXY_CIDRsetting names the one address or network allowed to send them.X-Forwarded-Proto: httpsis honoured only from that proxy too. - PHP can run only through
/index.php. Requests for.php,.phtml,.pharand numbered.php5-style files are refused, including path-info variants such asupload.php/photo.jpg. - Omeka's secret key can live in
.env. Omeka encrypts stored secrets with a key it tries to write intoconfig/, which is read-only here. That write always failed and left a warning on every admin page. Generate a value once withopenssl rand -base64 32, set it asOMEKA_SECRET_KEY, and never change it. - The database now flushes every commit to disk (
innodb-flush-log-at-trx-commit=1). A host crash can no longer lose the last second of edits. - The web container's tmpfs directories are root-owned
0755instead of world-writable1777.
Features
scripts/update-extensions.shis the one command for updating modules and themes. It backs up first, moves every pinned release archive to its newest release, and refreshes the live volumes. It then applies pending module migrations. On volume-backed stacks it no longer rebuilds the images, since the volumes take precedence over them; pass--rebuildor--pullto rebuild anyway.--dry-runreports without changing anything.- Backup retention:
backup.sh --keep N(orBACKUP_KEEP=Nin.env) deletes older snapshots once the new one is complete and checksummed. Unfinished snapshots are never counted. backup.sh --quiescestops web and PHP for the backup's duration, so the database dump and media archive come from the same moment. They restart afterwards.scripts/health-report.shprints a read-only summary of every container: state, health, restarts, out-of-memory kills, and current CPU and memory use.- Resource limits are set in
.env:PHP_CONTAINER_MEMORY,PHP_CPU_LIMIT,WEB_*,DB_*andSEARCH_*, for hosts larger or smaller than the defaults assume. - New guide for institutions: docs/INSTITUTION_SETUP.md covers adapting the template for your own institution.
- Modules can be installed from their published release archives (a
.zipURL inmodules.txtorthemes.txt). That gives a clean packaged copy instead of a git checkout of the module's development tree.
Fixes
- nginx follows PHP to its new address. Recreating only the
phpcontainer used to leave nginx on the old IP, and the site returned 502 untilwebwas restarted too. - Updated extensions reach visitors immediately. Static files are now revalidated instead of cached for a year, and PHP re-reads changed code within two seconds. Admin-panel and command-line module updates take effect without a restart.
- Backups are safer to rely on:
- An interrupted backup is marked incomplete, and
restore.shrefuses to restore it. backup.shrefuses to write into a non-empty directory.- Volumes are found from the active Compose configuration, not guessed from the project name.
- The Typesense search index is no longer archived, since a live copy of it is not a reliable snapshot. Rebuild the index from Omeka after a restore.
restore.sh --restore-searchstill reads older archives that include it.
- An interrupted backup is marked incomplete, and
update-extensions.shno longer downgrades pinned modules through the Omeka module registry. It also no longer unpacks duplicate copies of a module under differently cased folder names.update-module.shexits with an error when it cannot check a pinned archive. It reads only the manifests your active Compose configuration uses, not other institutions' files.- The PHP-FPM pool settings are checked at startup (
min_spare ≤ start ≤ max_spare ≤ max_children). A bad combination now fails with a clear message instead of crash-looping. - The database healthcheck works with passwords that contain shell-special characters.
AMIRA deployment
These changes affect only sites that use the AMIRA overlay (compose.amira.yml):
- The MCP server rate-limits each visitor separately instead of counting everyone as one client. Visitors can no longer forge their address to get around the limit.
- DRE-Visualizations keeps its generated files on a private volume,
dre_visualizations_private. After upgrading, press DRE Visualizations → Regenerate now once. The olddre_visualizations_datavolume can be removed after that succeeds. /favicon.icoserves the DRE-theme icon.- Pins: DRESearch 1.28.1, DRE-Visualizations 2.35.0, DRE-SEO 0.11.0, DRE-theme 2.35.3, amira-mcp v1.23.0.
Base images and docs
- PHP 8.5.11, nginx 1.30.5, Alpine 3.24.2 and Composer 2.10.3. Omeka S stays at 4.2.1. Dependabot now also tracks the Composer and php-extension-installer images.
- The README is now a shorter getting-started guide. Reference material moved to docs/CONFIGURATION.md, docs/CUSTOMISING.md and docs/PRODUCTION.md.
- The backup cron example in BACKUP_RESTORE.md is fixed. The old
find … -exec rm -rfline also matchedbackups/itself, and after one failed run it would have deleted every backup.
Full changelog: v2.2.0...v2.3.0