Self-host Rallly with Levelrail
Find a time that works for everyone with polls for scheduling meetings and events.
- Authorlukevella
- LicenceAGPL-3.0-or-later
- Memory256 MiB
- Archarm64
- Services2
How to self-host Rallly
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpinelukevella/rallly:4.15.2
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 2 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.
Rallly requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-or-later, network copyleft (agpl) 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 3000 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 Rallly. 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 Rallly docs page.
Deploy Rallly your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Rallly from the CLI
levelrail-cli templates deploy rallly --name my-rallly Deploy Rallly with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/rallly/deploy Rallly configuration
Rallly services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | rallly_db_data -> /var/lib/postgresql/data |
| rallly | lukevella/rallly:4.15.2 | 3000 | none |
Rallly environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Generated at deploy |
| DATABASE_URL | rallly | Generated at deploy |
| NEXT_PUBLIC_BASE_URL | rallly | Preset by the template |
| SECRET_PASSWORD | rallly | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: rallly_db_data -> /var/lib/postgresql/data
Rallly FAQ
How much memory does Rallly need?
The catalog lists about 256 MiB of memory for Rallly across its 2 services.
Does Rallly run on arm64?
For Rallly, an arm64 image is published; amd64 is image published.
What licence is Rallly under?
Rallly is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Rallly need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Rallly bundle?
The template includes Postgres, running as its own service.
Which ports does Rallly use?
Rallly listens on port 3000 inside the stack.
Where does Rallly keep its data?
In a named volume: rallly_db_data mounted at /var/lib/postgresql/data.
Can I deploy Rallly on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id rallly for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, lukevella/rallly:4.15.2 is what you deploy there.