Weblate
Weblate is a web-based continuous localization system with tight version control integration. Translators work in the browser while Weblate pulls from and pushes to your Git or Mercurial repositories, with quality checks, translation memory, machine translation, glossaries and add-ons across dozens of file formats.
Weblate
In Development
This script is currently in active development and may be unstable or incomplete. Use in production environments is not recommended.
This script is currently in active development and may be unstable or incomplete. Use in production environments is not recommended.
Installation
Default install:
1
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/weblate.sh)"
Default Credentials
| Username | Password |
|---|---|
admin | None |
Notes
The admin password is generated at install and stored as WEBLATE_ADMIN_PASSWORD in /opt/weblate_data/weblate.env. Weblate does not read that value, so change the password from your profile afterwards, or reset it with
weblate createadmin --update.Settings come from upstream's environment-driven weblate.settings_docker: add WEBLATE_* variables from the Docker documentation to /opt/weblate_data/weblate.env (for example WEBLATE_EMAIL_HOST for outgoing mail, or WEBLATE_SITE_DOMAIN and WEBLATE_ENABLE_HTTPS=1 behind an HTTPS proxy), then run
systemctl restart weblate weblate-celery. Python-level overrides go in /opt/weblate_data/settings-override.py.No mail server is configured, so registration and notification e-mails fail until WEBLATE_EMAIL_HOST is set.
Management commands need the environment loaded:
set -a; . /opt/weblate_data/weblate.env; set +a; /opt/weblate/.venv/bin/weblate .Celery runs two worker processes (--concurrency=2 in weblate-celery.service). Raise it together with CPU and RAM if Weblate reports long task queues.
Repositories, uploads and the secret key live in /opt/weblate_data. Back it up together with the PostgreSQL database.