feat(ops): docker compose stack for one-command boot #57
No reviewers
Labels
No labels
area:auth
area:docs
area:imap
area:model
area:ops
area:search
area:security
area:smtp
area:ui
priority:p0
priority:p1
priority:p2
type:bug
type:chore
type:feature
type:test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ariejan/envoy!57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-5-docker-compose"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #5.
What
docker-compose.ymlwiring app + Postgres 17 + dedicated Solid Queue worker.env.exampletemplate forRAILS_MASTER_KEYandENVOY_DATABASE_PASSWORD.gitignoreallows.env.examplethrough the/.env*excludeDecisions
SOLID_QUEUE_IN_PUMA). Matches PLAN ops posture for supervised workers; web restarts don't stall the queue.pg_data,storage,log.Test plan
docker compose configvalidates (done locally)cp .env.example .env, fill in values,docker compose up --build -dboots cleanlydocker compose logs jobsshows Solid Queue supervisor runningdocker compose down && docker compose up -dpreserves dataView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.