Repository navigation
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