Deploying on Coolify?

[pfriedl]

Hey all, I've tried to deploy Fizzy on Coolify, but it continues to fail. Is there any SOP or guide for using it on a system like Coolify?

[monorkin]

Hi @pfriedl I haven't used Coolify before so I'm not familiar with how it work.
Can you tell me if you are running into an error of some kind? I assume it deploys our Docker container?

[SamuelAierizer]

@pfriedl - I was just thinking the same thing! 🙂 Before we make it a deploy with one click we could just create a docker compose that handles everything. From reading the issues I think here (#1801) it was also discussed to have a Prebuilt Docker Image so if we are able to pull it from a public registry then we could set this up to be a very easy deploy. I want to take a look at it when I have some time but if someone does it faster, then thank you in advance!

[pfriedl]

Here's what I'm trying to do with Coolify - which is just a glorified docker manager with a pretty UI You create a project and add a resource, and I'm selecting the GIT repo: <img width="856" height="436" alt="01" src="https://github.com/user-attachments/assets/f08d029b-dc21-4df7-968b-452cd13f6c5c" /> Next you can set the build pack to a DockerFile, and you give it the path to the file in the repo: <img width="856" height="436" alt="02" src="https://github.com/user-attachments/assets/1a1b18a8-8748-4a70-b453-67e33915cb04" /> When you deploy, it starts building the Docker image, and I end up with this issue in the logs and it ends up being an unhealthy deployment. I'm running a VPS with Ubuntu 24.04 and Coolify is the base install. Currently this server's running n8n, Baserow and several other apps without issue, so I'm not quite sure how to proceed - and I'm definitely not a server/git guy :) <img width="1123" height="664" alt="03" src="https://github.com/user-attachments/assets/01dda726-e931-4c8a-84c6-5fba17f8dddf" />

…

On Wed, Dec 3, 2025 at 7:07 AM Shamu ***@***.***> wrote: @pfriedl <https://github.com/pfriedl> - I was just thinking the same thing! 🙂 Before we make it a deploy with one click we could just create a docker compose that handles everything. From reading the issues I think here (#1801 <#1801>) it was also discussed to have a Prebuilt Docker Image so if we are able to pull it from a public registry then we could set this up to be a very easy deploy. I want to take a look at it when I have some time but if someone does it faster, then thank you in advance! — Reply to this email directly, view it on GitHub <#1828 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJAJNQYUHNIUROEDX5QRRL373OBNAVCNFSM6AAAAACN3R3KPCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMJUHA3TGOI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[monorkin]

The images you added are broken in Github. Could you re-upload them?
If you have the option to use a regular Docker image, we have those pre-built: ghcr.io/basecamp/fizzy:main

[pfriedl]

Uploaded those initial images. In Coolify, we can't really execute CLI commands. If I use the Docker Image install and add the pull source ghcr.io/basecamp/fizzy:sha256-befd3706c06f8c312e622f276a017751dbd8ba999cd2d286873040f47242341d.sig then I end up with another issue:

[pfriedl]

OK, got a deployment, but there's something up with how the Docker sets up the server.

[pfriedl]

I think what needs to happen is that fizzy is binding to 127.0.0.1 and needs to bind to 0.0.0.0 for Coolify's proxy to reach it. Any ideas?

[monorkin]

The first error looks like a misconfigured image.

Fizzy binds to 0.0.0.0, can you provide some details about the server error?

[eddywashere]

Was tracking #1911 and noticed someone might have had this working in coolify. @arnsteinsm could you share any tips?

[eddywashere]

I missed that the fizzy template is there now. I am having a hard time configuring mailgun, might be a port issue on my host but I am curious what others used if they are using mailgun.

[mydalat]

Hello everyone, I have successfully installed Fizzy on Coolify. You can refer to the following method:

Step 1: Fork Repository

Go to https://github.com/basecamp/fizzy
Click Fork → Create your own copy
Enable SMTP: Edit config/environments/production.rb, add:

config.action_mailer.delivery_method = :smtp config.action_mailer.smtp_settings = { address: ENV["SMTP_ADDRESS"], port: ENV.fetch("SMTP_PORT", 587).to_i, user_name: ENV["SMTP_USERNAME"], password: ENV["SMTP_PASSWORD"], authentication: ENV.fetch("SMTP_AUTHENTICATION", "plain").to_sym, enable_starttls_auto: ENV.fetch("SMTP_ENABLE_STARTTLS", "true") == "true" }

Step 2: Create Resource on Coolify

1. Projects → Select or create new project
2. + New Resource → Public Repository
3. Enter your forked repo URL: https://github.com/YOUR_USERNAME/fizzy
4. Build Pack: Dockerfile
5. Branch: main
6. Base Directory: /
7. Click Continue

---

Step 3: Configure Domain & Environment

Domain:

kanban.yourdomain.com



`MAILER_FROM_ADDRESS=
RAILS_ENV=production
SECRET_KEY_BASE=(generate with openssl rand -hex 64)
SMTP_ADDRESS=
SMTP_AUTHENTICATION=plain
SMTP_ENABLE_STARTTLS=true
SMTP_PASSWORD=
SMTP_PORT=587
SMTP_USERNAME=
SOLID_QUEUE_IN_PUMA=true`

Step 4: Add Persistent Storage

Go to Persistent Storage → Add Volume Mount:

Volume Name : fizzy-storage
Source Path : /data/fizzy/storage
Destination Path : /rails/storage


Step 5: Deploy

Click Save
Click Deploy
Wait 3-5 minutes for build
Access your domain: https://kanban.yourdomain.com