a docker compose file needed

[Vikaskumargd]

A docker compose file for easy self hosting

[monorkin]

@Vikaskumargd Fizzy is a single-container project, there aren't any dependencies to orchestrate with Docker Compose.

If you want to run it via compose, this one should work:

services:
    web:
      image: ghcr.io/basecamp/fizzy:main
      ports:
        - "80:80"
        - "443:443"
      environment:
        - RAILS_ENV=production
        - DATABASE_ADAPTER=sqlite
        - SOLID_QUEUE_IN_PUMA=true
        - SECRET_KEY_BASE=${SECRET_KEY_BASE}
        - VAPID_PRIVATE_KEY=${VAPID_PRIVATE_KEY}
        - VAPID_PUBLIC_KEY=${VAPID_PUBLIC_KEY}
        - SSL_DOMAIN=${SSL_DOMAIN}
      volumes:
        - fizzy_storage:/rails/storage
        - thruster_certs:/rails/.thruster
      healthcheck:
        test: ["CMD", "curl", "-f", "http://localhost:3006/up"]
        interval: 30s
        timeout: 10s
        retries: 3
        start_period: 5s

volumes:
    fizzy_storage:
    thruster_certs:

If you really want, you can split out SolidQueue into a separate container:

services:
    web:
      image: ghcr.io/basecamp/fizzy:main
      ports:
        - "80:80"
        - "443:443"
      environment:
        - RAILS_ENV=production
        - SECRET_KEY_BASE=${SECRET_KEY_BASE}
        - VAPID_PRIVATE_KEY=${VAPID_PRIVATE_KEY}
        - VAPID_PUBLIC_KEY=${VAPID_PUBLIC_KEY}
        - DATABASE_ADAPTER=sqlite
        - SSL_DOMAIN=${SSL_DOMAIN}
        - ACME_DIRECTORY=${ACME_DIRECTORY:-https://acme-v02.api.letsencrypt.org/directory}
      volumes:
        - fizzy_storage:/rails/storage
        - thruster_certs:/rails/.thruster
      healthcheck:
        test: ["CMD", "curl", "-f", "http://localhost:3006/up"]
        interval: 30s
        timeout: 10s
        retries: 3
        start_period: 5s

    jobs:
      image: ghcr.io/basecamp/fizzy:main
      command: bin/jobs
      environment:
        - RAILS_ENV=production
        - SECRET_KEY_BASE=${SECRET_KEY_BASE}
        - VAPID_PRIVATE_KEY=${VAPID_PRIVATE_KEY}
        - VAPID_PUBLIC_KEY=${VAPID_PUBLIC
        - DATABASE_ADAPTER=sqlite
      volumes:
        - fizzy_storage:/rails/storage

volumes:
    fizzy_storage:
    thruster_certs:

[Aerics84]

If i would like to change to DATABASE_ADAPTER=mysql, what more i need to setup so fizzy connects to the mysql container?

[SeriousM]

very good question! sqlite is nice but not as reliable as a real db.

found this one:

fizzy/config/database.mysql.yml

Lines 3 to 6 in 641e67d

	host: <%= ENV.fetch("MYSQL_HOST", "127.0.0.1") %>
	port: <%= ENV.fetch("MYSQL_PORT", "3306") %>
	username: <%= ENV.fetch("MYSQL_USER", "root") %>
	password: <%= ENV["MYSQL_PASSWORD"] %>

[northeastprince]

SQLite is actually just as reliable as any "real DB", and with minor configuration (which Rails does by default), it can be a great option for small-to-medium setups, aka the majority of them.

[SeriousM]

true, @northeastprince. Thanks for pointing this out. I host fizzy at coolify and it currently has db backup solutions for postgres, mysql, mariadb and mongodb. sqlite is "just" a file and I wanted to use the backup functionality for that. I guess I need to find a solution to backup sqlite instead.