Weblate/weblate
0
0
Fork 0
mirror of https://gh.wpcy.net/https://github.com/WeblateOrg/weblate.git synced 2026-04-29 01:31:44 +08:00
Code Issues Projects Releases Packages Activity Actions 4
weblate/docs/admin/install/docker.rst
Michal Čihař bd2de18de9 feat(vcs): tighter validation of VCS URLs 
The validation now follows the same logic as existing for other outbound
traffic.
2026-04-09 16:13:23 +02:00

2591 lines
75 KiB
ReStructuredText
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Installing using Docker
=======================
With dockerized Weblate deployment you can get your personal Weblate instance
up and running in seconds. All of Weblate's dependencies are already included.
PostgreSQL is set up as the default database and Valkey as a caching backend.
.. include:: steps/hw.rst
.. _docker-deploy:
Installation
------------
.. hint::
The following examples assume you have a working Docker environment, with
``docker-compose-plugin`` installed. Please check the Docker documentation
for instructions.
This creates a Weblate deployment server via HTTP, so you should place it
behind HTTPS terminating proxy. You can also deploy with a HTTPS proxy, see
:ref:`docker-https-portal`. For larger setups, please see
:ref:`docker-scaling`.
1. Clone the weblate-docker repo:
.. code-block:: sh
git clone https://github.com/WeblateOrg/docker-compose.git weblate-docker
cd weblate-docker
2. Create a :file:`docker-compose.override.yml` file with your settings.
See :ref:`docker-environment` for full list of environment variables.
.. literalinclude:: ../../../weblate/examples/docker-compose.yml
:language: yaml
.. note::
If :envvar:`WEBLATE_ADMIN_PASSWORD` is not set, the admin user is created with
a random password shown on first startup.
The provided example makes Weblate listen on port 80, edit the port
mapping in the :file:`docker-compose.override.yml` file to change it.
3. Start Weblate containers:
.. code-block:: sh
docker compose up
Enjoy your Weblate deployment, it's accessible on port 80 of the ``weblate`` container.
.. seealso::
:ref:`invoke-manage`
Choosing Docker image registry
------------------------------
Weblate containers are published to following registries:
* Docker Hub, see https://hub.docker.com/r/weblate/weblate
* GitHub Packages registry, see https://github.com/WeblateOrg/docker/pkgs/container/weblate
.. note::
All examples currently fetch images from Docker Hub, please adjust the
configuration accordingly to use a different registry.
Choosing Docker image tag
-------------------------
Please choose a tag that matches your environment and expectations:
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
| Tag name | Description | Use case |
+=========================================+============================================================================================================+=============================================================================+
|``latest`` | Weblate stable release, matches latest tagged release | Rolling updates in a production environment |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``<MAJOR>`` | Weblate stable release | Rolling updates within a major version in a production environment |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``<MAJOR>.<MINOR>`` | Weblate stable release | Rolling updates within a minor version in a production environment |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``<MAJOR>.<MINOR>.<PATCH>.<BUILD>`` | Weblate stable release | Well defined deploy in a production environment |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``edge`` | Weblate stable release with development changes in the Docker container (for example updated dependencies) | Rolling updates in a staging environment |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``edge-<DATE>-<SHA>`` | Weblate stable release with development changes in the Docker container (for example updated dependencies) | Well defined deploy in a staging environment |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``bleeding`` | Development version Weblate from Git | Rolling updates to test upcoming Weblate features |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
|``bleeding-<DATE>-<SHA>`` | Development version Weblate from Git | Well defined deploy to test upcoming Weblate features |
+-----------------------------------------+------------------------------------------------------------------------------------------------------------+-----------------------------------------------------------------------------+
Every image is tested by our CI before it gets published, so even the `bleeding` version should be quite safe to use.
Full list of published tags can be found at `GitHub Packages`_
.. _GitHub Packages: https://github.com/WeblateOrg/docker/pkgs/container/weblate/versions?filters%5Bversion_type%5D=tagged
.. _docker-ssl:
Docker container with HTTPS support
-----------------------------------
Please see :ref:`docker-deploy` for generic deployment instructions, this
section only mentions differences compared to it.
.. _docker-ssl-proxy:
SSL terminating proxy
+++++++++++++++++++++
SSL can be terminated outside Weblate container. To make this work well
together, several headers need to be passed to the container so that it is
aware of its actual environment. In more detail, these headers are described in
:ref:`reverse-proxy`.
.. code-block:: nginx
:caption: Example nginx reverse proxy configuration for a Docker container.
location / {
proxy_pass http://127.0.0.1:8080;
proxy_read_timeout 3600s;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
}
.. code-block:: sh
:caption: Docker container environment for external SSL termination.
WEBLATE_ENABLE_HTTPS=1
WEBLATE_IP_PROXY_HEADER=HTTP_X_FORWARDED_FOR
Using own SSL certificates
++++++++++++++++++++++++++
In case you have own SSL certificate you want to use, simply place the files
into the Weblate data volume (see :ref:`docker-volume`):
* :file:`ssl/fullchain.pem` containing the certificate including any needed CA certificates
* :file:`ssl/privkey.pem` containing the private key
Both of these files must be owned by the same user as the one starting the docker container and have file mask set to ``600`` (readable and writable only by the owning user).
Additionally, Weblate container will now accept SSL connections on port 4443,
you will want to include the port forwarding for HTTPS in docker compose override:
.. code-block:: yaml
version: '3'
services:
weblate:
ports:
- 80:8080
- 443:4443
If you already host other sites on the same server, it is likely ports ``80`` and ``443`` are used by a reverse proxy, such as NGINX. To pass the HTTPS connection from NGINX to the docker container, you can use the following configuration:
.. code-block:: nginx
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name <SITE_URL>;
ssl_certificate /etc/letsencrypt/live/<SITE>/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/<SITE>/privkey.pem;
location / {
proxy_set_header HOST $host;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_pass https://127.0.0.1:<EXPOSED_DOCKER_PORT>;
}
}
Replace ``<SITE_URL>``, ``<SITE>`` and ``<EXPOSED_DOCKER_PORT>`` with actual values from your environment.
.. _docker-https-portal:
Automatic SSL certificates using Let’s Encrypt
++++++++++++++++++++++++++++++++++++++++++++++
In case you want to use `Let’s Encrypt <https://letsencrypt.org/>`_
automatically generated SSL certificates on public installation, you need to
add a reverse HTTPS proxy an additional Docker container, `https-portal
<https://hub.docker.com/r/steveltn/https-portal/>`_ will be used for that.
This is made use of in the :file:`docker-compose-https.yml` file. Then create
a :file:`docker-compose-https.override.yml` file with your settings:
.. code-block:: yaml
version: '3'
services:
weblate:
environment:
WEBLATE_EMAIL_HOST: smtp.example.com
WEBLATE_EMAIL_HOST_USER: user
WEBLATE_EMAIL_HOST_PASSWORD: pass
WEBLATE_SITE_DOMAIN: weblate.example.com
WEBLATE_ADMIN_PASSWORD: password for admin user
https-portal:
environment:
DOMAINS: 'weblate.example.com -> http://weblate:8080'
Whenever invoking :program:`docker compose` you need to pass both files to it,
and then do:
.. code-block:: console
docker compose -f docker-compose-https.yml -f docker-compose-https.override.yml build
docker compose -f docker-compose-https.yml -f docker-compose-https.override.yml up
.. _upgrading-docker:
Upgrading the Docker container
------------------------------
Usually it is good idea to only update the Weblate container and keep the PostgreSQL
container at the version you have, as upgrading PostgreSQL is quite painful and in most
cases does not bring many benefits.
You can do this by sticking with the existing docker-compose and just pull
the latest images and then restart:
.. code-block:: sh
# Fetch latest versions of the images
docker compose pull
# Stop and destroy the containers
docker compose down
# Spawn new containers in the background
docker compose up -d
# Follow the logs during upgrade
docker compose logs -f
The Weblate database should be automatically migrated on first startup, and there
should be no need for additional manual actions.
.. note::
Upgrades across major versions are not supported by Weblate. For example,
if you are on 3.x series and want to upgrade to 4.x, first upgrade to the
latest 4.0.x-y image (at time of writing this it is the ``4.0.4-5``), which
will do the migration and then continue upgrading to newer versions.
You might also want to update the ``docker-compose`` repository, though it's
not needed in most case. See :ref:`docker-postgres-upgrade` for upgrading the PostgreSQL server.
.. _docker-postgres-upgrade:
Upgrading PostgreSQL container
++++++++++++++++++++++++++++++
.. note::
PostgreSQL 18 changed the default data directory inside the container. A
common older setup mounted the database volume at
``/var/lib/postgresql/data``, while PostgreSQL 18 now uses
``/var/lib/postgresql`` by default.
If you are upgrading from an older version, either update the mount target
in your Docker configuration to the new path, or keep the old mount target
and set ``PGDATA`` accordingly.
Leaving the old mount target unchanged without setting ``PGDATA`` can cause
PostgreSQL to write its data outside the persisted volume.
See `PGDATA documentation <https://hub.docker.com/_/postgres#pgdata>`_ for
more information.
PostgreSQL containers do not support automatic upgrading between version, you
need to perform the upgrade manually. Following steps show one of the options
of upgrading.
.. seealso::
https://github.com/docker-library/postgres/issues/37
1. Stop Weblate container:
.. code-block:: shell
docker compose stop weblate cache
2. Backup the database:
.. code-block:: shell
docker compose exec database pg_dumpall --clean --if-exists --username weblate > backup.sql
3. Stop the database container:
.. code-block:: shell
docker compose stop database
4. Remove the PostgreSQL volume:
.. code-block:: shell
docker compose rm -v database
docker volume remove weblate-docker_postgres-data
.. hint::
The volume name contains name of the Docker Compose project, which is by
default the directory name what is ``weblate-docker`` in this documentation.
5. Adjust :file:`docker-compose.yml` to use new PostgreSQL version.
6. Start the database container:
.. code-block:: shell
docker compose up -d database
7. Restore the database from the backup:
.. code-block:: shell
cat backup.sql | docker compose exec -T database psql --username weblate --dbname weblate
.. hint::
Please check that the database name matches :envvar:`POSTGRES_DB`.
8. (Optional) Update password for the Weblate user. This might be needed when migrating to PostgreSQL 14 or 15 as way of storing passwords has been changed:
.. code-block:: shell
docker compose exec -T database psql --username weblate --dbname weblate -c "ALTER USER weblate WITH PASSWORD 'weblate'"
.. hint::
Please check that the database name matches :envvar:`POSTGRES_DB`.
9. Start all remaining containers:
.. code-block:: shell
docker compose up -d
.. _docker-admin-login:
Admin sign in
-------------
After container setup, you can sign in as `admin` user with password provided
in :envvar:`WEBLATE_ADMIN_PASSWORD`, or a random password generated on first
start if that was not set.
To reset `admin` password, restart the container with
:envvar:`WEBLATE_ADMIN_PASSWORD` set to new password.
.. seealso::
* :envvar:`WEBLATE_ADMIN_PASSWORD`
* :envvar:`WEBLATE_ADMIN_NAME`
* :envvar:`WEBLATE_ADMIN_EMAIL`
Number of processes and memory consumption
------------------------------------------
The number of worker processes for both WSGI and Celery is determined
automatically based on number of CPUs. This works well for most cloud virtual
machines as these typically have few CPUs and good amount of memory.
In case you have a lot of CPU cores and hit out of memory issues, try reducing
number of workers:
.. code-block:: yaml
environment:
WEBLATE_WORKERS: 2
You can also fine-tune individual worker categories:
.. code-block:: yaml
environment:
WEB_WORKERS: 4
CELERY_MAIN_OPTIONS: --concurrency 2
CELERY_NOTIFY_OPTIONS: --concurrency 1
CELERY_TRANSLATE_OPTIONS: --concurrency 1
Memory usage can be further reduced by running only a single Celery process:
.. code-block:: yaml
environment:
CELERY_SINGLE_PROCESS: 1
.. seealso::
* :envvar:`WEBLATE_WORKERS`
* :envvar:`CELERY_MAIN_OPTIONS`
* :envvar:`CELERY_NOTIFY_OPTIONS`
* :envvar:`CELERY_MEMORY_OPTIONS`
* :envvar:`CELERY_TRANSLATE_OPTIONS`
* :envvar:`CELERY_BACKUP_OPTIONS`
* :envvar:`CELERY_BEAT_OPTIONS`
* :envvar:`CELERY_SINGLE_PROCESS`
* :envvar:`WEB_WORKERS`
.. _docker-scaling:
Scaling horizontally
--------------------
.. versionadded:: 4.6
You can run multiple Weblate containers to scale the service horizontally. The
:file:`/app/data` volume has to be shared by all containers, it is recommended
to use cluster filesystem such as GlusterFS for this. The :file:`/app/cache`
volume should be separate for each container.
Each Weblate container has defined role using :envvar:`WEBLATE_SERVICE`
environment variable. Please follow carefully the documentation as some of the
services should be running just once in the cluster, and the order of the
services matters as well.
You can find example setup in the ``docker-compose`` repo as
`docker-compose-split.yml
<https://github.com/WeblateOrg/docker-compose/blob/main/docker-compose-split.yml>`__.
.. _docker-environment:
Docker environment variables
----------------------------
Many of Weblate's :ref:`config` can be set in the Docker container using
the environment variables described below.
If you need to define a setting not exposed through Docker environment
variables, see :ref:`docker-custom-config`.
.. _docker-secrets:
Passing secrets
+++++++++++++++
.. versionadded:: 5.0
Weblate container supports passing secrets as files. To utilize that, append
``_FILE`` suffix to the environment variable and pass secret file via Docker.
Related :file:`docker-compose.yml` might look like:
.. code-block:: yaml
services:
weblate:
environment:
POSTGRES_PASSWORD_FILE: /run/secrets/db_password
secrets:
- db_password
database:
environment:
POSTGRES_PASSWORD_FILE: /run/secrets/db_password
secrets:
- db_password
secrets:
db_password:
file: db_password.txt
.. seealso::
`How to use secrets in Docker Compose <https://docs.docker.com/compose/how-tos/use-secrets/>`_
Generic settings
++++++++++++++++
.. envvar:: WEBLATE_DEBUG
Configures Django debug mode using :setting:`DEBUG`.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_DEBUG: 1
.. seealso::
:ref:`production-debug`
.. envvar:: WEBLATE_LOGLEVEL
Configures the logging verbosity. Set this to ``DEBUG`` to get more detailed logs.
Defaults to ``INFO`` when :envvar:`WEBLATE_DEBUG` is turned off, ``DEBUG`` is used when debug mode is turned on.
For more silent logging use ``ERROR`` or ``WARNING``.
.. envvar:: WEBLATE_LOGLEVEL_DATABASE
Configures the logging of the database queries verbosity.
.. envvar:: WEBLATE_LOG_GELF_HOST
.. versionadded:: 5.9
Configures remote logging using GELF TCP connection. Can be used to integrate with Graylog.
.. envvar:: WEBLATE_LOG_GELF_PORT
.. versionadded:: 5.9
Use custom port for :envvar:`WEBLATE_LOG_GELF_HOST`, defaults to 12201.
.. envvar:: WEBLATE_SITE_TITLE
Changes the site-title shown in the header of all pages.
.. envvar:: WEBLATE_SITE_DOMAIN
Configures the site domain. This parameter is required.
Include port if using a non-standard one.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_SITE_DOMAIN: example.com:8080
.. seealso::
* :ref:`production-site`
* :setting:`SITE_DOMAIN`
.. envvar:: WEBLATE_ADMIN_NAME
.. envvar:: WEBLATE_ADMIN_EMAIL
Configures the site-admin's name and e-mail. It is used for both
:setting:`ADMINS` setting and creating `admin` user (see
:envvar:`WEBLATE_ADMIN_PASSWORD` for more info on that).
**Example:**
.. code-block:: yaml
environment:
WEBLATE_ADMIN_NAME: Weblate admin
WEBLATE_ADMIN_EMAIL: noreply@example.com
.. seealso::
* :ref:`docker-admin-login`
* :ref:`production-admins`
* :setting:`ADMINS`
.. envvar:: WEBLATE_ADMIN_PASSWORD
Sets the password for the `admin` user.
* If not set and `admin` user does not exist, it is created with a random
password shown on first container startup.
* If not set and `admin` user exists, no action is performed.
* If set the `admin` user is adjusted on every container startup to match
:envvar:`WEBLATE_ADMIN_PASSWORD`, :envvar:`WEBLATE_ADMIN_NAME` and
:envvar:`WEBLATE_ADMIN_EMAIL`.
.. warning::
It might be a security risk to store password in the configuration
file. Consider using this variable only for initial setup (or let
Weblate generate random password on initial startup) or for password
recovery.
.. seealso::
* :ref:`docker-admin-login`
* :ref:`docker-secrets`
* :envvar:`WEBLATE_ADMIN_PASSWORD`
* :envvar:`WEBLATE_ADMIN_NAME`
* :envvar:`WEBLATE_ADMIN_EMAIL`
.. envvar:: WEBLATE_ADMIN_NOTIFY_ERROR
Whether to send e-mail to admins upon server error. Turned on by default.
You might want to use other error collection like Sentry or Rollbar and turn this off.
.. seealso::
* :ref:`django:logging-security-implications`
* :envvar:`ROLLBAR_KEY`
* :envvar:`SENTRY_DSN`
.. envvar:: WEBLATE_SERVER_EMAIL
The email address that error messages are sent from.
.. seealso::
* :std:setting:`django:SERVER_EMAIL`
* :ref:`production-email`
.. envvar:: WEBLATE_DEFAULT_FROM_EMAIL
Configures the address for outgoing e-mails.
.. seealso::
* :std:setting:`django:DEFAULT_FROM_EMAIL`
* :ref:`production-email`
.. envvar:: WEBLATE_ADMINS_CONTACT
Configures :setting:`ADMINS_CONTACT`.
.. envvar:: WEBLATE_CONTACT_FORM
Configures contact form behavior, see :setting:`CONTACT_FORM`.
.. envvar:: WEBLATE_ALLOWED_HOSTS
Configures allowed HTTP hostnames using :setting:`ALLOWED_HOSTS`.
Defaults to ``*`` which allows all hostnames.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_ALLOWED_HOSTS: weblate.example.com,example.com
.. seealso::
* :setting:`ALLOWED_HOSTS`
* :ref:`production-hosts`
* :ref:`production-site`
.. envvar:: WEBLATE_REGISTRATION_OPEN
Configures whether registrations are open by toggling :std:setting:`REGISTRATION_OPEN`.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_REGISTRATION_OPEN: 0
.. envvar:: WEBLATE_REGISTRATION_CAPTCHA
.. versionadded:: 5.10
Configures whether captcha is used for registration and other unauthenticated actions, see :std:setting:`REGISTRATION_CAPTCHA`.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_REGISTRATION_CAPTCHA: 0
.. envvar:: WEBLATE_REGISTRATION_ALLOW_BACKENDS
Configure which authentication methods can be used to create new account via
:setting:`REGISTRATION_ALLOW_BACKENDS`.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_REGISTRATION_OPEN: 0
WEBLATE_REGISTRATION_ALLOW_BACKENDS: azuread-oauth2,azuread-tenant-oauth2
.. envvar:: WEBLATE_REGISTRATION_REBIND
.. versionadded:: 4.16
Configures :std:setting:`REGISTRATION_REBIND`.
.. envvar:: WEBLATE_REGISTRATION_ALLOW_DISPOSABLE_EMAILS
.. versionadded:: 5.16.1
Configures :setting:`REGISTRATION_ALLOW_DISPOSABLE_EMAILS`.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_REGISTRATION_ALLOW_DISPOSABLE_EMAILS: 1
.. envvar:: WEBLATE_PROJECT_WEB_RESTRICT_PRIVATE
.. versionadded:: 5.17
Configures :setting:`PROJECT_WEB_RESTRICT_PRIVATE`.
Defaults to enabled.
.. envvar:: WEBLATE_WEBHOOK_RESTRICT_PRIVATE
.. versionadded:: 5.17
Configures :setting:`WEBHOOK_RESTRICT_PRIVATE`.
Defaults to enabled.
.. envvar:: WEBLATE_WEBHOOK_PRIVATE_ALLOWLIST
.. versionadded:: 5.17
Configures :setting:`WEBHOOK_PRIVATE_ALLOWLIST`.
.. envvar:: WEBLATE_TIME_ZONE
Configures the used time zone in Weblate, see :std:setting:`django:TIME_ZONE`.
.. note::
To change the time zone of the Docker container itself, use the ``TZ``
environment variable.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_TIME_ZONE: Europe/Prague
.. envvar:: WEBLATE_ENABLE_HTTPS
Makes Weblate assume it is operated behind a reverse HTTPS proxy, it makes
Weblate use HTTPS in e-mail and API links or set secure flags on cookies.
.. hint::
Please see :setting:`ENABLE_HTTPS` documentation for possible caveats.
.. note::
This does not make the Weblate container accept HTTPS connections, you
need to configure that as well, see :ref:`docker-ssl` for examples.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_ENABLE_HTTPS: 1
.. seealso::
* :setting:`ENABLE_HTTPS`
* :ref:`production-site`
* :envvar:`WEBLATE_SECURE_PROXY_SSL_HEADER`
.. envvar:: WEBLATE_IP_PROXY_HEADER
Lets Weblate fetch the IP address from any given HTTP header. Use this when using
a reverse proxy in front of the Weblate container.
Enables :setting:`IP_BEHIND_REVERSE_PROXY` and sets :setting:`IP_PROXY_HEADER`.
.. note::
The format must conform to Django's expectations. Django
`transforms <https://docs.djangoproject.com/en/2.2/ref/request-response/#django.http.HttpRequest.META>`_
raw HTTP header names as follows:
- converts all characters to uppercase
- replaces any hyphens with underscores
- prepends ``HTTP_`` prefix
So ``X-Forwarded-For`` would be mapped to ``HTTP_X_FORWARDED_FOR``.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_IP_PROXY_HEADER: HTTP_X_FORWARDED_FOR
.. envvar:: WEBLATE_IP_PROXY_OFFSET
.. versionadded:: 5.0.1
Configures :setting:`IP_PROXY_OFFSET`.
.. envvar:: WEBLATE_USE_X_FORWARDED_PORT
.. versionadded:: 5.0.1
A boolean that specifies whether to use the :http:header:`X-Forwarded-Port` header in
preference to the SERVER_PORT META variable. This should only be enabled
if a proxy which sets this header is in use.
.. seealso::
:setting:`django:USE_X_FORWARDED_PORT`
.. note:: This is a boolean setting (use ``"true"`` or ``"false"``).
.. envvar:: WEBLATE_SECURE_PROXY_SSL_HEADER
A tuple representing a HTTP header/value combination that signifies a
request is secure. This is needed when Weblate is running behind a reverse
proxy doing SSL termination which does not pass standard HTTPS headers.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_SECURE_PROXY_SSL_HEADER: HTTP_X_FORWARDED_PROTO,https
.. seealso::
* :ref:`reverse-proxy`
* :setting:`django:SECURE_PROXY_SSL_HEADER`
.. envvar:: WEBLATE_REQUIRE_LOGIN
Enables :setting:`REQUIRE_LOGIN` to enforce authentication on whole Weblate.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_REQUIRE_LOGIN: 1
.. envvar:: WEBLATE_PUBLIC_ENGAGE
Enables :setting:`PUBLIC_ENGAGE`.
.. envvar:: WEBLATE_GOOGLE_ANALYTICS_ID
Configures ID for Google Analytics by changing :setting:`GOOGLE_ANALYTICS_ID`.
.. envvar:: WEBLATE_DEFAULT_PULL_MESSAGE
Configures the default title and message for pull requests via API by changing
:setting:`DEFAULT_PULL_MESSAGE`.
.. seealso::
:ref:`config-pull-message`
.. envvar:: WEBLATE_SIMPLIFY_LANGUAGES
Configures the language simplification policy, see :setting:`SIMPLIFY_LANGUAGES`.
.. envvar:: WEBLATE_HIDE_SHARED_GLOSSARY_COMPONENTS
Hides glossary components when shared to other projects, see :setting:`HIDE_SHARED_GLOSSARY_COMPONENTS`.
.. envvar:: WEBLATE_DEFAULT_ACCESS_CONTROL
Configures the default :ref:`project-access_control` for new projects, see :setting:`DEFAULT_ACCESS_CONTROL`.
.. envvar:: WEBLATE_DEFAULT_TRANSLATION_REVIEW
.. versionadded:: 5.16
Configures the default value for :ref:`project-translation_review`, turned off by default.
.. envvar:: WEBLATE_DEFAULT_SOURCE_REVIEW
.. versionadded:: 5.16
Configures the default value for :ref:`project-source_review`, turned off by default.
.. envvar:: WEBLATE_DEFAULT_RESTRICTED_COMPONENT
Configures the default value for :ref:`component-restricted` for new components, see :setting:`DEFAULT_RESTRICTED_COMPONENT`.
.. envvar:: WEBLATE_DEFAULT_TRANSLATION_PROPAGATION
Configures the default value for :ref:`component-allow_translation_propagation` for new components, see :setting:`DEFAULT_TRANSLATION_PROPAGATION`.
.. envvar:: WEBLATE_DEFAULT_COMMITER_EMAIL
Configures :setting:`DEFAULT_COMMITER_EMAIL`.
.. envvar:: WEBLATE_DEFAULT_COMMITER_NAME
Configures :setting:`DEFAULT_COMMITER_NAME`.
.. envvar:: WEBLATE_DEFAULT_SHARED_TM
Configures :setting:`DEFAULT_SHARED_TM`.
.. envvar:: WEBLATE_DEFAULT_AUTOCLEAN_TM
Configures :setting:`DEFAULT_AUTOCLEAN_TM`.
.. envvar:: WEBLATE_COMMIT_PENDING_HOURS
Configures the default value for :ref:`component-commit_pending_age` for new components, see :setting:`COMMIT_PENDING_HOURS`.
.. envvar:: WEBLATE_GPG_IDENTITY
Configures GPG signing of commits, see :setting:`WEBLATE_GPG_IDENTITY`.
.. seealso::
:ref:`gpg-sign`
.. envvar:: WEBLATE_URL_PREFIX
Configures URL prefix where Weblate is running, see :setting:`URL_PREFIX`.
.. envvar:: WEBLATE_STATIC_URL
Configures URL prefix for static files served from :setting:`CACHE_DIR`.
.. envvar:: WEBLATE_SILENCED_SYSTEM_CHECKS
Configures checks which you do not want to be displayed, see
:setting:`django:SILENCED_SYSTEM_CHECKS`.
.. envvar:: WEBLATE_CSP_SCRIPT_SRC
.. envvar:: WEBLATE_CSP_IMG_SRC
.. envvar:: WEBLATE_CSP_CONNECT_SRC
.. envvar:: WEBLATE_CSP_STYLE_SRC
.. envvar:: WEBLATE_CSP_FONT_SRC
.. envvar:: WEBLATE_CSP_FORM_SRC
Allows to customize :http:header:`Content-Security-Policy` HTTP header.
.. seealso::
* :ref:`csp`
* :setting:`CSP_SCRIPT_SRC`
* :setting:`CSP_IMG_SRC`
* :setting:`CSP_CONNECT_SRC`
* :setting:`CSP_STYLE_SRC`
* :setting:`CSP_FONT_SRC`
* :setting:`CSP_FORM_SRC`
.. envvar:: WEBLATE_LICENSE_FILTER
Configures :setting:`LICENSE_FILTER`.
.. envvar:: WEBLATE_LICENSE_REQUIRED
Configures :setting:`LICENSE_REQUIRED`.
.. envvar:: WEBLATE_WEBSITE_REQUIRED
Configures :setting:`WEBSITE_REQUIRED`.
.. envvar:: WEBLATE_HIDE_VERSION
Configures :setting:`HIDE_VERSION`.
.. envvar:: WEBLATE_BASIC_LANGUAGES
Configures :setting:`BASIC_LANGUAGES`.
.. envvar:: WEBLATE_DEFAULT_AUTO_WATCH
Configures :setting:`DEFAULT_AUTO_WATCH`.
.. envvar:: WEBLATE_RATELIMIT_ATTEMPTS
.. envvar:: WEBLATE_RATELIMIT_LOCKOUT
.. envvar:: WEBLATE_RATELIMIT_WINDOW
.. versionadded:: 4.6
Configures rate limiter.
.. hint::
You can set configuration for any rate limiter scopes. To do that add ``WEBLATE_`` prefix to
any of setting described in :ref:`rate-limit`.
.. seealso::
* :ref:`rate-limit`
* :setting:`RATELIMIT_ATTEMPTS`
* :setting:`RATELIMIT_WINDOW`
* :setting:`RATELIMIT_LOCKOUT`
.. envvar:: WEBLATE_API_RATELIMIT_ANON
.. envvar:: WEBLATE_API_RATELIMIT_USER
.. versionadded:: 4.11
Configures API rate limiting. Defaults to ``100/day`` for anonymous and
``5000/hour`` for authenticated users.
.. seealso::
:ref:`api-rate`
.. envvar:: WEBLATE_ENABLE_HOOKS
.. versionadded:: 4.13
Configures :setting:`ENABLE_HOOKS`.
.. envvar:: WEBLATE_ENABLE_AVATARS
.. versionadded:: 4.6.1
Configures :setting:`ENABLE_AVATARS`.
.. envvar:: WEBLATE_AVATAR_URL_PREFIX
.. versionadded:: 4.15
Configures :setting:`AVATAR_URL_PREFIX`.
.. envvar:: WEBLATE_LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH
.. versionadded:: 4.9
Configures :setting:`LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH`.
.. envvar:: WEBLATE_SSH_EXTRA_ARGS
.. versionadded:: 4.9
Configures :setting:`SSH_EXTRA_ARGS`.
.. envvar:: WEBLATE_BORG_EXTRA_ARGS
.. versionadded:: 4.9
Configures :setting:`BORG_EXTRA_ARGS` as a comma separated list of args.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_BORG_EXTRA_ARGS: --exclude,vcs/
.. envvar:: WEBLATE_ENABLE_SHARING
.. versionadded:: 4.14.1
Configures :setting:`ENABLE_SHARING`.
.. envvar:: WEBLATE_SUPPORT_STATUS_CHECK
.. versionadded:: 5.5
Configures :setting:`SUPPORT_STATUS_CHECK`.
.. envvar:: WEBLATE_EXTRA_HTML_HEAD
.. versionadded:: 4.15
Configures :setting:`EXTRA_HTML_HEAD`.
.. envvar:: WEBLATE_PRIVATE_COMMIT_EMAIL_TEMPLATE
.. versionadded:: 4.15
Configures :setting:`PRIVATE_COMMIT_EMAIL_TEMPLATE`.
.. envvar:: WEBLATE_PRIVATE_COMMIT_EMAIL_OPT_IN
.. versionadded:: 4.15
Configures :setting:`PRIVATE_COMMIT_EMAIL_OPT_IN`.
.. envvar:: WEBLATE_PRIVATE_COMMIT_NAME_TEMPLATE
.. versionadded:: 5.16
Configures :setting:`PRIVATE_COMMIT_NAME_TEMPLATE`.
.. envvar:: WEBLATE_PRIVATE_COMMIT_NAME_OPT_IN
.. versionadded:: 5.16
Configures :setting:`PRIVATE_COMMIT_NAME_OPT_IN`.
.. envvar:: WEBLATE_UNUSED_ALERT_DAYS
.. versionadded:: 4.17
Configures :setting:`UNUSED_ALERT_DAYS`.
.. envvar:: WEBLATE_UPDATE_LANGUAGES
.. versionadded:: 4.3.2
Configures :setting:`UPDATE_LANGUAGES`.
.. envvar:: WEBLATE_VCS_ALLOW_HOSTS
.. versionadded:: 5.15
Configures :setting:`VCS_ALLOW_HOSTS`.
.. envvar:: WEBLATE_VCS_ALLOW_SCHEMES
.. versionadded:: 5.15
Configures :setting:`VCS_ALLOW_SCHEMES`.
.. envvar:: WEBLATE_VCS_RESTRICT_PRIVATE
.. versionadded:: 5.17
Configures :setting:`VCS_RESTRICT_PRIVATE`.
.. envvar:: WEBLATE_VCS_CLONE_DEPTH
.. versionadded:: 5.4
Configures :setting:`VCS_CLONE_DEPTH`.
.. envvar:: WEBLATE_VCS_API_DELAY
.. versionadded:: 5.4
Configures :setting:`VCS_API_DELAY`.
.. envvar:: WEBLATE_VCS_API_TIMEOUT
.. versionadded:: 5.15
Configures :setting:`VCS_API_TIMEOUT`.
.. envvar:: WEBLATE_CORS_ALLOWED_ORIGINS
.. versionadded:: 4.16
Allow CORS requests to API from given origins.
**Example:**
.. code-block:: yaml
environment:
WEBLATE_CORS_ALLOWED_ORIGINS: https://example.com,https://weblate.org
.. envvar:: WEBLATE_CORS_ALLOW_ALL_ORIGINS
.. versionadded:: 5.6.1
Allows CORS requests to API from all origins.
.. envvar:: WEBLATE_WEBSITE_ALERTS_ENABLED
.. versionadded:: 5.17
Configures :setting:`WEBSITE_ALERTS_ENABLED`.
.. envvar:: CLIENT_MAX_BODY_SIZE
.. versionadded:: 4.16.3
Configures maximal body size accepted by the built-in web server.
.. code-block:: yaml
environment:
CLIENT_MAX_BODY_SIZE: 200m
.. hint::
This variable intentionally lacks ``WEBLATE_`` prefix as it is shared
with third-party container used in :ref:`docker-https-portal`.
.. _docker-vcs-config:
Code hosting sites credentials
++++++++++++++++++++++++++++++
In the Docker container, the code hosting credentials can be configured either
in separate variables or using a Python dictionary to set them at once. The
following examples are for :ref:`vcs-github`, but applies to all :ref:`vcs`
with appropriately changed variable names.
.. important::
All environment variable names must include the ``WEBLATE_`` prefix. For example,
to configure GitHub credentials, use ``WEBLATE_GITHUB_USERNAME``, not ``GITHUB_USERNAME``.
This applies whether you're configuring for pull requests or any other VCS integration.
An example configuration for GitHub pull requests might look like:
.. code-block:: shell
WEBLATE_GITHUB_USERNAME=api-user
WEBLATE_GITHUB_TOKEN=api-token
WEBLATE_GITHUB_HOST=api.github.com
Will be used as:
.. code-block:: python
GITHUB_CREDENTIALS = {
"api.github.com": {
"username": "api-user",
"token": "api-token",
}
}
Alternatively the Python dictionary can be provided as a string:
.. code-block:: shell
WEBLATE_GITHUB_CREDENTIALS='{ "api.github.com": { "username": "api-user", "token": "api-token", } }'
Or the path to a file containing the Python dictionary:
.. code-block:: shell
echo '{ "api.github.com": { "username": "api-user", "token": "api-token", } }' > /path/to/github-credentials
WEBLATE_GITHUB_CREDENTIALS_FILE='/path/to/github-credentials'
.. envvar:: WEBLATE_GITHUB_USERNAME
.. envvar:: WEBLATE_GITHUB_TOKEN
.. envvar:: WEBLATE_GITHUB_HOST
.. envvar:: WEBLATE_GITHUB_CREDENTIALS
Configures :ref:`vcs-github` by changing :setting:`GITHUB_CREDENTIALS`.
.. seealso::
:ref:`Configuring code hosting credentials in Docker <docker-vcs-config>`
.. envvar:: WEBLATE_GITLAB_USERNAME
.. envvar:: WEBLATE_GITLAB_TOKEN
.. envvar:: WEBLATE_GITLAB_HOST
.. envvar:: WEBLATE_GITLAB_CREDENTIALS
Configures :ref:`vcs-gitlab` by changing :setting:`GITLAB_CREDENTIALS`.
.. seealso::
:ref:`Configuring code hosting credentials in Docker <docker-vcs-config>`
.. envvar:: WEBLATE_GITEA_USERNAME
.. envvar:: WEBLATE_GITEA_TOKEN
.. envvar:: WEBLATE_GITEA_HOST
.. envvar:: WEBLATE_GITEA_CREDENTIALS
Configures :ref:`vcs-gitea` by changing :setting:`GITEA_CREDENTIALS`.
.. seealso::
:ref:`Configuring code hosting credentials in Docker <docker-vcs-config>`
.. envvar:: WEBLATE_PAGURE_USERNAME
.. envvar:: WEBLATE_PAGURE_TOKEN
.. envvar:: WEBLATE_PAGURE_HOST
.. envvar:: WEBLATE_PAGURE_CREDENTIALS
Configures :ref:`vcs-pagure` by changing :setting:`PAGURE_CREDENTIALS`.
.. seealso::
:ref:`Configuring code hosting credentials in Docker <docker-vcs-config>`
.. envvar:: WEBLATE_BITBUCKETSERVER_USERNAME
.. envvar:: WEBLATE_BITBUCKETSERVER_TOKEN
.. envvar:: WEBLATE_BITBUCKETSERVER_HOST
.. envvar:: WEBLATE_BITBUCKETSERVER_CREDENTIALS
Configures :ref:`vcs-bitbucket-data-center` by changing :setting:`BITBUCKETSERVER_CREDENTIALS`.
.. envvar:: WEBLATE_BITBUCKETCLOUD_USERNAME
.. envvar:: WEBLATE_BITBUCKETCLOUD_WORKSPACE
.. envvar:: WEBLATE_BITBUCKETCLOUD_TOKEN
.. envvar:: WEBLATE_BITBUCKETCLOUD_HOST
.. envvar:: WEBLATE_BITBUCKETCLOUD_CREDENTIALS
Configures :ref:`vcs-bitbucket-cloud` by changing :setting:`BITBUCKETCLOUD_CREDENTIALS`.
.. seealso::
:ref:`Configuring code hosting credentials in Docker <docker-vcs-config>`
.. envvar:: WEBLATE_AZURE_DEVOPS_USERNAME
.. envvar:: WEBLATE_AZURE_DEVOPS_ORGANIZATION
.. envvar:: WEBLATE_AZURE_DEVOPS_TOKEN
.. envvar:: WEBLATE_AZURE_DEVOPS_HOST
.. envvar:: WEBLATE_AZURE_DEVOPS_CREDENTIALS
Configures :ref:`vcs-azure-devops` by changing :setting:`AZURE_DEVOPS_CREDENTIALS`.
.. seealso::
:ref:`Configuring code hosting credentials in Docker <docker-vcs-config>`
.. _docker-machine:
Automatic suggestion settings
+++++++++++++++++++++++++++++
.. versionchanged:: 4.13
Automatic suggestion services are now configured in the user interface,
see :ref:`machine-translation-setup`.
The existing environment variables are imported during the migration to
Weblate 4.13, but changing them will not have any further effect.
.. _docker-auth:
Authentication settings
+++++++++++++++++++++++
.. hint::
The e-mail based authentication is turned on unless disabled by :envvar:`WEBLATE_NO_EMAIL_AUTH`.
LDAP
~~~~
.. envvar:: WEBLATE_AUTH_LDAP_SERVER_URI
.. envvar:: WEBLATE_AUTH_LDAP_USER_DN_TEMPLATE
.. envvar:: WEBLATE_AUTH_LDAP_USER_ATTR_MAP
.. envvar:: WEBLATE_AUTH_LDAP_BIND_DN
.. envvar:: WEBLATE_AUTH_LDAP_BIND_PASSWORD
.. envvar:: WEBLATE_AUTH_LDAP_CONNECTION_OPTION_REFERRALS
.. envvar:: WEBLATE_AUTH_LDAP_USER_SEARCH
.. envvar:: WEBLATE_AUTH_LDAP_USER_SEARCH_FILTER
.. envvar:: WEBLATE_AUTH_LDAP_USER_SEARCH_UNION
.. envvar:: WEBLATE_AUTH_LDAP_USER_SEARCH_UNION_DELIMITER
LDAP authentication configuration.
**Example for direct bind:**
.. code-block:: yaml
environment:
WEBLATE_AUTH_LDAP_SERVER_URI: ldap://ldap.example.org
WEBLATE_AUTH_LDAP_USER_DN_TEMPLATE: uid=%(user)s,ou=People,dc=example,dc=net
# map weblate 'full_name' to ldap 'name' and weblate 'email' attribute to 'mail' ldap attribute.
# another example that can be used with OpenLDAP: 'full_name:cn,email:mail'
WEBLATE_AUTH_LDAP_USER_ATTR_MAP: full_name:name,email:mail
**Example for search and bind:**
.. code-block:: yaml
environment:
WEBLATE_AUTH_LDAP_SERVER_URI: ldap://ldap.example.org
WEBLATE_AUTH_LDAP_BIND_DN: CN=ldap,CN=Users,DC=example,DC=com
WEBLATE_AUTH_LDAP_BIND_PASSWORD: password
WEBLATE_AUTH_LDAP_USER_ATTR_MAP: full_name:name,email:mail
WEBLATE_AUTH_LDAP_USER_SEARCH: CN=Users,DC=example,DC=com
**Example for union search and bind:**
.. code-block:: yaml
environment:
WEBLATE_AUTH_LDAP_SERVER_URI: ldap://ldap.example.org
WEBLATE_AUTH_LDAP_BIND_DN: CN=ldap,CN=Users,DC=example,DC=com
WEBLATE_AUTH_LDAP_BIND_PASSWORD: password
WEBLATE_AUTH_LDAP_USER_ATTR_MAP: full_name:name,email:mail
WEBLATE_AUTH_LDAP_USER_SEARCH_UNION: ou=users,dc=example,dc=com|ou=otherusers,dc=example,dc=com
**Example with search and bind against Active Directory:**
.. code-block:: yaml
environment:
WEBLATE_AUTH_LDAP_BIND_DN: CN=ldap,CN=Users,DC=example,DC=com
WEBLATE_AUTH_LDAP_BIND_PASSWORD: password
WEBLATE_AUTH_LDAP_SERVER_URI: ldap://ldap.example.org
WEBLATE_AUTH_LDAP_CONNECTION_OPTION_REFERRALS: 0
WEBLATE_AUTH_LDAP_USER_ATTR_MAP: full_name:name,email:mail
WEBLATE_AUTH_LDAP_USER_SEARCH: CN=Users,DC=example,DC=com
WEBLATE_AUTH_LDAP_USER_SEARCH_FILTER: (sAMAccountName=%(user)s)
.. seealso::
* :ref:`docker-secrets`
* :ref:`ldap-auth`
GitHub
~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ORG_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ORG_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ORG_NAME
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_TEAM_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_TEAM_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_TEAM_ID
Enables :ref:`github_auth`.
GitHub Enterprise Edition
~~~~~~~~~~~~~~~~~~~~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_URL
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_API_URL
.. envvar:: WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_SCOPE
Enables :ref:`github_ee_auth`.
Bitbucket
~~~~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_BITBUCKET_OAUTH2_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_BITBUCKET_OAUTH2_SECRET
Enables :ref:`bitbucket_auth`.
Facebook
~~~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_FACEBOOK_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_FACEBOOK_SECRET
Enables :ref:`facebook_auth`.
Google
~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_WHITELISTED_DOMAINS
.. envvar:: WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_WHITELISTED_EMAILS
Enables :ref:`google_auth`.
GitLab
~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_GITLAB_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GITLAB_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_GITLAB_API_URL
Enables :ref:`gitlab_auth`.
Gitea
~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_GITEA_API_URL
.. envvar:: WEBLATE_SOCIAL_AUTH_GITEA_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_GITEA_SECRET
Enables Gitea authentication.
Azure Active Directory
~~~~~~~~~~~~~~~~~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_AZUREAD_OAUTH2_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_AZUREAD_OAUTH2_SECRET
Enables Azure Active Directory authentication, see :ref:`azure-auth`.
Azure Active Directory with Tenant support
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_AZUREAD_TENANT_OAUTH2_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_AZUREAD_TENANT_OAUTH2_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_AZUREAD_TENANT_OAUTH2_TENANT_ID
Enables Azure Active Directory authentication with Tenant support, see
:ref:`azure-auth`.
Keycloak
~~~~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_PUBLIC_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_ALGORITHM
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_AUTHORIZATION_URL
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_ACCESS_TOKEN_URL
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_TITLE
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_IMAGE
Enables Keycloak authentication, see :doc:`psa:backends/keycloak`.
.. envvar:: WEBLATE_SOCIAL_AUTH_KEYCLOAK_ID_KEY
.. versionadded:: 5.17
Configures which claim is used as the unique user identifier from Keycloak.
Defaults to ``email``.
.. hint::
When Keycloak is configured to abstract third-party IDP, you will need
to configure :envvar:`WEBLATE_CSP_FORM_SRC` for the third-party IDP domain.
.. code-block:: yaml
:caption: Example when Keycloak is passing authentication to Microsoft.
environment:
WEBLATE_CSP_FORM_SRC: login.microsoftonline.com
Linux vendors
~~~~~~~~~~~~~
You can enable authentication using Linux vendors authentication services by
setting following variables to any value.
.. envvar:: WEBLATE_SOCIAL_AUTH_FEDORA
.. envvar:: WEBLATE_SOCIAL_AUTH_OPENSUSE
.. envvar:: WEBLATE_SOCIAL_AUTH_OPENINFRA
.. envvar:: WEBLATE_SOCIAL_AUTH_UBUNTU
Slack
~~~~~
.. envvar:: WEBLATE_SOCIAL_AUTH_SLACK_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_SLACK_SECRET
Enables Slack authentication, see :ref:`slack-auth`.
OpenID Connect
~~~~~~~~~~~~~~
.. versionadded:: 4.13-1
.. envvar:: WEBLATE_SOCIAL_AUTH_OIDC_OIDC_ENDPOINT
.. envvar:: WEBLATE_SOCIAL_AUTH_OIDC_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_OIDC_SECRET
.. envvar:: WEBLATE_SOCIAL_AUTH_OIDC_USERNAME_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_OIDC_TITLE
.. envvar:: WEBLATE_SOCIAL_AUTH_OIDC_IMAGE
Configures generic OpenID Connect integration.
.. seealso::
:doc:`psa:backends/oidc`
Fedora OpenID Connect
~~~~~~~~~~~~~~~~~~~~~
.. versionadded:: 5.15
.. envvar:: WEBLATE_SOCIAL_AUTH_FEDORA_OIDC_KEY
.. envvar:: WEBLATE_SOCIAL_AUTH_FEDORA_OIDC_SECRET
Configures Fedora OpenID Connect integration.
.. seealso::
:doc:`psa:backends/fedora`
.. _docker-saml:
SAML
~~~~
Self-signed SAML keys are automatically generated on first container startup.
In case you want to use own keys, place the certificate and private key in
:file:`/app/data/ssl/saml.crt` and :file:`/app/data/ssl/saml.key`.
.. envvar:: WEBLATE_SAML_IDP_ENTITY_ID
.. envvar:: WEBLATE_SAML_IDP_URL
.. envvar:: WEBLATE_SAML_IDP_X509CERT
.. envvar:: WEBLATE_SAML_IDP_IMAGE
.. envvar:: WEBLATE_SAML_IDP_TITLE
SAML Identity Provider settings, see :ref:`saml-auth`.
.. envvar:: WEBLATE_SAML_ID_ATTR_FULL_NAME
.. envvar:: WEBLATE_SAML_ID_ATTR_FIRST_NAME
.. envvar:: WEBLATE_SAML_ID_ATTR_LAST_NAME
.. envvar:: WEBLATE_SAML_ID_ATTR_USERNAME
.. envvar:: WEBLATE_SAML_ID_ATTR_EMAIL
.. envvar:: WEBLATE_SAML_ID_ATTR_USER_PERMANENT_ID
.. versionadded:: 4.18
SAML attributes mapping.
Other authentication settings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. envvar:: WEBLATE_NO_EMAIL_AUTH
Disables e-mail authentication when set to any value. See
:ref:`disable-email-auth`.
.. envvar:: WEBLATE_MIN_PASSWORD_SCORE
Minimal password score as evaluated by the `zxcvbn
<https://github.com/dwolfhub/zxcvbn-python>`_ password strength estimator.
Defaults to 3, set to 0 to disable strength checking.
.. seealso::
* :ref:`password-authentication`
* :setting:`PASSWORD_MINIMAL_STRENGTH`
PostgreSQL database setup
+++++++++++++++++++++++++
The database is created by :file:`docker-compose.yml`, so these settings affect
both Weblate and PostgreSQL containers.
.. seealso::
:ref:`database-setup`
.. envvar:: POSTGRES_PASSWORD
PostgreSQL password.
.. seealso::
:ref:`docker-secrets`
.. envvar:: POSTGRES_USER
PostgreSQL username.
.. envvar:: POSTGRES_DB
PostgreSQL database name.
.. envvar:: POSTGRES_HOST
PostgreSQL server hostname or IP address. Defaults to ``database``.
.. envvar:: POSTGRES_PORT
PostgreSQL server port. Defaults to none (uses the default value).
.. envvar:: POSTGRES_SSL_MODE
Configure how PostgreSQL handles SSL in connection to the server, for possible choices see
`SSL Mode Descriptions <https://www.postgresql.org/docs/11/libpq-ssl.html#LIBPQ-SSL-SSLMODE-STATEMENTS>`_.
.. envvar:: POSTGRES_ALTER_ROLE
Configures name of the PostgreSQL role to alter during the database migration, see :ref:`config-postgresql`.
Defaults to :envvar:`POSTGRES_USER`.
.. envvar:: POSTGRES_CONN_MAX_AGE
.. versionadded:: 4.8.1
The lifetime of a database connection, as an integer of seconds. Use 0 to
close database connections at the end of each request.
.. versionchanged:: 5.1
The default behavior is to have unlimited persistent database connections.
Enabling connection persistence will typically, cause more open connection
to the database. Please adjust your database configuration prior enabling.
Example configuration:
.. code-block:: yaml
environment:
POSTGRES_CONN_MAX_AGE: 3600
.. seealso::
* :setting:`django:CONN_MAX_AGE`
* :ref:`django:persistent-database-connections`
.. envvar:: POSTGRES_DISABLE_SERVER_SIDE_CURSORS
.. versionadded:: 4.9.1
Disable server side cursors in the database. This is necessary in some
:command:`pgbouncer` setups.
Example configuration:
.. code-block:: yaml
environment:
POSTGRES_DISABLE_SERVER_SIDE_CURSORS: 1
.. seealso::
* :setting:`DISABLE_SERVER_SIDE_CURSORS <django:DATABASE-DISABLE_SERVER_SIDE_CURSORS>`
* :ref:`django:transaction-pooling-server-side-cursors`
.. envvar:: WEBLATE_DATABASES
.. versionadded:: 5.1
Set to false to disables environment based configuration of the database
connection. Use :ref:`docker-settings-override` to configure the database
connection manually.
Database backup settings
++++++++++++++++++++++++
.. seealso::
:ref:`backup-dumps`
.. envvar:: WEBLATE_DATABASE_BACKUP
Configures the daily database dump using :setting:`DATABASE_BACKUP`. Defaults to ``plain``.
Datastore server setup
++++++++++++++++++++++
Using Valkey or Redis is required by the Weblate container and you have to
provide a connection parameters when running Weblate in Docker.
.. seealso::
:ref:`production-cache`
.. envvar:: REDIS_HOST
The datastore server hostname or IP address. Defaults to ``cache``.
.. envvar:: REDIS_PORT
The datastore server port. Defaults to ``6379``.
.. envvar:: REDIS_DB
The datastore database number, defaults to ``1``.
.. envvar:: REDIS_USER
.. versionadded:: 5.13
The datastore database user, not used by default.
.. envvar:: REDIS_PASSWORD
The datastore server password, not used by default.
.. seealso::
:ref:`docker-secrets`
.. envvar:: REDIS_TLS
Enables using SSL for the datastore connection.
.. envvar:: REDIS_VERIFY_SSL
Can be used to disable SSL certificate verification for the datastore connection.
.. _docker-mail:
Email server setup
++++++++++++++++++
To make outgoing e-mail work, you need to provide a mail server.
Example TLS configuration:
.. code-block:: yaml
environment:
WEBLATE_EMAIL_HOST: smtp.example.com
WEBLATE_EMAIL_HOST_USER: user
WEBLATE_EMAIL_HOST_PASSWORD: pass
Example SSL configuration:
.. code-block:: yaml
environment:
WEBLATE_EMAIL_HOST: smtp.example.com
WEBLATE_EMAIL_PORT: 465
WEBLATE_EMAIL_HOST_USER: user
WEBLATE_EMAIL_HOST_PASSWORD: pass
WEBLATE_EMAIL_USE_TLS: 0
WEBLATE_EMAIL_USE_SSL: 1
.. seealso::
:ref:`out-mail`
.. envvar:: WEBLATE_EMAIL_HOST
Mail server hostname or IP address.
.. seealso::
* :envvar:`WEBLATE_EMAIL_PORT`
* :envvar:`WEBLATE_EMAIL_USE_SSL`
* :envvar:`WEBLATE_EMAIL_USE_TLS`
* :setting:`django:EMAIL_HOST`
.. envvar:: WEBLATE_EMAIL_PORT
Mail server port, defaults to 25.
.. seealso::
:setting:`django:EMAIL_PORT`
.. envvar:: WEBLATE_EMAIL_HOST_USER
E-mail authentication user.
.. seealso::
:setting:`django:EMAIL_HOST_USER`
.. envvar:: WEBLATE_EMAIL_HOST_PASSWORD
E-mail authentication password.
.. seealso::
* :ref:`docker-secrets`
* :setting:`django:EMAIL_HOST_PASSWORD`
.. envvar:: WEBLATE_EMAIL_USE_SSL
Whether to use an implicit TLS (secure) connection when talking to the SMTP
server. In most e-mail documentation, this type of TLS connection is referred
to as SSL. It is generally used on port 465. If you are experiencing
problems, see the explicit TLS setting :envvar:`WEBLATE_EMAIL_USE_TLS`.
.. versionchanged:: 4.11
The SSL/TLS support is automatically enabled based on the
:envvar:`WEBLATE_EMAIL_PORT`.
.. seealso::
* :envvar:`WEBLATE_EMAIL_PORT`
* :envvar:`WEBLATE_EMAIL_USE_TLS`
* :setting:`django:EMAIL_USE_SSL`
.. envvar:: WEBLATE_EMAIL_USE_TLS
Whether to use a TLS (secure) connection when talking to the SMTP server.
This is used for explicit TLS connections, generally on port 587 or 25. If
you are experiencing connections that hang, see the implicit TLS setting
:envvar:`WEBLATE_EMAIL_USE_SSL`.
.. versionchanged:: 4.11
The SSL/TLS support is automatically enabled based on the
:envvar:`WEBLATE_EMAIL_PORT`.
.. seealso::
* :envvar:`WEBLATE_EMAIL_PORT`
* :envvar:`WEBLATE_EMAIL_USE_SSL`
* :setting:`django:EMAIL_USE_TLS`
.. envvar:: WEBLATE_EMAIL_BACKEND
Configures Django back-end to use for sending e-mails.
.. seealso::
* :ref:`production-email`
* :setting:`django:EMAIL_BACKEND`
.. envvar:: WEBLATE_AUTO_UPDATE
Configures if and how Weblate should update repositories.
.. seealso::
:setting:`AUTO_UPDATE`
.. note:: This is a Boolean setting (use ``"true"`` or ``"false"``).
Site integration
++++++++++++++++
.. envvar:: WEBLATE_GET_HELP_URL
Configures :setting:`GET_HELP_URL`.
.. envvar:: WEBLATE_STATUS_URL
Configures :setting:`STATUS_URL`.
.. envvar:: WEBLATE_LEGAL_URL
Configures :setting:`LEGAL_URL`.
.. envvar:: WEBLATE_PRIVACY_URL
Configures :setting:`PRIVACY_URL`.
.. envvar:: WEBLATE_PASSWORD_RESET_URL
Configures :setting:`PASSWORD_RESET_URL`.
Collecting error reports and monitoring performance
+++++++++++++++++++++++++++++++++++++++++++++++++++
It is recommended to collect errors from the installation systematically,
see :ref:`collecting-errors`.
To enable support for Rollbar, set the following:
.. envvar:: ROLLBAR_KEY
Your Rollbar post server access token.
.. envvar:: ROLLBAR_ENVIRONMENT
Your Rollbar environment, defaults to ``production``.
To enable support for Sentry, set following:
.. envvar:: SENTRY_DSN
Your Sentry DSN, see :setting:`SENTRY_DSN`.
.. envvar:: SENTRY_ENVIRONMENT
Your Sentry Environment (optional), defaults to :envvar:`WEBLATE_SITE_DOMAIN`.
.. envvar:: SENTRY_MONITOR_BEAT_TASKS
Whether to monitor Celery Beat tasks with Sentry, defaults to ``True``.
.. envvar:: SENTRY_TRACES_SAMPLE_RATE
Configures :setting:`SENTRY_TRACES_SAMPLE_RATE`.
**Example:**
.. code-block:: yaml
environment:
SENTRY_TRACES_SAMPLE_RATE: 0.5
.. envvar:: SENTRY_PROFILES_SAMPLE_RATE
Configures :setting:`SENTRY_PROFILES_SAMPLE_RATE`.
**Example:**
.. code-block:: yaml
environment:
SENTRY_PROFILES_SAMPLE_RATE: 0.5
.. envvar:: SENTRY_SEND_PII
Configures :setting:`SENTRY_SEND_PII`.
Localization CDN
++++++++++++++++
.. envvar:: WEBLATE_LOCALIZE_CDN_URL
.. envvar:: WEBLATE_LOCALIZE_CDN_PATH
.. versionadded:: 4.2.1
Configuration for :ref:`addon-weblate.cdn.cdnjs`.
The :envvar:`WEBLATE_LOCALIZE_CDN_PATH` is path within the container. It
should be stored on the persistent volume and not in the transient storage.
One of possibilities is storing that inside the Weblate data dir:
.. code-block:: yaml
environment:
WEBLATE_LOCALIZE_CDN_URL: https://cdn.example.com/
WEBLATE_LOCALIZE_CDN_PATH: /app/data/l10n-cdn
.. note::
You are responsible for setting up serving of the files generated by
Weblate, it only does stores the files in configured location.
.. seealso::
* :ref:`weblate-cdn`
* :setting:`LOCALIZE_CDN_URL`
* :setting:`LOCALIZE_CDN_PATH`
Changing enabled apps, checks, add-ons, machine translation or autofixes
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The built-in configuration of enabled checks, add-ons or autofixes can be
adjusted by the following variables:
.. envvar:: WEBLATE_ADD_APPS
.. envvar:: WEBLATE_REMOVE_APPS
.. envvar:: WEBLATE_ADD_CHECK
.. envvar:: WEBLATE_REMOVE_CHECK
.. envvar:: WEBLATE_ADD_AUTOFIX
.. envvar:: WEBLATE_REMOVE_AUTOFIX
.. envvar:: WEBLATE_ADD_ADDONS
.. envvar:: WEBLATE_REMOVE_ADDONS
.. envvar:: WEBLATE_ADD_MACHINERY
.. versionadded:: 5.6.1
.. envvar:: WEBLATE_REMOVE_MACHINERY
.. versionadded:: 5.6.1
**Example:**
.. code-block:: yaml
environment:
WEBLATE_REMOVE_AUTOFIX: weblate.trans.autofixes.whitespace.SameBookendingWhitespace
WEBLATE_ADD_ADDONS: customize.addons.MyAddon,customize.addons.OtherAddon
.. seealso::
* :setting:`CHECK_LIST`
* :setting:`AUTOFIX_LIST`
* :setting:`WEBLATE_ADDONS`
* :setting:`django:INSTALLED_APPS`
* :setting:`WEBLATE_MACHINERY`
Container settings
++++++++++++++++++
.. envvar:: WEBLATE_WORKERS
.. versionadded:: 4.6.1
Base number of worker processes running in the container. When not set it is
determined automatically on container startup based on number of CPU cores
available.
It is used to determine :envvar:`CELERY_MAIN_OPTIONS`,
:envvar:`CELERY_NOTIFY_OPTIONS`, :envvar:`CELERY_MEMORY_OPTIONS`,
:envvar:`CELERY_TRANSLATE_OPTIONS`, :envvar:`CELERY_BACKUP_OPTIONS`,
:envvar:`CELERY_BEAT_OPTIONS`, and :envvar:`WEB_WORKERS`. You can use
these settings to fine-tune.
.. envvar:: CELERY_MAIN_OPTIONS
.. envvar:: CELERY_NOTIFY_OPTIONS
.. envvar:: CELERY_MEMORY_OPTIONS
.. envvar:: CELERY_TRANSLATE_OPTIONS
.. envvar:: CELERY_BACKUP_OPTIONS
.. envvar:: CELERY_BEAT_OPTIONS
These variables allow you to adjust Celery worker options. It can be useful
to adjust concurrency (``--concurrency 16``) or use different pool
implementation (``--pool=gevent``).
By default, the number of concurrent workers is based on :envvar:`WEBLATE_WORKERS`.
**Example:**
.. code-block:: yaml
environment:
CELERY_MAIN_OPTIONS: --concurrency 16
.. seealso::
* :doc:`Celery worker options <celery:reference/celery.bin.worker>`
* :ref:`celery`
.. envvar:: CELERY_SINGLE_PROCESS
.. versionadded:: 5.7.1
This variable can be set to ``1`` to run only one celery process. This reduces memory usage but may impact Weblate performance.
.. code-block:: yaml
environment:
CELERY_SINGLE_PROCESS: 1
.. seealso::
:ref:`minimal-celery`
.. envvar:: WEB_WORKERS
Configure how many WSGI workers should be executed.
It defaults to half of :envvar:`WEBLATE_WORKERS`, but is always at least 2.
**Example:**
.. code-block:: yaml
environment:
WEB_WORKERS: 4
.. versionchanged:: 5.13
:envvar:`WEB_WORKERS` configures how many worker processes will used by :program:`granian`.
.. envvar:: WEBLATE_SERVICE
Defines which services should be executed inside the container. Use this for :ref:`docker-scaling`.
Following services are defined:
``celery-beat``
Celery task scheduler, only one instance should be running.
This container is also responsible for the database structure migrations
and it should be started prior others.
``celery-backup``
Celery worker for backups, only one instance should be running.
``celery-celery``
Generic Celery worker.
``celery-memory``
Translation memory Celery worker.
``celery-notify``
Notifications Celery worker.
``celery-translate``
Automatic translation Celery worker.
``web``
Web server.
.. seealso::
:ref:`background-tasks-internals`
.. envvar:: WEBLATE_ANUBIS_URL
.. versionadded:: 5.11.4
URL of `Anubis`_ server to handle subrequest authentication. This can be
useful to filter incoming HTTP requests using proof-of-work to stop AI
crawlers. You need to configure `Anubis for Subrequest Authentication`_ to
make it work.
.. seealso::
* :ref:`docker-anubis`
* `Anubis`_
.. _Anubis: https://anubis.techaro.lol/
.. _Anubis for Subrequest Authentication: https://anubis.techaro.lol/docs/admin/configuration/subrequest-auth
.. _docker-volume:
Docker container volumes
------------------------
There are two volumes (:file:`data` and :file:`cache`) exported by the Weblate
container.
.. note::
The other service containers (such as PostgreSQL or Valkey) have their data
volumes as well and are required to maintain Weblate persistence.
The PostgreSQL container stores the database in the
:file:`/var/lib/postgresql` volume and Valkey in the :file:`/data` volume.
Valkey container does not save the data by default and needs additional
configuration to enable persistence.
Base your configuration on Weblate-provided examples or consult their
documentation for more information.
The :file:`data` volume is mounted as :file:`/app/data` and is used to store
Weblate persistent data such as cloned repositories or to customize Weblate
installation. :setting:`DATA_DIR` describes in more detail what is stored here.
The :file:`data` volume is also place to store Weblate customization such as
:ref:`docker-settings-override`, :ref:`docker-static-override` or
:ref:`docker-python-override`.
The placement of the Docker volume on host system depends on your Docker
configuration, but usually it is stored in
:file:`/var/lib/docker/volumes/weblate-docker_weblate-data/_data/` (the path
consist of name of your docker-compose directory, container, and volume names).
The :file:`cache` volume is mounted as :file:`/app/cache` and is used to store static
files and :setting:`CACHE_DIR`. Its content is recreated on container startup
and the volume can be mounted using ephemeral filesystem such as `tmpfs`.
When creating the volumes manually, the directories should be owned by UID 1000
as that is user used inside the container.
Weblate container can also be executed with a read-only root file system. In
this case, two additional ``tmpfs`` volumes should be mounted: :file:`/tmp` and
:file:`/run`.
.. seealso::
* `Docker volumes documentation <https://docs.docker.com/engine/storage/volumes/>`_
* :setting:`DATA_DIR`
* :setting:`CACHE_DIR`
Read-only root filesystem
+++++++++++++++++++++++++
.. versionadded:: 4.18
When running the container with a read-only root filesystem, two additional
`tmpfs` volumes are required - :file:`/tmp` and :file:`/run`.
.. _docker-custom-config:
Configuration beyond environment variables
------------------------------------------
:ref:`Docker environment variables <docker-environment>` are intended to expose
most :ref:`configuration settings <config>` of relevance for Weblate
installations.
If you find a setting that is not exposed as an environment variable, and you
believe that it should be, feel free to :ref:`ask for it to be exposed in a
future version of Weblate <report-issue>`.
If you need to modify a setting that is not exposed as a Docker environment
variable, you can still do so, either :ref:`from the data volume
<docker-settings-override>` or :ref:`extending the Docker image
<docker-custom-settings>`.
.. seealso::
:doc:`../customize`
.. _docker-settings-override:
Overriding settings from the data volume
++++++++++++++++++++++++++++++++++++++++
You can create a file at :file:`/app/data/settings-override.py`, i.e. at the
root of the :ref:`data volume <docker-volume>`, to extend or override settings
defined through environment variables.
.. _docker-custom-settings:
Overriding settings by extending the Docker image
+++++++++++++++++++++++++++++++++++++++++++++++++
To override settings at the Docker image level instead of from the data volume:
#. :ref:`Create a custom Python package <custom-module>`.
#. Add a module to your package that imports all settings from
``weblate.settings_docker``.
For example, within the example package structure defined at
:ref:`custom-module`, you could create a file at
``weblate_customization/weblate_customization/settings.py`` with the
following initial code:
.. code-block:: python
from weblate.settings_docker import *
#. Create a custom ``Dockerfile`` that inherits from the official Weblate
Docker image, and then installs your package and points the
``DJANGO_SETTINGS_MODULE`` environment variable to your settings module:
.. code-block:: docker
FROM weblate/weblate
USER root
COPY weblate_customization /usr/src/weblate_customization
RUN source /app/venv/bin/activate && uv pip install --no-cache-dir /usr/src/weblate_customization
ENV DJANGO_SETTINGS_MODULE=weblate_customization.settings
USER 1000
#. Instead of using the official Weblate Docker image, build a custom image
from this ``Dockerfile`` file.
There is `no clean way <https://github.com/docker/compose/issues/7231>`__
to do this with ``docker-compose.override.yml``. You *could* add
``build: .`` to the ``weblate`` node in that file, but then your custom
image will be tagged as ``weblate/weblate`` in your system, which could be
problematic.
So, instead of using the ``docker-compose.yml`` straight from the `official
repository <https://github.com/WeblateOrg/docker-compose>`__, unmodified,
and extending it through ``docker-compose.override.yml``, you may want to
make a copy of the official ``docker-compose.yml`` file, and edit your copy
to replace ``image: weblate/weblate`` with ``build: .``.
See the `Compose file build reference`_ for details on building images from
source when using ``docker-compose``.
.. _Compose file build reference: https://docs.docker.com/reference/compose-file/build/
#. Extend your custom settings module to define or redefine settings.
You can define settings before or after the import statement above to
determine which settings take precedence. Settings defined before the
import statement can be overridden by environment variables and setting
overrides defined in the data volume. Setting defined after the import
statement cannot be overridden.
You can also go further. For example, you can reproduce some of the things
that ``weblate.docker_settings`` `does
<https://github.com/WeblateOrg/weblate/blob/main/weblate/settings_docker.py>`__,
such as exposing settings as environment variables, or allow overriding
settings from Python files in the data volume.
.. _docker-static-override:
Replacing logo and other static files
+++++++++++++++++++++++++++++++++++++
The static files coming with Weblate can be overridden by placing into
:file:`/app/data/python/customize/static` (see :ref:`docker-volume`). For
example creating :file:`/app/data/python/customize/static/favicon.ico` will
replace the favicon.
.. hint::
The files are copied to the corresponding location upon container startup, so
a restart of Weblate is needed after changing the content of the volume.
This approach can be also used to override Weblate templates. For example
:ref:`legal` documents can be placed into
:file:`/app/data/python/customize/templates/legal/documents`.
Alternatively you can also include own module (see :doc:`../customize`) and add
it as separate volume to the Docker container, for example:
.. code-block:: yaml
weblate:
volumes:
- weblate-data:/app/data
- ./weblate_customization/weblate_customization:/app/data/python/weblate_customization
environment:
WEBLATE_ADD_APPS: weblate_customization
.. _docker-python-override:
Customizing code
++++++++++++++++
.. note::
The internal Weblate API may vary significantly between releases and is not
meant to be stable. Please review your custom code interacting with Weblate
internals on each upgrade.
You can place additional Python code into :file:`/app/data/python/customize`
(see :ref:`docker-volume`). It is already installed as a Django application
inside Weblate (this is used for customizing templates and static files as
described above).
This can be used to place any code (for example :ref:`own-checks`) or to add
custom maintenance tasks to the Celery task scheduler.
.. literalinclude:: ../../../weblate/examples/custom_tasks.py
:language: python
:caption: An example of custom scheduled tasks in :file:`/app/data/python/customize/tasks.py`.
Integrating third-party containers
----------------------------------
The Weblate Docker setup can be extended with additional containers to provide
complementary services such as machine translation, spell checking, or other
tools that enhance the translation workflow. These services can be integrated
into your Docker Compose configuration and work alongside Weblate.
When adding third-party containers, consider the following:
* **Network connectivity**: Ensure containers can communicate with each other by placing them on the same Docker network
* **Data persistence**: Use volumes for services that need to persist data
* **Security**: Configure appropriate access controls and avoid exposing unnecessary ports
.. _docker-libretranslate:
LibreTranslate Docker container integration
+++++++++++++++++++++++++++++++++++++++++++
`LibreTranslate <https://libretranslate.com/>`_ is a free and open-source machine
translation service that can be self-hosted. Integrating it with Weblate provides
offline machine translation capabilities without relying on external services.
You can incorporate the LibreTranslate service into your Weblate deployment by including it in a :file:`docker-compose.override.yml` file. Since it runs within the Docker network, it's only accessible to Weblate and not exposed to the public internet.
Basic setup using :file:`docker-compose.override.yml`:
.. code-block:: yaml
services:
libretranslate:
image: libretranslate/libretranslate:latest
command: --disable-web-ui
restart: unless-stopped
environment:
LT_UPDATE_MODELS: true
volumes:
- libretranslate_models:/home/libretranslate/.local:rw
healthcheck:
test: ['CMD-SHELL', './venv/bin/python scripts/healthcheck.py']
interval: 10s
timeout: 4s
retries: 4
start_period: 5s
volumes:
libretranslate_models:
For GPU-accelerated translation (if you have NVIDIA GPU available):
.. code-block:: yaml
services:
libretranslate:
image: libretranslate/libretranslate:latest-cuda
command: --disable-web-ui
restart: unless-stopped
environment:
LT_UPDATE_MODELS: true
PUID: root
volumes:
- libretranslate_models:/home/libretranslate/.local:rw
healthcheck:
test: ['CMD-SHELL', './venv/bin/python scripts/healthcheck.py']
interval: 10s
timeout: 4s
retries: 4
start_period: 5s
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: 1
capabilities: [gpu]
volumes:
libretranslate_models:
After starting the services with ``docker compose down && docker compose up -d``,
configure LibreTranslate in Weblate:
1. Access the Weblate admin interface
2. Navigate to :guilabel:`Machine translation` → :guilabel:`Automatic suggestions`
3. Add a new LibreTranslate service with:
:Service: LibreTranslate
:API URL: ``http://libretranslate:5000``
:API key: Leave empty
LibreTranslate is now configured and available for machine translation in Weblate.
.. note::
* The LibreTranslate service runs without the web UI (``--disable-web-ui``) and is only accessible via the API within the Docker network.
* Models are automatically updated when the container starts. (``LT_UPDATE_MODELS: true``)
* Data is persisted using Docker volumes for optimal performance and data safety.
* Health checks ensure that the Docker engine properly observes the state of the service.
* For GPU acceleration, use the CUDA image variant and ensure your system has NVIDIA Docker support. This container runs as a privileged user to be able to use the GPU.
* No external ports are exposed, making the setup secure by default.
.. seealso::
* :ref:`mt-libretranslate`
* `LibreTranslate Docker documentation`_
* :ref:`machine-translation-setup`
.. _LibreTranslate Docker documentation: https://docs.libretranslate.com/guides/installation/#with-docker
.. _docker-anubis:
Anubis Docker container integration
+++++++++++++++++++++++++++++++++++
`Anubis`_ is a web AI firewall utility to block AI scrapers and other disruptive
traffic on the server. It is typically needed for publicly open Weblate
installations to avoid excessive load caused by scraping.
Anubis can be deployed using Docker Compose:
.. code-block:: yaml
anubis:
image: ghcr.io/techarohq/anubis:latest
environment:
BIND: ":8923"
DIFFICULTY: "4"
METRICS_BIND: ":9090"
SERVE_ROBOTS_TXT: "false"
OG_PASSTHROUGH: "false"
# The single space in TARGET enables subrequest authentication
TARGET: " "
# The redirect domain has to match WEBLATE_SITE_DOMAIN
REDIRECT_DOMAINS: weblate.example.com
# Generate a random private key using: openssl rand -hex 32
ED25519_PRIVATE_KEY_HEX: "..."
# Customize your Anubis policy
POLICY_FNAME: /data/botPolicies.yaml
healthcheck:
test: ["CMD", "anubis", "--healthcheck"]
interval: 5s
timeout: 30s
retries: 5
start_period: 500ms
volumes:
- anubis-data:/data
volumes:
anubis-data:
.. note::
The ``anubis-data`` volume in the above configuration is expected to contain
:file:`botPolicies.yaml` with a bot policy configured to your needs.
At minimum, you need to adjust status codes as described in
https://anubis.techaro.lol/docs/admin/configuration/subrequest-auth.
It is also recommended to configure persistent storage backend as described in
https://anubis.techaro.lol/docs/admin/policies/#storage-backends.
You can then turn on the Anubis usage in Weblate using:
.. code-block:: yaml
environment:
WEBLATE_ANUBIS_URL: http://anubis:8923
.. seealso::
:envvar:`WEBLATE_ANUBIS_URL`
Configuring PostgreSQL server
-----------------------------
The PostgreSQL container uses default PostgreSQL configuration and it won't
effectively utilize your CPU cores or memory. It is recommended to customize
the configuration to improve the performance.
The configuration can be adjusted as described in `Database Configuration` at
https://hub.docker.com/_/postgres. The configuration matching your environment
can be generated using https://pgtune.leopard.in.ua/.
Container internals
-------------------
The container is using :program:`supervisor` to start individual services. In
case of :ref:`docker-scaling`, it only starts single service in a container.
To check the services status use:
.. code-block:: sh
docker compose exec --user weblate weblate supervisorctl status
There are individual services for each Celery queue (see :ref:`celery` for
details). You can stop processing some tasks by stopping the appropriate worker:
.. code-block:: sh
docker compose exec --user weblate weblate supervisorctl stop celery-translate
Reference in a new issue View git blame Copy permalink