Deploy on Coolify
Coolify can deploy Day Planner straight from the repository’s docker-compose.yml, which is written for it: Coolify’s Traefik proxy serves it over HTTPS on your domain.
Create the application
Section titled “Create the application”- In Coolify, open your project and select + New Resource.
- Choose Public Repository and enter
https://github.com/Deejpotter/day-planner(or your fork). - Set Branch to
main, Build Pack to Docker Compose, Base Directory to/and Docker Compose Location to/docker-compose.yml. - Give the app service your domain with the container port, for example
https://tasks.example.com:8303. The app listens on 8303; Traefik serves it on 443.
Set the environment variables
Section titled “Set the environment variables”In the application’s Environment Variables tab, set at least:
| Variable | Value |
|---|---|
POSTGRES_PASSWORD |
A long random string |
BETTER_AUTH_SECRET |
Output of openssl rand -base64 32 |
BETTER_AUTH_URL |
https://tasks.example.com |
Add ADMIN_EMAIL and ADMIN_PASSWORD if you want to skip the setup page. Every other setting is in the configuration reference.
Deploy
Section titled “Deploy”Select Deploy. The first build takes around five minutes. When it finishes, Coolify’s health check calls /api/health, and the container shows as healthy.
If you didn’t set ADMIN_EMAIL, open the application’s Logs, find setup_token=, and open your domain to finish first-run setup.
Automatic deploys
Section titled “Automatic deploys”Enable Auto Deploy to redeploy on every push to the branch. Database migrations run when the new container starts, before it serves traffic.
See also
Section titled “See also”- Reverse proxy and client IPs: settings if Cloudflare sits in front of Coolify
- Backups and restore: back up the Postgres volume
- Upgrading: what happens when a new version deploys