bobslaede

Can I finally replace my old chromecast audio devices. That would be great.

Erosion

I totally read that as Eurovision, and I could absolutely not figure out how that ties in to this.

I think it looks pants

What does that even mean?

It's from diskette. Not about what country the spelling is from.

No. You can leave that out. That was just me showing you that it runs on my machine, with that setup. Just bind the port instead.

Your passwords for the database does not match.
But the error is about it not being able to reach the database on the hostname.
I can run it with this compose file:

services:
  jellystat-db:
    image: postgres:16-alpine
    container_name: jellystat-db
    restart: unless-stopped
    environment:
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
    volumes:
      - postgres-data:/var/lib/postgresql/data
    networks:
      - jellystat
  jellystat:
    image: cyfershepard/jellystat:latest
    container_name: jellystat
    restart: unless-stopped
    environment:
      POSTGRES_USER: ${POSTGRES_USER}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_IP: jellystat-db
      POSTGRES_PORT: 5432
      JWT_SECRET: ${JWT_SECRET}
      TZ: Europe/Paris # timezone (ex: Europe/Paris)
      JS_BASE_URL: /
    volumes:
      - jellystat-backup-data:/app/backend/backup-data
    depends_on:
      - jellystat-db
    networks:
      - traefik
      - jellystat
    labels:
      - traefik.enable=true
      - traefik.docker.network=traefik
      - traefik.http.routers.jellystat.entrypoints=https
      - traefik.http.routers.jellystat.rule=Host(`${HOSTNAME}`)
      - traefik.http.routers.jellystat.tls.certresolver=http
      - traefik.http.routers.jellystat.service=jellystat
      - traefik.http.services.jellystat.loadbalancer.server.port=3000
      - traefik.http.services.jellystat.loadbalancer.server.scheme=http
networks:
  jellystat: {}
  traefik:
    external: true
volumes:
  postgres-data: null
  jellystat-backup-data: null

In the same place as you run your docker compose up command you just type docker compose logs

There will probably be something in the logs that tells you what is going wrong. Maybe it can't connect to the db, or maybe it's starting on a wrong port or something.

Uh! They should use AI for it. That will be great! /s

They have a docker-compose.yml file in the repo. It looks like it has everything all ready for you.

Are we sure these are real humans?

You get a ThinkPad! And you get a ThinkPad! Everyone gets a ThinkPad! :oprah_wave: