29 Heimdall

Heimdall Application Dashboard is a dashboard for all your web applications. It doesn’t need to be limited to applications though, you can add links to anything you like.

Heimdall is an elegant solution to organise all your web applications. Its dedicated to this purpose so you wont lose your links in a sea of bookmarks.

Heimdall provides a single URL to manage access to all of your autopirate tools, and includes “enhanced” (i.e., display stats within Heimdall without launching the app) access to NZBGet, SABnzbd, and friends.

29.1 Inclusion into AutoPirate

To include Heimdall in your AutoPirate stack, include the following in your autopirate.yml stack definition file:

  heimdall:
    image: linuxserver/heimdall:latest
    env_file: /var/data/config/autopirate/heimdall.env
    volumes:
      - /etc/localtime:/etc/localtime:ro      
      - /var/data/heimdall:/config
    networks:
      - internal

  heimdall_proxy:
    image: funkypenguin/oauth2_proxy:latest
    env_file : /var/data/config/autopirate/heimdall.env
    networks:
      - internal
      - traefik_public
    deploy:
      labels:
        - traefik.frontend.rule=Host:heimdall.example.com
        - traefik.docker.network=traefik_public
        - traefik.port=4180
    volumes:
      - /etc/localtime:/etc/localtime:ro  
      - /var/data/config/autopirate/authenticated-emails.txt:/authenticated-e\
mails.txt
    command: |
      -cookie-secure=false
      -upstream=http://heimdall:80
      -redirect-url=https://heimdall.example.com
      -http-address=http://0.0.0.0:4180
      -email-domain=example.com
      -provider=github
      -authenticated-emails-file=/authenticated-emails.txt

29.2 Assemble more tools..

Continue through the list of tools below, adding whichever tools your want to use, and finishing with the end section:

• SABnzbd
• NZBGet
• RTorrent
• Sonarr
• Radarr
• Mylar
• Lazy Librarian
• Headphones
• Lidarr
• NZBHydra
• NZBHydra2
• Ombi
• Jackett
• Heimdall (this page)
• End (launch the stack)

29.3 Chef’s Notes

1. In many cases, tools will integrate with each other. I.e., Radarr needs to talk to SABnzbd and NZBHydra, Ombi needs to talk to Radarr, etc. Since each tool runs within the stack under its own name, just refer to each tool by name (i.e. “radarr”), and docker swarm will resolve the name to the appropriate container. You can identify the tool-specific port by looking at the docker-compose service definition.
2. The inclusion of Heimdall was due to the efforts of @gkoerk in our Discord server. Thanks gkoerk!

Launch Autopirate stack

Launch the AutoPirate stack by running docker stack deploy autopirate -c <path -to-docker-compose.yml>

Confirm the container status by running “docker stack ps autopirate”, and wait for all containers to enter the “Running” state.

Log into each of your new tools at its respective HTTPS URL. You’ll be prompted to authenticate against your OAuth provider, and upon success, redirected to the tool’s UI.

29.4 Chef’s Notes

1. This is a complex stack. Sing out in the comments if you found a flaw or need a hand :)

hero: Duplicity - A boring recipe to backup your exciting stuff. Boring is good.