IIIF Cloud uses S3 compatible storage to store images and PDFs. The system has been tested with AWS S3 but should also work with S3 compatible object storage systems as well.
The IIIF Cloud docker compose setup uses the Cantaloupe IIIF Image Server. The docker image that is used is the UCLA Library docker-cantaloupe distribution.
The IIIF Cloud system uses Redis as the job backend for the rails service. The docker compose system utilizes the official image.
The IIIF Cloud system uses Postgres as the DB for the CMS subsystem. The docker compose system utilizes the official image.
Using the .env.example as a guide, set the appropriate values for the variables.
The sections below have some additional guidance in terms of proper setting of these variables.
Whether using AWS S3 or a compatible service, create a bucket that will hold your uploaded images.
Set the ENV variable AWS_BUCKET_NAME to the name of the bucket.
Be sure to proved a access key and a secret access key which has access to this resource. SET the appropriate values in the ENV variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
If using AWS S3, set the ENV variable AWS_REGION to the region in which the bucket was created (i.e. us-east-1).
In order to persist your DB between restarts, it is recommended that you set a local file directory as the location for the DB data. This could be local block storage or a mounted NFS drive. Set the ENV variable DB_VOLUME to this directory.
IIIF_HOST
- When running locally (localhost), this should be set tohttp://localhost:8182
, If being run with a domain, it should be set to the url that will be handling Cantaloupe traffic on port 8182. The HTTPS traffic will be handle on port 8183.SECRET_KEY_BASE
- This is a rails style secret which can be generated using opensslopenssl rand -hex 64
HOSTNAME
- Should be the hostname for IIIF Cloud CMS.http://localhost:8080
for local installs.REDIS_URL
- This should be removed when using docker-compose.
From the root of the project repo run:
docker compose up --build
This will build the iiif-cloud image and startup the entire system once built.
After the first run, if the code has not changed you can run:
docker compose up
The IIIF CMS is seeded with an initial admin account of:
Username: [email protected]
Password: password
This should be immediately changed after first login.
- Navigate to the IIIF Cloud frontend and login using the credentials above.
- Go to user management (the People Icon on the sidebar navigation)
- Edit the Administrator user
- Set the Email and Password to your desired values.