Repository navigation
Deployment
Filmlog ships as one Docker image that runs three roles: web app, queue worker and scheduler. PostgreSQL runs separately.
Dockerfile builds a production image based on serversideup/php:8.5-fpm-nginx-alpine:
- Composer dependencies without dev packages and an authoritative class map
- Frontend assets with Vite and Tailwind
- Runtime with the
intlextension; on start the container runs migrations and caches config, routes, events and views (AUTORUN_ENABLED=true)
The image listens on port 8080 and answers /up for health checks.
.github/workflows/build.yml:
- Pull requests: Pint and the test suite against a PostgreSQL service. Fork PRs get no secrets.
-
Push to
main, tagsv*, weekly schedule, manual run: tests, then build and push to the GitHub Container Registry (ghcr.io/<owner>/filmlog). A red test never produces a newlatest. -
Deploy: with the repository variable
AUTO_DEPLOY=true, a successful build triggers the Coolify deploy webhook (POST, secretsCOOLIFY_WEBHOOKandCOOLIFY_TOKEN).
The weekly build picks up the newest PHP patch release of the base image.
deploy/docker-compose.coolify.yml is pasted into a Coolify "Docker Compose Empty" resource. Coolify does not read it from the repository, so paste it again after it changes.
- Three services from the same image:
app(with migrations),worker(queue:work --tries=3 --timeout=120) andscheduler(schedule:work) - All three share the volume
app-storage(uploads such as Trakt ZIPs are written byappand read byworker) - PostgreSQL 17 is its own Coolify resource. The services join the external network
coolifyto reach it; setDB_HOSTto its internal host name - Set every
${…}variable under Environment Variables, see Configuration - Point your domain at the
appservice, port 8080 - Coolify must be able to pull from GHCR:
docker login ghcr.ioon the server with a token that hasread:packages
- PostgreSQL resource with daily backups
- Docker Compose resource with the compose file and all variables, including
APP_URLwithhttps://andFILMLOG_ADMIN_EMAIL - Domain and TLS in Coolify
- Repository secrets
COOLIFY_WEBHOOK,COOLIFY_TOKENand variableAUTO_DEPLOY=true - First deploy, then log in with a login link and add a passkey
| Time | Task |
|---|---|
| 03:15 | Plex library sync (only when Plex is configured) |
| 03:30 | TMDB refresh for films on lists and films older than 30 days |
| 03:45 | Collections of seen films |
| 04:00 | Delete failed jobs older than 14 days |
| 04:15 | Delete Trakt ZIPs seven days after the import |
Every push to main deploys. Versioned releases are created deliberately, never automatically:
- Pick the next version following semantic versioning (
v0.1.0,v0.2.0, …). - Create the release on GitHub (or
gh release create vX.Y.Z --generate-notes). The tag starts the build workflow, which publishes the image asghcr.io/<owner>/filmlog:X.Y.Zin addition tolatest. - To pin a server to a version, set
APP_TAG=X.Y.Zin Coolify instead oflatest.
Release notes list new features, fixes and anything that needs action on the server (new variables, a changed compose file).
Generated from handbuch/ by scripts/build-wiki.py. Please edit the files in the repository, not this wiki.