Self-host Traggo with Levelrail
Self-hosted time tracking with tags instead of projects, a timeline and dashboards. Runs a single container with data on a volume.
- Authortraggo
- LicenceGPL-3.0-only
- Memory64 MiB
- Services1
How to self-host Traggo
-
Pull the images
One image is pulled on your server.
Show images
traggo/server:0.8.3
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 3030.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is 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.
After the first start
- Sign in as admin with the generated password shown in the deployment variables, then create tags and start a timer.
Traggo requirements
- Memory
- About 64 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3030
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-only, copyleft 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 Traggo. 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 Traggo docs page.
Deploy Traggo your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Traggo from the CLI
levelrail-cli templates install traggo --name my-traggo Deploy Traggo with the API
curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
https://levelrail.example.com/api/v1/service-templates/traggo/install \
-d '{
"name": "my-traggo"
}' Traggo configuration
Traggo services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| traggo | traggo/server:0.8.3 | 3030 | data -> /opt/traggo/data |
Traggo environment variables
| Variable | Service | Value |
|---|---|---|
| TRAGGO_DEFAULT_USER_NAME | traggo | Preset by the template |
| TRAGGO_DEFAULT_USER_PASS | traggo | Generated at deploy |
Ports and volumes
- Ports
- 3030
- Volumes
- 1 named mount: data -> /opt/traggo/data
Traggo FAQ
How much memory does Traggo need?
The catalog lists about 64 MiB of memory for Traggo.
Does Traggo run on arm64?
For Traggo, arm64 support is not confirmed; amd64 is unknown.
What licence is Traggo under?
Traggo is licensed under GPL-3.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does Traggo need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Traggo use?
Traggo listens on port 3030 inside the stack.
Where does Traggo keep its data?
In a named volume: data mounted at /opt/traggo/data.
Can I deploy Traggo 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 Traggo, 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 traggo/server:0.8.3 is what you deploy there.