Islandora Enterprise (ISLE) is a community project that addresses two of the most significant pain-points in Islandora: installation and maintenance.
[!WARNING] The ISLE Legacy project (also known as ISLE7) is no longer actively supported by the Islandora community, except for some security updates. When creating new sites, please see the currently supported installation options found in the official Islandora community documentation site. For the latest ISLE, please use the isle-dc repository instead: https://github.com/Islandora-Devops/isle-dc
ISLE uses replaceable Docker images to streamline and largely automate the process of installing and maintaining the entire Islandora 7.x stack, while at the same time enabling institutions to create customizations that persist separately from core code. The result is the ability to easily, quickly and regularly update an institution’s entire Islandora stack. Maintaining ISLE requires significantly less time and staff, and also reduces the dependency on expert technical staff and outside vendors.
The ISLE project maintainers keep your Islandora stack smoothly running with minimal effort by regularly releasing updated (and tested) Docker images that contain up-to-date Islandora releases, software patches, security updates and feature improvements.
ISLE is quite flexible and may be run on an institution’s servers or in the cloud, or as a hybrid; similarly, it may be maintained by an institution’s staff, by a vendor, or as a shared project.
ISLE (legacy) is on a quarterly release cycle.
1.5.28
- January 2024 (Q1 2024)Please use the ISLE Documentation for using ISLE to install Islandora on server environments.
Important: This "Quick Start Guide" is for testing ISLE and should not be used in production.
24.x
+1.29.2
2.0+
COMPOSE_CONVERT_WINDOWS_PATHS=1
git clone https://github.com/Islandora-Collaboration-Group/ISLE.git
cd ISLE
(by default)cp sample.env .env
docker-compose pull
docker-compose up -d
docker exec -it isle-apache-ld bash /utility-scripts/isle_drupal_build_tools/isle_islandora_installer.sh
docker-compose down -v
(nb: the -v removes all volumes, and will delete any work. This option does not persist your data)If you have been testing the stack extensively you may want to prune
your Docker daemon as you test.
docker-compose.demo.yml
docker-compose down -v
pruned
on Docker:
docker system prune --all
Y
to remove all unused volumes, images, and networks.prune
:
docker ps
and take note of any running ISLE services:
docker down {list of all the running ISLE services, tab auto-complete may work}
(You may add as many containers as needed in one command.)docker image ls
and take note of all ISLE-related images:
docker image rm {list of all images to be removed, tab auto-complete may work}
(Again, you may add as many as needed.)docker volume ls
and take note of all ISLE-related volumes:
docker volume rm {list of all volumes to be removed, tab auto-complete may work}
(Again, you may add as many as needed.)docker network ls
and take note of all ISLE-related networks:
docker network rm {list of all networks to be removed, tab auto-complete may work}
(Again, you may add as many as needed.)Portainer is a GUI for managing Docker containers. It has been built into ISLE for your convenience.
Windows Users: Please open the .env and uncomment COMPOSE_CONVERT_WINDOWS_PATHS=1
Note that both HTTP and HTTPS work Please accept the self-signed certificate for testing when using HTTPS.
docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' isle-apache-ld
http://{IP}/
Read as username:password
Islandora (Drupal) user and pass (default):
isle
:isle
All Tomcat services come with the default users and passwords:
admin
:isle_admin
manager
:isle_manager
Portainer's authentication can be configured: