32

Hi! I'm currently looking onto perhaps running Jellystat. But the instructions seem to be a bit...lacking? Is there a step by step guide on how to get it up and running?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[-] bobslaede@feddit.dk 1 points 2 months ago

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
[-] iturnedintoanewt@lemm.ee 1 points 2 months ago* (last edited 2 months ago)
 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

Hmmm thanks but I'm not using traefik...Is it part of the needed setup?

[-] bobslaede@feddit.dk 1 points 2 months ago

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.

[-] iturnedintoanewt@lemm.ee 2 points 2 months ago

Just came to say thanks...Yeah eventually after copy-pasting it from scratch again, I got it running. Seems to be working now. Thanks again!

this post was submitted on 22 Aug 2024
32 points (97.1% liked)

Selfhosted

40183 readers
645 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS