Skip to main content
The ISLE plugin manages IIIF with two related components:
  • iiif chooses the implementation: cantaloupe or triplet.
  • iiif-topology chooses where that implementation runs. disabled means local Compose. distributed means Drupal points at an external upstream while local development keeps the selected IIIF service in docker-compose.dev.yml.

​
Component reference

​
Use Triplet Locally

This removes the local Cantaloupe service and Traefik file, adds the Triplet service, writes 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

This restores the Cantaloupe service and /cantaloupe Traefik routing, removes Triplet files, and points Drupal back at /cantaloupe/iiif/2.

​
Use External IIIF

Use 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 triplet routes /iiif and uses a local Triplet override on port 8080.
  • iiif cantaloupe routes /cantaloupe and uses a local Cantaloupe override on port 8182.
The development override resets Drupal and Traefik to the local service URL, so local 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 this setup during sitectl create isle:
If you do not pass topology flags, sitectl assumes local IIIF.