Jafner.net/5etools-docker/README.md

Note: The 5e.tools domain upon which this image relies is offline indefinitely. This image will not work until this situation is resolved.

This is a simple image for hosting your own 5eTools instance. It is based on the Apache httpd image and uses a heavily-modified version of the auto-updater script from the 5eTools wiki. This image is built from this GitHub repository.

Usage with Docker Run

Quickstart

You can quick-start this image by running:

docker run -d -p 80:80 --rm --name 5etools-docker -v 5etools:/usr/local/apache2/htdocs jafner/5etools-docker

Then give the container a minute or two to come online and it will be accessible at localhost. When you stop the container, it will automatically delete itself. The downloaded files will remain in the 5etools volume, so you can always start the container back up by re-running the command.

Getting token images

You can configure the container's initialization script to download image files by setting the IMG environment variable: docker run -d -p 80:80 --rm --name 5etools-docker -v 5etools:/usr/local/apache2/htdocs -e IMG=true jafner/5etools-docker This will add a significant amount of time to the container's initialization. The -e flag specifies a Docker environment variable, which is passed into the container's shell environment and allows for customization of the container during the run command. Here, the environment variable is named IMG and this command sets the value to true.

Using a persistent volume

By default, this container uses a Docker-managed persistent volume for the server files. This allows the downloaded 5eTools files to persist, even if the container is destroyed. Alternatively, you can use a host directory mapping to share files between your host file system and the container.

Using a host directory mapping

You can persist your container's data by mapping a directory in the host's file system into the container. Assuming you want to use the directory ~/5etools-docker on the host:

1. Create the directories with mkdir -p ~/5etools-docker/htdocs/download. This will create the three nested directories necessary to run the container.
2. Run the container with docker run -d -p 80:80 --rm --name 5etools-docker -v ~/5etools-docker/htdocs:/usr/local/apache2/htdocs jafner/5etools-docker Note: host directory mappings must be absolute (cannot use . to refer to working directory). However, you can still refer to your working directory with ${PWD}.

Updating the container

Because this image is built on the auto-updater script, updating the container is very simple. Restart the container with docker restart 5etools-docker. When it restarts, the container will automatically check for an update and download it before starting. Note: there is no way to disable this auto-updating behavior except to never restart the container. If you want a specific version of the container, it is recommended that you look into using the httpd image instead.

Using a different port

Change the value on the left side of the -p 80:80 flag to the desired port. Leave the value on the right alone.

Integrating a reverse proxy

Supporting integration of a reverse proxy is beyond the scope of this guide. However, any instructions which work for the base httpd (Apache) image, should also work for this, as it is minimally different.

Usage with Docker Compose

Create the ~/5etools-docker/docker-compose.yml file with your preferred text editor. Then add the following contents:

version: "3"
services:
  5etools-docker:
    container_name: 5etools-docker
    image: jafner/5etools-docker:latest
    volumes:
      - ~/5etools-docker/htdocs:/usr/local/apache2/htdocs 
    environment:
      - IMG=false # set to true to download images
      - PUID=1000 
      - PGID=1000

If you would like to auto-load homebrew, you will need to follow the instructions in the Compose file.

Auto-loading homebrew

To use auto-loading homebrew, you will need to use a host directory mapping as described above.

1. Start the container (using either docker run or docker-compose) and wait for the container to finish starting. You can monitor its progress with docker logs -f 5etools-docker.
2. Assuming you are using the mapping ~/5etools-docker/htdocs:/usr/local/apache2/htdocs place your homebrew json files into the ~/5etools-docker/htdocs/homebrew/ folder, then add their filenames to the ~/5etools-docker/htdocs/homebrew/index.json file. For example, if your homebrew folder contains:

index.json
'Jafner; JafnerBrew Campaigns.json'
'Jafner; JafnerBrew Collection.json'
'Jafner; Legendary Tomes of Knowledge.json'
'KibblesTasty; Artificer (Revised).json'

Then your index.json should look like:

{
    "readme": [
        "NOTE: This feature is designed for use in user-hosted copies of the site, and not for integrating \"official\" 5etools content.",
        "The \"production\" version of the site (i.e., not the development ZIP) has this feature disabled. You can re-enable it by replacing `IS_DEPLOYED = \"X.Y.Z\";` in the file `js/utils.js`, with `IS_DEPLOYED = undefined;`",
        "This file contains as an index for other homebrew files, which should be placed in the same directory.",
        "For example, add \"My Homebrew.json\" to the \"toImport\" array below, and have a valid JSON homebrew file in this (\"homebrew/\") directory."
    ],
    "toImport": [
        "Jafner; JafnerBrew Collection.json",
        "Jafner; JafnerBrew Campaigns.json",
        "Jafner; Legendary Tomes of Knowledge.json",
        "KibblesTasty; Artificer (Revised).json"
    ]
}

Note the commas after each entry except the last in each array. See the wiki page for more information.