iiifchooses the implementation:cantaloupeortriplet.iiif-topologychooses where that implementation runs.disabledmeans local Compose.distributedmeans Drupal points at an external upstream while local development keeps the selected IIIF service indocker-compose.dev.yml.
Component reference
| Component | Dispositions | Default | Managed changes |
|---|---|---|---|
iiif | cantaloupe, triplet | cantaloupe | Compose services and volumes, conf/traefik/cantaloupe.yml, conf/traefik/triplet.yml, conf/triplet/config.yaml, Drupal’s Cantaloupe URL, and robots.txt IIIF route hints. |
iiif-topology | disabled, distributed | disabled | Base Compose service placement, Drupal’s Cantaloupe URL, Traefik IIIF_UPSTREAM_URL, and docker-compose.dev.yml local override settings. |
Use Triplet Locally
conf/triplet/config.yaml, routes /iiif, and updates Drupal’s Cantaloupe URL setting to /iiif/3.
Triplet uses the existing Drupal public/private volumes and the fcrepo volume when fcrepo is present. It also adds a triplet-cache volume for derivatives.
Use Cantaloupe Locally
/cantaloupe Traefik routing, removes Triplet files, and points Drupal back at /cantaloupe/iiif/2.
Use External IIIF
distributed when Cantaloupe or Triplet runs outside the public site stack. sitectl removes the selected IIIF service from docker-compose.yml, updates Drupal’s DRUPAL_DEFAULT_CANTALOUPE_URL to the upstream URL, sets IIIF_UPSTREAM_URL on Traefik, and keeps a local override service for development in docker-compose.dev.yml.
The selected implementation still matters:
iiif tripletroutes/iiifand uses a local Triplet override on port8080.iiif cantalouperoutes/cantaloupeand uses a local Cantaloupe override on port8182.
docker compose workflows can still use the selected IIIF service even when the base stack is distributed.
Return to local IIIF with:
Create Flags
You can choose the same shape duringsitectl create isle:

