Self-host Weblate with Levelrail
A continuous localization system for translating software with a web-based editor and review flow.
- AuthorWeblateOrg
- LicenceGPL-3.0-or-later
- Memory1 GiB
- Archarm64
- Services3
How to self-host Weblate
-
Pull the images
3 images are pulled on your server.
Show images
postgres:16-alpineredis:7-alpineweblate/weblate:5.15
-
Create the app
3 services start in a single Compose app, with 4 named volume mounts for your data, on port 8080.
-
Fill in the secrets
5 secrets are generated and stored encrypted, 8 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.
Weblate requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-3.0-or-later, copyleft 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 8080 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 Weblate. 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 Weblate docs page.
Deploy Weblate your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Weblate from the CLI
levelrail-cli templates deploy weblate --name my-weblate Deploy Weblate with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/weblate/deploy Weblate configuration
Weblate services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | weblate_db_data -> /var/lib/postgresql/data |
| redis | redis:7-alpine | none | weblate_redis_data -> /data |
| weblate | weblate/weblate:5.15 | 8080 | weblate_data -> /app/dataweblate_cache -> /app/cache |
Weblate 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 |
| REDIS_PASSWORD | redis | Generated at deploy |
| POSTGRES_DATABASE | weblate | Preset by the template |
| POSTGRES_HOST | weblate | Preset by the template |
| POSTGRES_PASSWORD | weblate | Generated at deploy |
| POSTGRES_USER | weblate | Preset by the template |
Show all 13 variables
- REDIS_HOSTweblatePreset by the template
- REDIS_PASSWORDweblateGenerated at deploy
- REDIS_PORTweblatePreset by the template
- WEBLATE_ADMIN_PASSWORDweblateGenerated at deploy
- WEBLATE_SITE_DOMAINweblatePreset by the template
Ports and volumes
- Ports
- 8080
- Volumes
- 4 named mounts: weblate_db_data -> /var/lib/postgresql/data, weblate_redis_data -> /data, weblate_data -> /app/data, weblate_cache -> /app/cache
Weblate FAQ
How much memory does Weblate need?
The catalog lists about 1 GiB of memory for Weblate across its 3 services.
Does Weblate run on arm64?
For Weblate, an arm64 image is published; amd64 is image published.
What licence is Weblate under?
Weblate is licensed under GPL-3.0-or-later, which is copyleft, so changes you distribute must be shared under the same terms.
Does Weblate need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Weblate bundle?
The template includes Postgres and Redis, running as its own service.
Which ports does Weblate use?
Weblate listens on port 8080 inside the stack.
Where does Weblate keep its data?
In named volumes: weblate_db_data mounted at /var/lib/postgresql/data, weblate_redis_data mounted at /data, weblate_data mounted at /app/data and weblate_cache mounted at /app/cache.
Can I deploy Weblate 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 weblate for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, redis:7-alpine, weblate/weblate:5.15 is what you deploy there.