Self-host Campfire with Levelrail
Basecamp's open-source group chat app: rooms, direct messages, and file sharing, self-hosted as one container.
- Authorbasecamp
- LicenceMIT
- Memory256 MiB
- Archarm64
- Services1
How to self-host Campfire
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/basecamp/once-campfire:main
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 80.
-
Fill in the secrets
1 secret is generated and stored encrypted, 3 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Campfire requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 80
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 80 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Campfire. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Campfire docs page.
Deploy Campfire your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Campfire from the CLI
levelrail-cli templates deploy campfire --name my-campfire Deploy Campfire with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/campfire/deploy Campfire configuration
Campfire services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| campfire | ghcr.io/basecamp/once-campfire:main | 80 | campfire_storage -> /rails/storage |
Campfire environment variables
| Variable | Service | Value |
|---|---|---|
| DISABLE_SSL | campfire | Preset by the template |
| SECRET_KEY_BASE | campfire | Generated at deploy |
| SKIP_TELEMETRY | campfire | Preset by the template |
| SSL_DOMAIN | campfire | Preset by the template |
Ports and volumes
- Ports
- 80
- Volumes
- 1 named mount: campfire_storage -> /rails/storage
Campfire FAQ
How much memory does Campfire need?
The catalog lists about 256 MiB of memory for Campfire.
Does Campfire run on arm64?
For Campfire, an arm64 image is published; amd64 is image published.
What licence is Campfire under?
Campfire is licensed under MIT, which is permissive, with few conditions on reuse.
Does Campfire need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Campfire use?
Campfire listens on port 80 inside the stack.
Where does Campfire keep its data?
In a named volume: campfire_storage mounted at /rails/storage.
Can I deploy Campfire on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Campfire, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/basecamp/once-campfire:main is what you deploy there.