Self-host Reactive Resume with Levelrail
A free resume builder with live preview, templates and PDF export, backed by Postgres. MIT licensed. Register an account on first open, uploads are stored on a local volume.
- Authorreactive-resume
- LicenceMIT
- Memory768 MiB
- Archarm64
- Services2
How to self-host Reactive Resume
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpineamruthpillai/reactive-resume:v6.0.9
-
Create the app
2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3000.
-
Fill in the secrets
3 secrets are generated and stored encrypted, 4 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.
Reactive Resume requirements
- Memory
- About 768 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
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Reactive Resume. 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 Reactive Resume docs page.
Deploy Reactive Resume your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Reactive Resume from the CLI
levelrail-cli templates install reactive-resume --name my-reactive-resume Deploy Reactive Resume with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/reactive-resume/install \
-d '{
"name": "my-reactive-resume"
}' Reactive Resume configuration
Reactive Resume services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | pgdata -> /var/lib/postgresql/data |
| reactive-resume | amruthpillai/reactive-resume:v6.0.9 | 3000 | data -> /app/data |
Reactive Resume environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| APP_URL | reactive-resume | Preset by the template |
| AUTH_SECRET | reactive-resume | Generated at deploy |
| DATABASE_URL | reactive-resume | Generated at deploy |
| PORT | reactive-resume | Preset by the template |
Ports and volumes
- Ports
- 3000
- Volumes
- 2 named mounts: pgdata -> /var/lib/postgresql/data, data -> /app/data
Reactive Resume FAQ
How much memory does Reactive Resume need?
The catalog lists about 768 MiB of memory for Reactive Resume across its 2 services.
Does Reactive Resume run on arm64?
For Reactive Resume, an arm64 image is published; amd64 is image published.
What licence is Reactive Resume under?
Reactive Resume is licensed under MIT, which is permissive, with few conditions on reuse.
Does Reactive Resume need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Reactive Resume bundle?
The template includes Postgres, running as its own service.
Which ports does Reactive Resume use?
Reactive Resume listens on port 3000 inside the stack.
Where does Reactive Resume keep its data?
In named volumes: pgdata mounted at /var/lib/postgresql/data and data mounted at /app/data.
Can I deploy Reactive Resume 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 reactive-resume for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, amruthpillai/reactive-resume:v6.0.9 is what you deploy there.