Install on Dockge
Manage OpenPost as a Dockge stack from the canonical Compose file.
Create a Dockge stack with the supplied deploy/dockge/compose.yaml. Dockge keeps the Compose file and .env on the host, so the same stack also works with the Docker Compose CLI. The image supports x86_64 and ARM64 hosts.
What you need
- Dockge connected to a Docker host. Its default stacks directory is
/opt/stacks. - A public HTTPS address before you connect social accounts.
Create the stack
- In Dockge, choose Create Stack and name it
openpost. Stack names accept lowercase letters, numbers, underscores, and hyphens. - Paste
deploy/dockge/compose.yamlinto the stack editor. - Add the public URLs and secrets to the stack's
.env, with one line per${...}variable. - Deploy the stack. Dockge stores its files under
/opt/stacks/openpost/by default. Keep OpenPost secrets in the stack.env, not a sharedglobal.env. - Verify readiness:
curl https://post.example.com/api/v1/readyExpect "status":"ready" and "database":"ok". Check the stack logs if it fails.
Open the app and create the first account. It becomes the instance administrator. The stack stores SQLite and media in the openpost_data volume.
Upgrade and back up
Pin the image to a release tag before production use. Back up the openpost_data volume and private environment settings before changing the tag and redeploying. Also keep compose.yaml and .env from the stack directory. Follow the maintenance guide for readiness checks and restores. Database migrations can require restoring a matching backup when rolling back.
After installation, configure social integrations and email delivery if needed.