After you've finished installing Islandora using ISLE, here's some useful information to keep close at hand about running your site.
make commands that you used to install Islandora will leave you with two very important files.
||A configuration file that is yours to customize. This file controls how the docker-compose.yml file gets generated to meet your use case.It also allows you to set variables that make their way into the final
||A ready to run
Here's a list of all the available services. Note that there are some services over
http and not
Those aren't meant to be exposed to the public, but internally people from your organization will want to
access them. In practice, you can restrict access to these services using firewall rules to just those who
If you want to stop Islandora, you can bring down all the containers with
If you want to start Islandora back up after stopping it, use
If you want to stop Islandora and delete all of its content, use
If you make changes to configuration in the .env file, you may need to regenerate your
docker-compose.yml file so that
those changes take effect.
Once you have a new
docker-compose.yml file, you'll need to restart your containers that have had configuration change.
You can do this easily with
Even if the site is up and running, that command will only restart the containers it needs to.
You can see a list of all the containers that you have running and their statuses by running
You can tail logs using
docker-compose logs service_name
For example, to tail nginx logs for Drupal, use
docker-compose logs drupal.
If you don't know what you're looking for exactly, you can turn on the fire hose and look through all logs by dropping the service name and simply using