Bluebeam

Yeah it seems like HA OS is the way to go, running the separate Docker containers has been a headache and breaks/take time more than it’s worth

For anyone trying to google a solution, I got it to work with the below in Portainer

version: ‘3.7’

services:

api:
    image: 'gthole/drink-stash:latest'
    init: true
    restart: 'always'
    environment:
      - SECRET_KEY=*enter-a-key-here*
      - ALLOWED_HOSTS=*enter-ip-here*
      - DJANGO_SUPERUSER_USERNAME=*can-be-whatever*
      - DJANGO_SUPERUSER_EMAIL=*duh*
      - DJANGO_SUPERUSER_PASSWORD=*make-it-up*
      - DJANGO_SUPERUSER_FIRST_NAME=*John*
      - DJANGO_SUPERUSER_LAST_NAME=*Smith*
      - INITIAL_FIXTURES=recipes
    ports:
      - 8081:8000
    volumes:
        - /volume1/docker/drink-stash/data:/data
        - /volume1/docker/drink-stash/public:/public

deleted by creator

Well that did allow the Portainer to compile without error and deploy so I really appreciate the help! When navigating to the http://(my ip):8081 though I get a white page with “Bad Request (400)” on it

Not sure on the terms, but I did change the volume lines to direct to folders I pre-made in /volume1/drink-stash/data (same for public)

Well, with “- SECRET_KEY=” I at least got a different error, a bind mount fail?

Well, I added in the docker-compose snippet in the “Running” section of the link to a new stack in Portainer, changing secret_key and allowed_hosts to localhost, pre-setup the volumes on Synology. The first error I get is “services.api.environment must be a mapping”

Not sure why the downvote, its right there on the website https://tailscale.com/pricing/

Yeah, the digg v4 move didn’t have identical reasons as now, but it sure felt familar