# Instalarea folosind 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.
## Cerințe hardware
Weblate should run on any contemporary hardware without problems, the following is
the minimal configuration required to run Weblate on a single host (Weblate, database
and web server):
* 3 GB of RAM
* 2 nuclee CPU
* 1 GB de spațiu de stocare
#### NOTE
Cerințele reale pentru instalarea Weblate variază foarte mult în funcție de dimensiunea traducerilor gestionate în cadrul acesteia.
### Memory usage
The more memory the better - it is used for caching on all
levels (file system, database and Weblate).
For hundreds of translation components, at least 4 GB of RAM is
recommended.
#### HINT
For systems with less memory than recommended, [Single-process Celery setup](https://docs.weblate.org/ro/latest/admin/install.md#minimal-celery) is recommended.
### CPU usage
Many concurrent users increase the amount of needed CPU cores.
Weblate 2026.8 introduced NumPy as a required dependency. On x86-64 systems,
the optimized NumPy build bundled in the Docker image requires an x86-64-v2
compatible CPU. Without the required CPU features, NumPy fails to load and
Weblate cannot start.
Before upgrading, check for the required SSE4.2 CPU feature on the Linux system
running Docker:
```sh
grep sse4_2 /proc/cpuinfo
```
Empty output indicates that a required CPU feature is unavailable. This is a
preliminary check; finding SSE4.2 does not verify all x86-64-v2 CPU features.
If Docker runs in a virtual machine, run the check inside the guest. Virtual
machines can hide CPU features supported by the host. Configure the virtual
machine to expose the required host CPU features, then reboot the guest. If
the physical CPU lacks the required features, upgrade the hardware.
### Storage usage
The typical database storage usage is around 300 MB per 1 million hosted words.
Storage space needed for cloned repositories varies, but Weblate tries to keep
their size minimal by doing shallow clones.
### Storage performance
Version control operations perform many filesystem metadata lookups. The
`vcs` subdirectory in [`DATA_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DATA_DIR) therefore needs low read
latency; storage with slow metadata access can make operations such as
**git status** take a long time even when its bulk throughput is good.
Keep [`CACHE_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CACHE_DIR) on low-latency local or temporary storage when
possible.
The deployment checks measure metadata lookup latency for both locations and
warn when the median latency exceeds 10 milliseconds. This is an approximate
point-in-time measurement affected by filesystem and system load. Rerun
**weblate check --deploy** before changing the storage configuration.
### Nodes
For small and medium-sized sites (millions of hosted words), all Weblate components (see
[Architecture overview](https://docs.weblate.org/ro/latest/admin/install.md#architecture)) can be run on a single node.
When you grow to hundreds of millions of hosted words, it is recommended to
have a dedicated node for database (see [Configurarea bazei de date pentru Weblate](https://docs.weblate.org/ro/latest/admin/install.md#database-setup)).
## Instalare
#### 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
[Certificate SSL automate folosind Let’s Encrypt](#docker-https-portal). For larger setups, please see
[Scalare pe orizontală](#docker-scaling).
1. Clonați repo-ul weblate-docker:
```sh
git clone https://github.com/WeblateOrg/docker-compose.git weblate-docker
cd weblate-docker
```
#### NOTE
The Docker Compose files are example deployment configurations. Operators
typically customize them for their own deployment and maintain those local
changes. Weblate application updates are delivered through Docker image
tags; there is no release-bound update path for customized Compose files.
2. Creați un fișier `docker-compose.override.yml` cu setările dumneavoastră. Consultați [Variabile de mediu Docker](#docker-environment) pentru lista completă a variabilelor de mediu.
```yaml
services:
weblate:
image: weblate/weblate:latest
environment:
WEBLATE_EMAIL_HOST: smtp.example.com
WEBLATE_EMAIL_HOST_USER: user
WEBLATE_EMAIL_HOST_PASSWORD: pass
WEBLATE_SERVER_EMAIL: weblate@example.com
WEBLATE_DEFAULT_FROM_EMAIL: weblate@example.com
WEBLATE_SITE_DOMAIN: weblate.example.com
WEBLATE_ADMIN_PASSWORD: password for the admin user
WEBLATE_ADMIN_EMAIL: weblate.admin@example.com
ports:
- 80:8080
```
#### NOTE
Dacă [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD) nu este setat, utilizatorul administrator este creat cu o parolă aleatorie afișată la prima pornire.
Exemplul furnizat face ca Weblate să asculte pe portul 80, editați maparea porturilor în fișierul `docker-compose.override.yml` pentru a o modifica.
3. Porniți containerele Weblate:
```sh
docker compose up
```
Bucurați-vă de implementarea Weblate, acesta este accesibil pe portul 80 al containerului `weblate`.
#### SEE ALSO
[Invocarea comenzilor de gestionare](https://docs.weblate.org/ro/latest/admin/management.md#invoke-manage)
## Choosing Docker image registry
Weblate containers are published to following registries:
* Docker Hub, see [https://hub.docker.com/r/weblate/weblate](https://hub.docker.com/r/weblate/weblate)
* GitHub Packages registry, see [https://github.com/WeblateOrg/docker/pkgs/container/weblate](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:
| Denumirea etichetei | Descriere | Caz de utilizare |
|----------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|
| `latest` | Weblate versiune stabilă, se potrivește cu cea mai recentă versiune etichetată | Actualizări continue într-un mediu de producție |
| `` | Weblate versiune stabilă | Rolling updates within a calendar year in a production environment |
| `.` | Weblate versiune stabilă | Rolling updates within a monthly release in a production environment |
| `...` | Weblate versiune stabilă | Implementare bine definită într-un mediu de producție |
| `edge` | Versiune stabilă Weblate cu modificări de dezvoltare în containerul Docker (de exemplu, dependențe actualizate) | Rularea actualizărilor într-un mediu de pregătire |
| `edge--` | Versiune stabilă Weblate cu modificări de dezvoltare în containerul Docker (de exemplu, dependențe actualizate) | Implementare bine definită într-un mediu de staționare |
| `bleeding` | Versiunea de dezvoltare Weblate din Git | Rolling updates to test upcoming Weblate features |
| `bleeding--` | Versiunea de dezvoltare Weblate din Git | Implementare bine definită pentru a testa viitoarele caracteristici Weblate |
Fiecare imagine este testată de către CI înainte de a fi publicată, astfel încât chiar și versiunea „sângerândă” ar trebui să fie destul de sigură pentru utilizare.
Full list of published tags can be found at [GitHub Packages](https://github.com/WeblateOrg/docker/pkgs/container/weblate/versions?filters%5Bversion_type%5D=tagged)
## Container Docker cu suport HTTPS
Vă rugăm să consultați [Instalare](#docker-deploy) pentru instrucțiuni generice de implementare, această secțiune menționează doar diferențele față de aceasta.
### 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
[Rularea în spatele unui proxy invers](https://docs.weblate.org/ro/latest/admin/install.md#reverse-proxy).
```nginx
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;
}
```
```sh
WEBLATE_ENABLE_HTTPS=1
WEBLATE_IP_PROXY_HEADER=HTTP_X_FORWARDED_FOR
WEBLATE_TRUSTED_PROXY_ADDRESSES=192.0.2.10
```
Replace the example trusted proxy address with the address or network of the
reverse proxy as seen by the Weblate container. Make sure that untrusted
clients cannot reach a published container port by bypassing the reverse
proxy.
### Utilizarea certificatelor SSL proprii
În cazul în care aveți propriul certificat SSL pe care doriți să îl utilizați, plasați pur și simplu fișierele în volumul de date Weblate (a se vedea [Volumele containerelor Docker](#docker-volume)):
* `ssl/fullchain.pem` care conține certificatul, inclusiv toate certificatele CA necesare
* `ssl/privkey.pem` conținând cheia privată
Ambele fișiere trebuie să fie deținute de același utilizator ca și cel care pornește containerul docker și să aibă masca de fișier setată la `600` (poate fi citită și scrisă numai de către utilizatorul proprietar).
În plus, containerul Weblate va accepta acum conexiuni SSL pe portul 4443, veți dori să includeți redirecționarea portului pentru HTTPS în suprascrierea docker compose:
```yaml
version: '3'
services:
weblate:
ports:
- 80:8080
- 443:4443
```
Dacă găzduiți deja alte site-uri pe același server, este posibil ca porturile `80` și `443` să fie utilizate de un proxy invers, cum ar fi NGINX. Pentru a transmite conexiunea HTTPS de la NGINX la containerul docker, puteți utiliza următoarea configurație:
```nginx
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name ;
ssl_certificate /etc/letsencrypt/live//fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live//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:;
}
}
```
Înlocuiți ``, `` și `` cu valorile reale din mediul dumneavoastră.
### Certificate SSL automate folosind Let’s Encrypt
În cazul în care doriți să utilizați certificatele SSL generate automat de [Let’s Encrypt](https://letsencrypt.org/) pe instalația publică, trebuie să adăugați un proxy HTTPS invers un container Docker suplimentar, [https-portal](https://hub.docker.com/r/steveltn/https-portal/) va fi utilizat pentru aceasta. Acest lucru este utilizat în fișierul `docker-compose-https.yml`. Apoi creați un fișier `docker-compose-https.override.yml` cu setările dumneavoastră:
```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 **docker compose** you need to pass both files to it,
and then do:
```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
```
## Actualizarea containerului Docker
De obicei, este o idee bună să actualizați doar containerul Weblate și să păstrați containerul PostgreSQL la versiunea pe care o aveți, deoarece actualizarea PostgreSQL este destul de dureroasă și, în majoritatea cazurilor, nu aduce multe beneficii.
Puteți face acest lucru rămânând la docker-compose existent și doar să extrageți cele mai recente imagini și apoi să reporniți:
```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
```
Baza de date Weblate ar trebui să fie migrată automat la prima pornire și nu ar trebui să fie nevoie de acțiuni manuale suplimentare.
#### NOTE
Direct upgrades are only supported for releases from the current or previous
calendar year. If you need to upgrade from an older release, upgrade first
to an intermediate version listed in [Version-specific instructions](https://docs.weblate.org/ro/latest/admin/upgrade.md#version-specific-instructions).
If you use the example Compose files without local changes, you can also
review updates in the `docker-compose` repository, though this is not needed
for most Weblate upgrades. Customized Compose files need to be maintained as
part of your deployment. See [Actualizarea containerului PostgreSQL](#docker-postgres-upgrade) for upgrading the
PostgreSQL server.
### Actualizarea containerului PostgreSQL
#### 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.
Containerele PostgreSQL nu acceptă actualizarea automată între versiuni, trebuie să efectuați actualizarea manual. Următorii pași prezintă una dintre opțiunile de actualizare.
#### SEE ALSO
[https://github.com/docker-library/postgres/issues/37](https://github.com/docker-library/postgres/issues/37)
1. Opriți containerul Weblate:
```shell
docker compose stop weblate cache
```
2. Efectuați o copie de rezervă a bazei de date:
```shell
docker compose exec database pg_dumpall --clean --if-exists --username weblate > backup.sql
```
3. Opriți containerul bazei de date:
```shell
docker compose stop database
```
4. Eliminați volumul PostgreSQL:
```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. Ajustați `docker-compose.yml` pentru a utiliza noua versiune PostgreSQL.
6. Porniți containerul bazei de date:
```shell
docker compose up -d database
```
7. Restaurați baza de date din backup:
```shell
cat backup.sql | docker compose exec -T database psql --username weblate --dbname weblate
```
#### HINT
Please check that the database name matches [`POSTGRES_DB`](#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:
```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 [`POSTGRES_DB`](#envvar-POSTGRES_DB).
9. Porniți toate containerele rămase:
```shell
docker compose up -d
```
## Autentificare administrator
După configurarea containerului, vă puteți autentifica ca utilizator admin cu parola furnizată în [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD), sau cu o parolă aleatorie generată la prima pornire, dacă aceasta nu a fost setată.
Pentru a reseta parola admin, reporniți containerul cu [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD) setat la noua parolă.
#### SEE ALSO
* [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD)
* [`WEBLATE_ADMIN_NAME`](#envvar-WEBLATE_ADMIN_NAME)
* [`WEBLATE_ADMIN_EMAIL`](#envvar-WEBLATE_ADMIN_EMAIL)
## Numărul de procese și consumul de memorie
The number of worker processes for both the web application 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.
By default, one combined Celery worker handles all task queues using a prefork
pool with three times [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS) processes. Sharing the initial
application memory between all Celery workers reduces memory usage while the
higher process count increases task throughput.
În cazul în care aveți o mulțime de nuclee CPU și nu mai aveți probleme de memorie, încercați să reduceți numărul de lucrători:
```yaml
environment:
WEBLATE_WORKERS: 2
```
You can fine-tune the combined worker:
```yaml
environment:
CELERY_COMBINED_OPTIONS: --concurrency 12 --prefetch-multiplier 1
```
Alternatively, use the split mode to run and fine-tune individual worker
categories:
```yaml
environment:
CELERY_WORKER_MODE: split
WEB_WORKERS: 4
WEB_BLOCKING_THREADS: 4
CELERY_MAIN_OPTIONS: --concurrency 2 --prefetch-multiplier 1
CELERY_NOTIFY_OPTIONS: --concurrency 1 --prefetch-multiplier 4
CELERY_MEMORY_OPTIONS: --concurrency 1 --prefetch-multiplier 1
CELERY_TRANSLATE_OPTIONS: --concurrency 1 --prefetch-multiplier 1
CELERY_BACKUP_OPTIONS: --concurrency 1 --prefetch-multiplier 1
```
The prefetch multiplier controls how many tasks each worker execution slot can
reserve. The default of one avoids reserving additional long-running or
payload-heavy tasks. The notification worker uses four in this example because
its short tasks can benefit from buffering. Increase the value only after
measuring queue latency and worker memory usage.
Memory usage can be further reduced by running Celery in a single process:
```yaml
environment:
CELERY_WORKER_MODE: single
```
#### SEE ALSO
* [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS)
* [`CELERY_WORKER_MODE`](#envvar-CELERY_WORKER_MODE)
* [`CELERY_COMBINED_OPTIONS`](#envvar-CELERY_COMBINED_OPTIONS)
* [`CELERY_MAIN_OPTIONS`](#envvar-CELERY_MAIN_OPTIONS)
* [`CELERY_NOTIFY_OPTIONS`](#envvar-CELERY_NOTIFY_OPTIONS)
* [`CELERY_MEMORY_OPTIONS`](#envvar-CELERY_MEMORY_OPTIONS)
* [`CELERY_TRANSLATE_OPTIONS`](#envvar-CELERY_TRANSLATE_OPTIONS)
* [`CELERY_BACKUP_OPTIONS`](#envvar-CELERY_BACKUP_OPTIONS)
* [`CELERY_BEAT_OPTIONS`](#envvar-CELERY_BEAT_OPTIONS)
* [`CELERY_SINGLE_OPTIONS`](#envvar-CELERY_SINGLE_OPTIONS)
* [`WEBLATE_ASGI`](#envvar-WEBLATE_ASGI)
* [`WEB_WORKERS`](#envvar-WEB_WORKERS)
* [`WEB_BLOCKING_THREADS`](#envvar-WEB_BLOCKING_THREADS)
## Scalare pe orizontală
#### Versionadded
Added in version 4.6.
Puteți rula mai multe containere Weblate pentru a scala serviciul pe orizontală. Volumul `/app/data` trebuie să fie partajat de toate containerele, pentru aceasta se recomandă utilizarea unui sistem de fișiere cluster, cum ar fi GlusterFS. Volumul `/app/cache` trebuie să fie separat pentru fiecare container.
Each Weblate container has defined role using [`WEBLATE_SERVICE`](#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.
Puteți găsi un exemplu de configurare în repo-ul `docker-compose` ca [docker-compose-split.yml](https://github.com/WeblateOrg/docker-compose/blob/main/docker-compose-split.yml).
## Startup configuration warnings
The Docker container records actionable configuration warnings from startup
in the shared `/app/data` volume. They are shown by
**weblate check --deploy** and in the [Raport de performanță](https://docs.weblate.org/ro/latest/admin/admin.md#manage-performance)
management interface, in addition to being written to the container log.
Each container reports its warnings separately. This keeps warnings from
containers with different [`WEBLATE_SERVICE`](#envvar-WEBLATE_SERVICE) roles visible in a
horizontally scaled deployment. Reports are refreshed while their container is
running and are removed during an orderly container shutdown. Reports left by
an abrupt shutdown expire after five minutes, and stale report files are
cleaned up automatically by later container startups.
## Variabile de mediu Docker
Many of Weblate’s [Configurație](https://docs.weblate.org/ro/latest/admin/config.md#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 [Configuration beyond environment variables](#docker-custom-config).
### Passing secrets
#### Versionadded
Added in version 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 `docker-compose.yml` might look like:
```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
```
#### SEE ALSO
[How to use secrets in Docker Compose](https://docs.docker.com/compose/how-tos/use-secrets/)
### Setări generice
### WEBLATE_DEBUG
Configurează modul de depanare Django folosind [`DEBUG`](https://docs.weblate.org/ro/latest/admin/install.md#std-setting-DEBUG).
**Exemplu:**
```yaml
environment:
WEBLATE_DEBUG: 1
```
#### SEE ALSO
[Dezactivați modul de depanare](https://docs.weblate.org/ro/latest/admin/install.md#production-debug)
### WEBLATE_LOGLEVEL
Configures the logging verbosity. Set this to `DEBUG` to get more detailed logs.
Defaults to `INFO` when [`WEBLATE_DEBUG`](#envvar-WEBLATE_DEBUG) is turned off, `DEBUG` is used when debug mode is turned on.
For more silent logging use `ERROR` or `WARNING`.
### WEBLATE_LOGLEVEL_DATABASE
Configurează înregistrarea în jurnal a verbozității interogărilor bazei de date.
### WEBLATE_LOG_GELF_HOST
#### Versionadded
Added in version 5.9.
Configures remote logging using GELF TCP connection. Can be used to integrate with Graylog.
### WEBLATE_LOG_GELF_PORT
#### Versionadded
Added in version 5.9.
Use custom port for [`WEBLATE_LOG_GELF_HOST`](#envvar-WEBLATE_LOG_GELF_HOST), defaults to 12201.
### WEBLATE_SITE_TITLE
Schimbă titlul site-ului afișat în antetul tuturor paginilor.
### WEBLATE_SITE_DOMAIN
Configures the site domain. This parameter is required and accepts a
hostname or IPv4 address.
Include a port between 1 and 65535 if using a non-standard one. IPv6
addresses are not currently supported.
**Exemplu:**
```yaml
environment:
WEBLATE_SITE_DOMAIN: example.com:8080
```
#### SEE ALSO
* [Setați domeniul corect al site-ului](https://docs.weblate.org/ro/latest/admin/install.md#production-site)
* [`SITE_DOMAIN`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SITE_DOMAIN)
### WEBLATE_ADMIN_NAME
### WEBLATE_ADMIN_EMAIL
Configurează numele și adresa de e-mail ale administratorului site-ului. Este utilizat atât pentru setarea [`ADMINS`](https://docs.weblate.org/ro/latest/admin/install.md#std-setting-ADMINS), cât și pentru crearea utilizatorului admin (a se vedea [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD) pentru mai multe informații în acest sens).
**Exemplu:**
```yaml
environment:
WEBLATE_ADMIN_NAME: Weblate admin
WEBLATE_ADMIN_EMAIL: noreply@example.com
```
#### SEE ALSO
* [Autentificare administrator](#docker-admin-login)
* [Configurați în mod corespunzător administratorii](https://docs.weblate.org/ro/latest/admin/install.md#production-admins)
* [`ADMINS`](https://docs.weblate.org/ro/latest/admin/install.md#std-setting-ADMINS)
### WEBLATE_ADMIN_PASSWORD
Stabilește parola pentru utilizatorul admin.
* Dacă nu este setat și utilizatorul admin nu există, acesta este creat cu o parolă aleatorie afișată la prima pornire a containerului.
* Dacă nu este setat și există utilizatorul admin, nu se efectuează nicio acțiune.
* Dacă este setat, utilizatorul admin este ajustat la fiecare pornire a containerului pentru a se potrivi cu [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD), [`WEBLATE_ADMIN_NAME`](#envvar-WEBLATE_ADMIN_NAME) și [`WEBLATE_ADMIN_EMAIL`](#envvar-WEBLATE_ADMIN_EMAIL).
#### WARNING
Stocarea parolei în fișierul de configurare ar putea reprezenta un risc de securitate. Luați în considerare utilizarea acestei variabile numai pentru configurarea inițială (sau lăsați Weblate să genereze o parolă aleatorie la pornirea inițială) sau pentru recuperarea parolei.
#### SEE ALSO
* [Autentificare administrator](#docker-admin-login)
* [Passing secrets](#docker-secrets)
* [`WEBLATE_ADMIN_PASSWORD`](#envvar-WEBLATE_ADMIN_PASSWORD)
* [`WEBLATE_ADMIN_NAME`](#envvar-WEBLATE_ADMIN_NAME)
* [`WEBLATE_ADMIN_EMAIL`](#envvar-WEBLATE_ADMIN_EMAIL)
### 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.
#### SEE ALSO
* [Security implications](https://docs.djangoproject.com/en/stable/topics/logging/#logging-security-implications)
* [`ROLLBAR_KEY`](#envvar-ROLLBAR_KEY)
* [`SENTRY_DSN`](#envvar-SENTRY_DSN)
### WEBLATE_SERVER_EMAIL
Adresa de e-mail de la care sunt trimise mesajele de eroare.
#### SEE ALSO
* [`SERVER_EMAIL`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-SERVER_EMAIL)
* [Configurați trimiterea de e-mailuri](https://docs.weblate.org/ro/latest/admin/install.md#production-email)
### WEBLATE_DEFAULT_FROM_EMAIL
Configurează adresa pentru e-mailurile de ieșire.
#### SEE ALSO
* [`DEFAULT_FROM_EMAIL`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-DEFAULT_FROM_EMAIL)
* [Configurați trimiterea de e-mailuri](https://docs.weblate.org/ro/latest/admin/install.md#production-email)
### WEBLATE_ADMINS_CONTACT
Configures [`ADMINS_CONTACT`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ADMINS_CONTACT).
### WEBLATE_CONTACT_FORM
Configurează comportamentul formularului de contact, a se vedea [`CONTACT_FORM`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CONTACT_FORM).
### WEBLATE_ALLOWED_HOSTS
Configurează numele de gazdă HTTP permise folosind [`ALLOWED_HOSTS`](https://docs.weblate.org/ro/latest/admin/install.md#std-setting-ALLOWED_HOSTS).
Valoarea implicită este `*` care permite toate numele de gazdă.
**Exemplu:**
```yaml
environment:
WEBLATE_ALLOWED_HOSTS: weblate.example.com,example.com
```
#### SEE ALSO
* [`ALLOWED_HOSTS`](https://docs.weblate.org/ro/latest/admin/install.md#std-setting-ALLOWED_HOSTS)
* [Configurarea gazdelor permise](https://docs.weblate.org/ro/latest/admin/install.md#production-hosts)
* [Setați domeniul corect al site-ului](https://docs.weblate.org/ro/latest/admin/install.md#production-site)
### WEBLATE_REGISTRATION_OPEN
Configurează dacă înregistrările sunt deschise prin activarea [`REGISTRATION_OPEN`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REGISTRATION_OPEN).
**Exemplu:**
```yaml
environment:
WEBLATE_REGISTRATION_OPEN: 0
```
### WEBLATE_REGISTRATION_CAPTCHA
#### Versionadded
Added in version 5.10.
Configures whether captcha is used for registration and other unauthenticated actions, see [`REGISTRATION_CAPTCHA`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REGISTRATION_CAPTCHA).
**Exemplu:**
```yaml
environment:
WEBLATE_REGISTRATION_CAPTCHA: 0
```
### WEBLATE_REGISTRATION_ALLOW_BACKENDS
Configurați ce metode de autentificare pot fi folosite pentru a crea un cont nou prin [`REGISTRATION_ALLOW_BACKENDS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REGISTRATION_ALLOW_BACKENDS).
> **Exemplu:**
> ```yaml
> environment:
> WEBLATE_REGISTRATION_OPEN: 0
> WEBLATE_REGISTRATION_ALLOW_BACKENDS: azuread-oauth2,azuread-tenant-oauth2
> ```
### WEBLATE_REGISTRATION_REBIND
#### Versionadded
Added in version 4.16.
Configures [`REGISTRATION_REBIND`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REGISTRATION_REBIND).
### WEBLATE_REGISTRATION_ALLOW_DISPOSABLE_EMAILS
#### Versionadded
Added in version 5.16.1.
Configures [`REGISTRATION_ALLOW_DISPOSABLE_EMAILS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REGISTRATION_ALLOW_DISPOSABLE_EMAILS).
**Exemplu:**
```yaml
environment:
WEBLATE_REGISTRATION_ALLOW_DISPOSABLE_EMAILS: 1
```
### WEBLATE_PROJECT_WEB_RESTRICT_PRIVATE
#### Versionadded
Added in version 5.17.
Configures [`PROJECT_WEB_RESTRICT_PRIVATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_WEB_RESTRICT_PRIVATE).
Defaults to enabled.
### WEBLATE_PROJECT_WEB_RESTRICT_ALLOWLIST
#### Versionadded
Added in version 5.17.
Configures [`PROJECT_WEB_RESTRICT_ALLOWLIST`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_WEB_RESTRICT_ALLOWLIST).
Expects a comma-separated list of trusted project slugs.
### WEBLATE_WEBHOOK_RESTRICT_PRIVATE
#### Versionadded
Added in version 5.17.
Configures [`WEBHOOK_RESTRICT_PRIVATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBHOOK_RESTRICT_PRIVATE).
Defaults to enabled.
### WEBLATE_WEBHOOK_PRIVATE_ALLOWLIST
#### Versionadded
Added in version 5.17.
Configures [`WEBHOOK_PRIVATE_ALLOWLIST`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBHOOK_PRIVATE_ALLOWLIST).
Expects a comma-separated list of trusted hostnames or domains.
### WEBLATE_ALLOWED_ASSET_SIZE
#### Versionadded
Added in version 2025.7.
Configures [`ALLOWED_ASSET_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ALLOWED_ASSET_SIZE).
### WEBLATE_ASSET_RESTRICT_PRIVATE
#### Versionadded
Added in version 2025.5.
Configures [`ASSET_RESTRICT_PRIVATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ASSET_RESTRICT_PRIVATE).
Defaults to enabled.
### WEBLATE_ASSET_PRIVATE_ALLOWLIST
#### Versionadded
Added in version 2025.5.
Configures [`ASSET_PRIVATE_ALLOWLIST`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ASSET_PRIVATE_ALLOWLIST).
Expects a comma-separated list of trusted hostnames or domains.
### WEBLATE_TIME_ZONE
Configurează fusul orar utilizat în Weblate, vezi [`TIME_ZONE`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-TIME_ZONE).
#### NOTE
Pentru a schimba fusul orar al containerului Docker în sine, utilizați variabila de mediu `TZ`.
**Exemplu:**
```yaml
environment:
WEBLATE_TIME_ZONE: Europe/Prague
```
### WEBLATE_ENABLE_HTTPS
Face ca Weblate să presupună că este operat în spatele unui proxy HTTPS inversat, face ca Weblate să utilizeze HTTPS în e-mail și în legăturile API sau să seteze indicatori de siguranță pe cookie-uri.
#### HINT
Vă rugăm să consultați documentația [`ENABLE_HTTPS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ENABLE_HTTPS) pentru eventualele avertismente.
#### NOTE
Acest lucru nu face ca containerul Weblate să accepte conexiuni HTTPS, trebuie să configurați și acest lucru, consultați [Container Docker cu suport HTTPS](#docker-ssl) pentru exemple.
**Exemplu:**
```yaml
environment:
WEBLATE_ENABLE_HTTPS: 1
```
#### SEE ALSO
* [`ENABLE_HTTPS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ENABLE_HTTPS)
* [Setați domeniul corect al site-ului](https://docs.weblate.org/ro/latest/admin/install.md#production-site)
* [`WEBLATE_SECURE_PROXY_SSL_HEADER`](#envvar-WEBLATE_SECURE_PROXY_SSL_HEADER)
### WEBLATE_NGINX_IPV6
#### Versionadded
Added in version 5.17.
Controls whether the bundled NGINX listens on IPv6 addresses.
Supported values are:
* `auto` to enable IPv6 listeners only when IPv6 is available in the
container runtime. This is the default.
* `on` to always enable IPv6 listeners.
* `off` to disable IPv6 listeners.
**Exemplu:**
```yaml
environment:
WEBLATE_NGINX_IPV6: auto
```
### WEBLATE_IP_PROXY_HEADER
Permite lui Weblate să extragă adresa IP din orice antet HTTP dat. Utilizați această opțiune atunci când utilizați un proxy invers în fața containerului Weblate.
Activează [`IP_BEHIND_REVERSE_PROXY`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-IP_BEHIND_REVERSE_PROXY) și setează [`IP_PROXY_HEADER`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-IP_PROXY_HEADER).
When set to `HTTP_X_FORWARDED_FOR`, the bundled nginx resolves the client
address using [`WEBLATE_TRUSTED_PROXY_ADDRESSES`](#envvar-WEBLATE_TRUSTED_PROXY_ADDRESSES), uses that address
in its logs, and forwards one normalized address to Weblate.
#### Versionchanged
Schimbat în versiunea 2026.9: The bundled nginx no longer trusts `X-Forwarded-For` from all network
addresses. Trusted proxy addresses have to be configured explicitly.
#### NOTE
Formatul trebuie să fie în conformitate cu așteptările Django. Acesta [transformă](https://docs.djangoproject.com/en/2.2/ref/request-response/#django.http.HttpRequest.META) numele brute ale antetului HTTP după cum urmează:
- convertește toate caracterele în majuscule
- înlocuiește orice cratimă cu sublinieri
- adaugă prefixul `HTTP_` \`\`
Așadar, `X-Forwarded-For` ar trebui să fie corespondat cu `HTTP_X_FORWARDED_FOR`.
**Exemplu:**
```yaml
environment:
WEBLATE_IP_PROXY_HEADER: HTTP_X_FORWARDED_FOR
WEBLATE_TRUSTED_PROXY_ADDRESSES: "192.0.2.10 2001:db8::/64 proxy"
```
### WEBLATE_TRUSTED_PROXY_ADDRESSES
#### Versionadded
Added in version 2026.9.
Configures the IPv4 or IPv6 addresses, networks, or hostnames of reverse
proxies trusted by the bundled nginx to supply `X-Forwarded-For`. Separate
multiple values by whitespace.
This setting is used only when [`WEBLATE_IP_PROXY_HEADER`](#envvar-WEBLATE_IP_PROXY_HEADER) is
`HTTP_X_FORWARDED_FOR`. If the list is empty, nginx uses the immediate TCP
peer in its logs and forwards that address to Weblate.
Only list proxies under your control, and do not expose the Weblate
container through a path which bypasses them.
**Exemplu:**
```yaml
environment:
WEBLATE_IP_PROXY_HEADER: HTTP_X_FORWARDED_FOR
WEBLATE_TRUSTED_PROXY_ADDRESSES: "192.0.2.10 2001:db8::/64 proxy"
```
### WEBLATE_IP_PROXY_OFFSET
#### Versionadded
Added in version 5.0.1.
Configures [`IP_PROXY_OFFSET`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-IP_PROXY_OFFSET).
When [`WEBLATE_IP_PROXY_HEADER`](#envvar-WEBLATE_IP_PROXY_HEADER) is `HTTP_X_FORWARDED_FOR`, the
bundled nginx forwards one normalized address and the container uses an
effective offset of `0`.
### WEBLATE_USE_X_FORWARDED_PORT
#### Versionadded
Added in version 5.0.1.
A boolean that specifies whether to use the *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.
#### SEE ALSO
[`USE_X_FORWARDED_PORT`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-USE_X_FORWARDED_PORT)
#### NOTE
This is a boolean setting (use `"true"` or `"false"`).
### WEBLATE_SECURE_PROXY_SSL_HEADER
A tuple representing an 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.
**Exemplu:**
```yaml
environment:
WEBLATE_SECURE_PROXY_SSL_HEADER: HTTP_X_FORWARDED_PROTO,https
```
#### SEE ALSO
* [Rularea în spatele unui proxy invers](https://docs.weblate.org/ro/latest/admin/install.md#reverse-proxy)
* [`SECURE_PROXY_SSL_HEADER`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-SECURE_PROXY_SSL_HEADER)
### WEBLATE_REQUIRE_LOGIN
Activează [`REQUIRE_LOGIN`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REQUIRE_LOGIN) pentru a impune autentificarea pe întregul Weblate.
**Exemplu:**
```yaml
environment:
WEBLATE_REQUIRE_LOGIN: 1
```
### WEBLATE_LEGAL_INTEGRATION
Enables the [Legal module](https://docs.weblate.org/ro/latest/admin/optionals.md#legal) module in Docker deployments.
By default, the integration is disabled; leave this variable unset or empty to disable it.
Supported values are:
* `tos-confirm` to enable the legal module and enforce legal document
confirmation during social authentication and for signed-in users.
* `wllegal` to enable the same integration and additionally load the
hosted legal document templates from `wllegal`. These templates are
used by services operated by Weblate s.r.o. and are not intended for
general use.
To provide your own legal documents in Docker, override the templates in
`/app/data/python/customize/templates/legal/documents`, see
[Înlocuirea logo-ului și a altor fișiere statice](#docker-static-override).
Recreate the Docker container after changing this environment variable,
for example using **docker compose up -d**. Restarting an existing
container does not apply changed environment values.
**Exemplu:**
```yaml
environment:
WEBLATE_LEGAL_INTEGRATION: tos-confirm
```
#### SEE ALSO
* [Legal module](https://docs.weblate.org/ro/latest/admin/optionals.md#legal)
* [Înlocuirea logo-ului și a altor fișiere statice](#docker-static-override)
### WEBLATE_LEGAL_DOCUMENT_CSS_CLASS
Configures [`LEGAL_DOCUMENT_CSS_CLASS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LEGAL_DOCUMENT_CSS_CLASS) in Docker deployments with
[`WEBLATE_LEGAL_INTEGRATION`](#envvar-WEBLATE_LEGAL_INTEGRATION) enabled.
Set this to the class targeted by your custom legal stylesheet. Set it to
an empty string to render legal documents without a wrapper class.
**Exemplu:**
```yaml
environment:
WEBLATE_LEGAL_DOCUMENT_CSS_CLASS: ""
```
### WEBLATE_LEGAL_HIDDEN_DOCUMENTS
Configures [`LEGAL_HIDDEN_DOCUMENTS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LEGAL_HIDDEN_DOCUMENTS) in Docker deployments with
[`WEBLATE_LEGAL_INTEGRATION`](#envvar-WEBLATE_LEGAL_INTEGRATION) enabled.
Provide a comma-separated list of legal document page identifiers.
External legal documents are used as fallbacks for hidden internal pages.
The following configuration links both documents externally and requires
one agreement covering the terms of service and privacy policy:
**Exemplu:**
```yaml
environment:
WEBLATE_LEGAL_INTEGRATION: tos-confirm
WEBLATE_LEGAL_HIDDEN_DOCUMENTS: terms,privacy
WEBLATE_LEGAL_URL: https://example.com/terms/
WEBLATE_PRIVACY_URL: https://example.com/privacy/
```
### WEBLATE_PUBLIC_ENGAGE
Enables [`PUBLIC_ENGAGE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PUBLIC_ENGAGE).
### WEBLATE_GOOGLE_ANALYTICS_ID
Configurează ID-ul pentru Google Analytics prin modificarea [`GOOGLE_ANALYTICS_ID`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GOOGLE_ANALYTICS_ID).
### WEBLATE_DEFAULT_PULL_MESSAGE
Configures the default title and message for pull requests via API by changing
[`DEFAULT_PULL_MESSAGE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_PULL_MESSAGE).
#### SEE ALSO
[DEFAULT_PULL_MESSAGE](https://docs.weblate.org/ro/latest/admin/config.md#config-pull-message)
### WEBLATE_SIMPLIFY_LANGUAGES
Configurează politica de simplificare a limbilor, a se vedea [`SIMPLIFY_LANGUAGES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SIMPLIFY_LANGUAGES).
### WEBLATE_HIDE_SHARED_GLOSSARY_COMPONENTS
Hides glossary components when shared to other projects, see [`HIDE_SHARED_GLOSSARY_COMPONENTS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-HIDE_SHARED_GLOSSARY_COMPONENTS).
### WEBLATE_DEFAULT_ACCESS_CONTROL
Configurează controlul implicit [Control acces](https://docs.weblate.org/ro/latest/admin/projects.md#project-access-control) pentru proiectele noi, a se vedea [`DEFAULT_ACCESS_CONTROL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_ACCESS_CONTROL).
### WEBLATE_DEFAULT_TRANSLATION_REVIEW
#### Versionadded
Added in version 5.16.
Configures the default value for [Activează recenzii](https://docs.weblate.org/ro/latest/admin/projects.md#project-translation-review), turned off by default.
### WEBLATE_DEFAULT_SOURCE_REVIEW
#### Versionadded
Added in version 5.16.
Configures the default value for [Activează revizuiri sursă](https://docs.weblate.org/ro/latest/admin/projects.md#project-source-review), turned off by default.
### WEBLATE_DEFAULT_RESTRICTED_COMPONENT
Configurează valoarea implicită pentru [Acces restricționat](https://docs.weblate.org/ro/latest/admin/projects.md#component-restricted) pentru componentele noi, a se vedea [`DEFAULT_RESTRICTED_COMPONENT`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_RESTRICTED_COMPONENT).
### WEBLATE_DEFAULT_TRANSLATION_PROPAGATION
Configurează valoarea implicită pentru [Permite propagarea traducerii](https://docs.weblate.org/ro/latest/admin/projects.md#component-allow-translation-propagation) pentru componentele noi, a se vedea [`DEFAULT_TRANSLATION_PROPAGATION`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_TRANSLATION_PROPAGATION).
### WEBLATE_DEFAULT_COMMITER_EMAIL
Configurează [`DEFAULT_COMMITER_EMAIL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_COMMITER_EMAIL).
### WEBLATE_DEFAULT_COMMITER_NAME
Configurează [`DEFAULT_COMMITER_NAME`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_COMMITER_NAME).
### WEBLATE_DEFAULT_SHARED_TM
Configurează [`DEFAULT_SHARED_TM`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_SHARED_TM).
### WEBLATE_DEFAULT_AUTOCLEAN_TM
Configures [`DEFAULT_AUTOCLEAN_TM`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_AUTOCLEAN_TM).
### WEBLATE_COMMIT_PENDING_HOURS
Configures the default value for [Vârsta modificărilor care urmează să fie comise](https://docs.weblate.org/ro/latest/admin/projects.md#component-commit-pending-age) for new components, see [`COMMIT_PENDING_HOURS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-COMMIT_PENDING_HOURS).
### WEBLATE_GPG_IDENTITY
Configurează semnarea GPG a modificărilor, a se vedea [`WEBLATE_GPG_IDENTITY`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBLATE_GPG_IDENTITY).
#### SEE ALSO
[Semnarea comenzilor Git cu GnuPG](https://docs.weblate.org/ro/latest/admin/optionals.md#gpg-sign)
### WEBLATE_URL_PREFIX
Configures URL prefix where Weblate is running, see [`URL_PREFIX`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-URL_PREFIX).
Leave it empty to serve Weblate at the root, or use slash-separated path
segments starting with a slash, for example `/translations` or
`/tools/translations`. Each segment can contain ASCII letters, digits,
`_`, and `-`.
### WEBLATE_STATIC_URL
Configures URL prefix for static files served from [`CACHE_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CACHE_DIR).
### WEBLATE_SILENCED_SYSTEM_CHECKS
Configurează verificările care nu doriți să fie afișate, a se vedea [`SILENCED_SYSTEM_CHECKS`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-SILENCED_SYSTEM_CHECKS).
### WEBLATE_CSP_SCRIPT_SRC
### WEBLATE_CSP_IMG_SRC
### WEBLATE_CSP_CONNECT_SRC
### WEBLATE_CSP_STYLE_SRC
### WEBLATE_CSP_FONT_SRC
### WEBLATE_CSP_FORM_SRC
Allows to customize *Content-Security-Policy* HTTP header.
#### SEE ALSO
* [Politica de securitate a conținutului](https://docs.weblate.org/ro/latest/admin/install.md#csp)
* [`CSP_SCRIPT_SRC`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CSP_SCRIPT_SRC)
* [`CSP_IMG_SRC`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CSP_IMG_SRC)
* [`CSP_CONNECT_SRC`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CSP_CONNECT_SRC)
* [`CSP_STYLE_SRC`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CSP_STYLE_SRC)
* [`CSP_FONT_SRC`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CSP_FONT_SRC)
* [`CSP_FORM_SRC`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CSP_FORM_SRC)
### WEBLATE_LICENSE_FILTER
Configurează [`LICENSE_FILTER`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LICENSE_FILTER).
### WEBLATE_LICENSE_REQUIRED
Configures [`LICENSE_REQUIRED`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LICENSE_REQUIRED).
### WEBLATE_WEBSITE_REQUIRED
Configures [`WEBSITE_REQUIRED`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBSITE_REQUIRED).
### WEBLATE_VERSION_DISPLAY
Configures [`VERSION_DISPLAY`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VERSION_DISPLAY).
### WEBLATE_HIDE_VERSION
Configurează [`HIDE_VERSION`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-HIDE_VERSION).
### WEBLATE_BASIC_LANGUAGES
Configurează [`BASIC_LANGUAGES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-BASIC_LANGUAGES).
### WEBLATE_DEFAULT_AUTO_WATCH
Configurează [`DEFAULT_AUTO_WATCH`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DEFAULT_AUTO_WATCH).
### WEBLATE_RATELIMIT_ATTEMPTS
### WEBLATE_RATELIMIT_LOCKOUT
### WEBLATE_RATELIMIT_WINDOW
#### Versionadded
Added in version 4.6.
Configurează limitatorul de viteză.
#### HINT
Puteți seta configurația pentru orice rază de cuprindere a limitatorului de viteză. Pentru a face acest lucru, adăugați prefixul `WEBLATE_` la oricare dintre setările descrise în [Limitarea ratei](https://docs.weblate.org/ro/latest/admin/optionals.md#rate-limit).
#### SEE ALSO
* [Limitarea ratei](https://docs.weblate.org/ro/latest/admin/optionals.md#rate-limit)
* [`RATELIMIT_ATTEMPTS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-RATELIMIT_ATTEMPTS)
* [`RATELIMIT_WINDOW`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-RATELIMIT_WINDOW)
* [`RATELIMIT_LOCKOUT`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-RATELIMIT_LOCKOUT)
### WEBLATE_API_RATELIMIT_ANON
### WEBLATE_API_RATELIMIT_USER
#### Versionadded
Added in version 4.11.
Configures [`API_RATELIMIT_ANON`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-API_RATELIMIT_ANON) and [`API_RATELIMIT_USER`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-API_RATELIMIT_USER).
Defaults to `100/day` for anonymous and
`5000/hour` for authenticated users.
#### SEE ALSO
[Limitarea ratei API](https://docs.weblate.org/ro/latest/api.md#api-rate)
### WEBLATE_API_RATELIMIT_USER_OVERRIDES
### WEBLATE_API_RATELIMIT_IP_OVERRIDES
#### Versionadded
Added in version 2026.10.
JSON mappings configuring [`API_RATELIMIT_USER_OVERRIDES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-API_RATELIMIT_USER_OVERRIDES) and
[`API_RATELIMIT_IP_OVERRIDES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-API_RATELIMIT_IP_OVERRIDES). Both default to empty objects.
Use JSON `null` to exempt a user, IP address, or network from API throttling.
For example, in `compose.override.yaml`:
```yaml
services:
weblate:
environment:
WEBLATE_API_RATELIMIT_USER_OVERRIDES: '{"automation":"20000/hour"}'
WEBLATE_API_RATELIMIT_IP_OVERRIDES: '{"192.0.2.42":null,"198.51.100.0/24":"10000/hour"}'
```
Username rules take precedence over IP rules. See [Limitarea ratei API](https://docs.weblate.org/ro/latest/api.md#api-rate) for
counting behavior and proxy configuration requirements.
### WEBLATE_ENABLE_HOOKS
#### Versionadded
Added in version 4.13.
Configurează [`ENABLE_HOOKS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ENABLE_HOOKS).
### WEBLATE_ENABLE_AVATARS
#### Versionadded
Added in version 4.6.1.
Configurează [`ENABLE_AVATARS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ENABLE_AVATARS).
### WEBLATE_AVATAR_URL_PREFIX
#### Versionadded
Added in version 4.15.
Configurează [`AVATAR_URL_PREFIX`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-AVATAR_URL_PREFIX).
### WEBLATE_LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH
#### Versionadded
Added in version 4.9.
Configurează [`LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH).
### WEBLATE_SSH_EXTRA_ARGS
#### Versionadded
Added in version 4.9.
Configurează [`SSH_EXTRA_ARGS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SSH_EXTRA_ARGS).
### WEBLATE_BORG_EXTRA_ARGS
#### Versionadded
Added in version 4.9.
Configures [`BORG_EXTRA_ARGS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-BORG_EXTRA_ARGS) as a comma separated list of args.
**Exemplu:**
```yaml
environment:
WEBLATE_BORG_EXTRA_ARGS: --exclude,vcs/
```
### WEBLATE_ENABLE_SHARING
#### Versionadded
Added in version 4.14.1.
Configurează [`ENABLE_SHARING`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-ENABLE_SHARING).
### WEBLATE_SUPPORT_STATUS_CHECK
#### Versionadded
Added in version 5.5.
Configures [`SUPPORT_STATUS_CHECK`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SUPPORT_STATUS_CHECK).
### WEBLATE_EXTRA_HTML_HEAD
#### Versionadded
Added in version 4.15.
Configures [`EXTRA_HTML_HEAD`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-EXTRA_HTML_HEAD).
### WEBLATE_INTERNAL_BOT_EMAIL_TEMPLATE
#### Versionadded
Added in version 2026.7.1.
Configures [`INTERNAL_BOT_EMAIL_TEMPLATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-INTERNAL_BOT_EMAIL_TEMPLATE).
### WEBLATE_PRIVATE_COMMIT_EMAIL_TEMPLATE
#### Versionadded
Added in version 4.15.
Configures [`PRIVATE_COMMIT_EMAIL_TEMPLATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PRIVATE_COMMIT_EMAIL_TEMPLATE).
### WEBLATE_PRIVATE_COMMIT_EMAIL_OPT_IN
#### Versionadded
Added in version 4.15.
Configures [`PRIVATE_COMMIT_EMAIL_OPT_IN`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PRIVATE_COMMIT_EMAIL_OPT_IN).
### WEBLATE_PRIVATE_COMMIT_NAME_TEMPLATE
#### Versionadded
Added in version 5.16.
Configures [`PRIVATE_COMMIT_NAME_TEMPLATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PRIVATE_COMMIT_NAME_TEMPLATE).
### WEBLATE_PRIVATE_COMMIT_NAME_OPT_IN
#### Versionadded
Added in version 5.16.
Configures [`PRIVATE_COMMIT_NAME_OPT_IN`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PRIVATE_COMMIT_NAME_OPT_IN).
### WEBLATE_UNUSED_ALERT_DAYS
#### Versionadded
Added in version 4.17.
Configures [`UNUSED_ALERT_DAYS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-UNUSED_ALERT_DAYS).
### WEBLATE_REPORT_EXPIRY
#### Versionadded
Added in version 2026.8.
Configures [`REPORT_EXPIRY`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-REPORT_EXPIRY).
### WEBLATE_UPDATE_LANGUAGES
#### Versionadded
Added in version 4.3.2.
Configures [`UPDATE_LANGUAGES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-UPDATE_LANGUAGES).
### WEBLATE_VCS_ALLOW_HOSTS
#### Versionadded
Added in version 5.15.
Configures [`VCS_ALLOW_HOSTS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_ALLOW_HOSTS).
### WEBLATE_VCS_PRIVATE_ALLOWLIST
#### Versionadded
Added in version 2026.9.
Configures [`VCS_PRIVATE_ALLOWLIST`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_PRIVATE_ALLOWLIST).
### WEBLATE_VCS_ALLOW_SCHEMES
#### Versionadded
Added in version 5.15.
Configures [`VCS_ALLOW_SCHEMES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_ALLOW_SCHEMES).
### WEBLATE_VCS_RESTRICT_PRIVATE
#### Versionadded
Added in version 5.17.
Configures [`VCS_RESTRICT_PRIVATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_RESTRICT_PRIVATE).
### WEBLATE_VCS_CLONE_DEPTH
#### Versionadded
Added in version 5.4.
Configures [`VCS_CLONE_DEPTH`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_CLONE_DEPTH).
### WEBLATE_VCS_API_DELAY
#### Versionadded
Added in version 5.4.
Configures [`VCS_API_DELAY`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_API_DELAY).
### WEBLATE_VCS_API_TIMEOUT
#### Versionadded
Added in version 5.15.
Configures [`VCS_API_TIMEOUT`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-VCS_API_TIMEOUT).
### WEBLATE_CORS_ALLOWED_ORIGINS
#### Versionadded
Added in version 4.16.
Allow CORS requests to API from given origins.
**Exemplu:**
```yaml
environment:
WEBLATE_CORS_ALLOWED_ORIGINS: https://example.com,https://weblate.org
```
### WEBLATE_CORS_ALLOW_ALL_ORIGINS
#### Versionadded
Added in version 5.6.1: Allows CORS requests to API from all origins.
### WEBLATE_WEBSITE_ALERTS_ENABLED
#### Versionadded
Added in version 5.17.
Configures [`WEBSITE_ALERTS_ENABLED`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBSITE_ALERTS_ENABLED).
### CLIENT_MAX_BODY_SIZE
#### Versionadded
Added in version 4.16.3.
Configures maximal body size accepted by the built-in web server.
Use a non-negative integer with an optional `k`, `m`, or `g` suffix.
The suffix is case-insensitive, and `0` disables the request body size
limit.
```yaml
environment:
CLIENT_MAX_BODY_SIZE: 200m
```
#### HINT
This variable intentionally lacks `WEBLATE_` prefix as it is shared
with third-party container used in [Certificate SSL automate folosind Let’s Encrypt](#docker-https-portal).
### WEBLATE_TRANSLATION_UPLOAD_MAX_SIZE
Configures [`TRANSLATION_UPLOAD_MAX_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-TRANSLATION_UPLOAD_MAX_SIZE).
The value is in bytes.
### WEBLATE_COMPONENT_ZIP_UPLOAD_MAX_SIZE
Configures [`COMPONENT_ZIP_UPLOAD_MAX_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-COMPONENT_ZIP_UPLOAD_MAX_SIZE).
The value is in bytes.
### WEBLATE_PROJECT_BACKUP_UPLOAD_MAX_SIZE
Configures [`PROJECT_BACKUP_UPLOAD_MAX_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_BACKUP_UPLOAD_MAX_SIZE).
The value is in bytes. Make sure [`CLIENT_MAX_BODY_SIZE`](#envvar-CLIENT_MAX_BODY_SIZE) is also
large enough for uploaded backup files.
### WEBLATE_PROJECT_BACKUP_IMPORT_MAX_MEMBERS
#### Versionadded
Added in version 2026.5.
Configures [`PROJECT_BACKUP_IMPORT_MAX_MEMBERS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_BACKUP_IMPORT_MAX_MEMBERS).
### WEBLATE_PROJECT_BACKUP_IMPORT_MAX_TOTAL_UNCOMPRESSED_SIZE
#### Versionadded
Added in version 2026.5.
Configures [`PROJECT_BACKUP_IMPORT_MAX_TOTAL_UNCOMPRESSED_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_BACKUP_IMPORT_MAX_TOTAL_UNCOMPRESSED_SIZE).
The value is in bytes.
### WEBLATE_PROJECT_BACKUP_IMPORT_MAX_COMPRESSED_ENTRY_SIZE
#### Versionadded
Added in version 2026.5.
Configures [`PROJECT_BACKUP_IMPORT_MAX_COMPRESSED_ENTRY_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_BACKUP_IMPORT_MAX_COMPRESSED_ENTRY_SIZE).
The value is in bytes.
### WEBLATE_PROJECT_BACKUP_IMPORT_MIN_RATIO_SIZE
#### Versionadded
Added in version 2026.5.
Configures [`PROJECT_BACKUP_IMPORT_MIN_RATIO_SIZE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_BACKUP_IMPORT_MIN_RATIO_SIZE).
The value is in bytes.
### WEBLATE_PROJECT_BACKUP_IMPORT_MAX_COMPRESSED_ENTRY_RATIO
#### Versionadded
Added in version 2026.5.
Configures [`PROJECT_BACKUP_IMPORT_MAX_COMPRESSED_ENTRY_RATIO`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PROJECT_BACKUP_IMPORT_MAX_COMPRESSED_ENTRY_RATIO).
### 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 [GitHub solicitări de tracțiune](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-github-pull-requests), but apply
to all [Integrare control versiune](https://docs.weblate.org/ro/latest/vcs.md#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:
```shell
WEBLATE_GITHUB_USERNAME=api-user
WEBLATE_GITHUB_TOKEN=api-token
WEBLATE_GITHUB_HOST=api.github.com
```
Will be used as:
```python
GITHUB_CREDENTIALS = {
"api.github.com": {
"username": "api-user",
"token": "api-token",
}
}
```
Alternatively the Python dictionary can be provided as a string:
```shell
WEBLATE_GITHUB_CREDENTIALS='{ "api.github.com": { "username": "api-user", "token": "api-token", } }'
```
Or the path to a file containing the Python dictionary:
```shell
echo '{ "api.github.com": { "username": "api-user", "token": "api-token", } }' > /path/to/github-credentials
WEBLATE_GITHUB_CREDENTIALS_FILE='/path/to/github-credentials'
```
### WEBLATE_GITHUB_USERNAME
### WEBLATE_GITHUB_TOKEN
### WEBLATE_GITHUB_HOST
### WEBLATE_GITHUB_CREDENTIALS
Configures [GitHub solicitări de tracțiune](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-github-pull-requests) by changing
[`GITHUB_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GITHUB_CREDENTIALS).
#### SEE ALSO
[Configuring code-hosting credentials in Docker](#docker-vcs-config)
### WEBLATE_GITHUB_LEGACY_APP_WEBHOOK_SECRET
#### Versionadded
Added in version 2026.8.
Configures [`GITHUB_LEGACY_APP_WEBHOOK_SECRET`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GITHUB_LEGACY_APP_WEBHOOK_SECRET). The `_FILE`
variant can be used to load the secret from a file.
GitHub Apps registered through the in-app manifest flow are stored in the
database and do not need environment variables. See
[GitHub notifications](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-github-notifications).
### WEBLATE_GITLAB_USERNAME
### WEBLATE_GITLAB_TOKEN
### WEBLATE_GITLAB_HOST
### WEBLATE_GITLAB_CREDENTIALS
Configures [Cereri de fuziune GitLab](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-gitlab-merge-requests) by changing
[`GITLAB_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GITLAB_CREDENTIALS).
#### SEE ALSO
[Configuring code-hosting credentials in Docker](#docker-vcs-config)
### WEBLATE_GITEA_USERNAME
### WEBLATE_GITEA_TOKEN
### WEBLATE_GITEA_HOST
### WEBLATE_GITEA_CREDENTIALS
Configures [Gitea cereri de pull](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-gitea-pull-requests) by changing
[`GITEA_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GITEA_CREDENTIALS).
#### SEE ALSO
[Configuring code-hosting credentials in Docker](#docker-vcs-config)
### WEBLATE_PAGURE_USERNAME
### WEBLATE_PAGURE_TOKEN
### WEBLATE_PAGURE_HOST
### WEBLATE_PAGURE_CREDENTIALS
Configures [Cereri de fuziune Pagure](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-pagure-merge-requests) by changing
[`PAGURE_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PAGURE_CREDENTIALS).
#### SEE ALSO
[Configuring code-hosting credentials in Docker](#docker-vcs-config)
### WEBLATE_BITBUCKETSERVER_USERNAME
### WEBLATE_BITBUCKETSERVER_TOKEN
### WEBLATE_BITBUCKETSERVER_HOST
### WEBLATE_BITBUCKETSERVER_CREDENTIALS
Configures [Bitbucket Data Center pull requests](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-bitbucket-data-center-pull-requests) by
changing [`BITBUCKETSERVER_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-BITBUCKETSERVER_CREDENTIALS).
### WEBLATE_BITBUCKETCLOUD_USERNAME
### WEBLATE_BITBUCKETCLOUD_WORKSPACE
### WEBLATE_BITBUCKETCLOUD_TOKEN
### WEBLATE_BITBUCKETCLOUD_HOST
### WEBLATE_BITBUCKETCLOUD_CREDENTIALS
Configures [Bitbucket Cloud pull requests](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-bitbucket-cloud-pull-requests) by changing
[`BITBUCKETCLOUD_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-BITBUCKETCLOUD_CREDENTIALS).
#### SEE ALSO
[Configuring code-hosting credentials in Docker](#docker-vcs-config)
### WEBLATE_AZURE_DEVOPS_USERNAME
### WEBLATE_AZURE_DEVOPS_ORGANIZATION
### WEBLATE_AZURE_DEVOPS_TOKEN
### WEBLATE_AZURE_DEVOPS_HOST
### WEBLATE_AZURE_DEVOPS_CREDENTIALS
Configures [Azure DevOps pull requests](https://docs.weblate.org/ro/latest/admin/code-hosting.md#code-hosting-azure-devops-pull-requests) by changing
[`AZURE_DEVOPS_CREDENTIALS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-AZURE_DEVOPS_CREDENTIALS).
#### SEE ALSO
[Configuring code-hosting credentials in Docker](#docker-vcs-config)
### Setări de sugestii automate
#### Versionchanged
Schimbat în versiunea 4.13: Serviciile de sugestie automată sunt acum configurate în interfața cu utilizatorul, a se vedea [Sugestii automate](https://docs.weblate.org/ro/latest/admin/machine.md#machine-translation-setup).
Variabilele de mediu existente sunt importate în timpul migrării la Weblate 4.13, dar modificarea lor nu va mai avea niciun efect.
### Setări de autentificare
#### HINT
The e-mail based authentication is turned on unless disabled by [`WEBLATE_NO_EMAIL_AUTH`](#envvar-WEBLATE_NO_EMAIL_AUTH).
#### LDAP
### WEBLATE_AUTH_LDAP_SERVER_URI
### WEBLATE_AUTH_LDAP_USER_DN_TEMPLATE
### WEBLATE_AUTH_LDAP_USER_ATTR_MAP
### WEBLATE_AUTH_LDAP_BIND_DN
### WEBLATE_AUTH_LDAP_BIND_PASSWORD
### WEBLATE_AUTH_LDAP_CONNECTION_OPTION_REFERRALS
### WEBLATE_AUTH_LDAP_USER_SEARCH
### WEBLATE_AUTH_LDAP_USER_SEARCH_FILTER
### WEBLATE_AUTH_LDAP_USER_SEARCH_UNION
### WEBLATE_AUTH_LDAP_USER_SEARCH_UNION_DELIMITER
Configurarea autentificării LDAP.
**Exemplu pentru legarea directă:**
```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
```
**Exemplu pentru căutare și legare:**
```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
```
**Exemplu pentru căutarea și legarea uniunii:**
```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
```
**Exemplu cu căutare și legare în Active Directory:**
```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)
```
#### SEE ALSO
* [Passing secrets](#docker-secrets)
* [Autentificare LDAP](https://docs.weblate.org/ro/latest/admin/auth.md#ldap-auth)
#### GitHub
### WEBLATE_SOCIAL_AUTH_GITHUB_KEY
### WEBLATE_SOCIAL_AUTH_GITHUB_SECRET
### WEBLATE_SOCIAL_AUTH_GITHUB_ORG_KEY
### WEBLATE_SOCIAL_AUTH_GITHUB_ORG_SECRET
### WEBLATE_SOCIAL_AUTH_GITHUB_ORG_NAME
### WEBLATE_SOCIAL_AUTH_GITHUB_TEAM_KEY
### WEBLATE_SOCIAL_AUTH_GITHUB_TEAM_SECRET
### WEBLATE_SOCIAL_AUTH_GITHUB_TEAM_ID
Activează [Autentificarea GitHub](https://docs.weblate.org/ro/latest/admin/auth.md#github-auth).
#### GitHub Enterprise Edition
### WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_KEY
### WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_SECRET
### WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_URL
### WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_API_URL
### WEBLATE_SOCIAL_AUTH_GITHUB_ENTERPRISE_SCOPE
Enables [GitHub EE authentication](https://docs.weblate.org/ro/latest/admin/auth.md#github-ee-auth).
#### Bitbucket
### WEBLATE_SOCIAL_AUTH_BITBUCKET_OAUTH2_KEY
### WEBLATE_SOCIAL_AUTH_BITBUCKET_OAUTH2_SECRET
Activează [Autentificarea Bitbucket](https://docs.weblate.org/ro/latest/admin/auth.md#bitbucket-auth).
#### Facebook
### WEBLATE_SOCIAL_AUTH_FACEBOOK_KEY
### WEBLATE_SOCIAL_AUTH_FACEBOOK_SECRET
Activează [Facebook OAuth 2](https://docs.weblate.org/ro/latest/admin/auth.md#facebook-auth).
#### Google
### WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_KEY
### WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_SECRET
### WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_WHITELISTED_DOMAINS
### WEBLATE_SOCIAL_AUTH_GOOGLE_OAUTH2_WHITELISTED_EMAILS
Activează [Google OAuth 2](https://docs.weblate.org/ro/latest/admin/auth.md#google-auth).
#### GitLab
### WEBLATE_SOCIAL_AUTH_GITLAB_KEY
### WEBLATE_SOCIAL_AUTH_GITLAB_SECRET
### WEBLATE_SOCIAL_AUTH_GITLAB_API_URL
Activează [GitLab OAuth 2](https://docs.weblate.org/ro/latest/admin/auth.md#gitlab-auth).
#### Gitea
### WEBLATE_SOCIAL_AUTH_GITEA_API_URL
### WEBLATE_SOCIAL_AUTH_GITEA_KEY
### WEBLATE_SOCIAL_AUTH_GITEA_SECRET
Enables Gitea authentication.
#### Microsoft Entra ID
### WEBLATE_SOCIAL_AUTH_AZUREAD_OAUTH2_KEY
### WEBLATE_SOCIAL_AUTH_AZUREAD_OAUTH2_SECRET
Enables Microsoft Entra ID authentication, see [Microsoft Entra ID](https://docs.weblate.org/ro/latest/admin/auth.md#entra-auth).
#### Microsoft Entra ID with Tenant support
### WEBLATE_SOCIAL_AUTH_AZUREAD_TENANT_OAUTH2_KEY
### WEBLATE_SOCIAL_AUTH_AZUREAD_TENANT_OAUTH2_SECRET
### WEBLATE_SOCIAL_AUTH_AZUREAD_TENANT_OAUTH2_TENANT_ID
Enables Microsoft Entra ID authentication with Tenant support, see
[Microsoft Entra ID](https://docs.weblate.org/ro/latest/admin/auth.md#entra-auth).
#### Keycloak
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_KEY
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_SECRET
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_PUBLIC_KEY
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_ALGORITHM
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_AUTHORIZATION_URL
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_ACCESS_TOKEN_URL
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_TITLE
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_IMAGE
Enables Keycloak authentication, see [Keycloak - Open Source Red Hat SSO](https://python-social-auth.readthedocs.io/en/latest/backends/keycloak.html).
### WEBLATE_SOCIAL_AUTH_KEYCLOAK_ID_KEY
#### Versionadded
Added in version 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 [`WEBLATE_CSP_FORM_SRC`](#envvar-WEBLATE_CSP_FORM_SRC) for the third-party IDP domain.
```yaml
environment:
WEBLATE_CSP_FORM_SRC: login.microsoftonline.com
```
#### Furnizori Linux
Puteți activa autentificarea utilizând serviciile de autentificare ale furnizorilor Linux prin setarea următoarelor variabile la orice valoare.
### WEBLATE_SOCIAL_AUTH_FEDORA
### WEBLATE_SOCIAL_AUTH_OPENSUSE
### WEBLATE_SOCIAL_AUTH_OPENINFRA
### WEBLATE_SOCIAL_AUTH_UBUNTU
#### Slack
### WEBLATE_SOCIAL_AUTH_SLACK_KEY
### WEBLATE_SOCIAL_AUTH_SLACK_SECRET
Activează autentificarea Slack, vezi [Slack](https://docs.weblate.org/ro/latest/admin/auth.md#slack-auth).
#### Conectare OpenID
#### Versionadded
Added in version 4.13-1.
### WEBLATE_SOCIAL_AUTH_OIDC_OIDC_ENDPOINT
### WEBLATE_SOCIAL_AUTH_OIDC_KEY
### WEBLATE_SOCIAL_AUTH_OIDC_SECRET
### WEBLATE_SOCIAL_AUTH_OIDC_USERNAME_KEY
### WEBLATE_SOCIAL_AUTH_OIDC_TITLE
### WEBLATE_SOCIAL_AUTH_OIDC_IMAGE
Configures generic OpenID Connect integration.
#### SEE ALSO
[OIDC (OpenID Connect)](https://python-social-auth.readthedocs.io/en/latest/backends/oidc.html)
#### Fedora OpenID Connect
#### Versionadded
Added in version 5.15.
### WEBLATE_SOCIAL_AUTH_FEDORA_OIDC_KEY
### WEBLATE_SOCIAL_AUTH_FEDORA_OIDC_SECRET
Configures Fedora OpenID Connect integration.
#### SEE ALSO
[Fedora](https://python-social-auth.readthedocs.io/en/latest/backends/fedora.html)
#### SAML
Cheile SAML autofirmate sunt generate automat la prima pornire a containerului. În cazul în care doriți să utilizați chei proprii, plasați certificatul și cheia privată în `/app/data/ssl/saml.crt` și `/app/data/ssl/saml.key`.
### WEBLATE_SAML_IDP_ENTITY_ID
### WEBLATE_SAML_IDP_URL
### WEBLATE_SAML_IDP_X509CERT
### WEBLATE_SAML_IDP_IMAGE
### WEBLATE_SAML_IDP_TITLE
Setările furnizorului de identitate SAML, consultați [Autentificare SAML](https://docs.weblate.org/ro/latest/admin/auth.md#saml-auth).
### WEBLATE_SAML_SECURITY_CONFIG
#### Versionadded
Added in version 2026.6.
SAML security configuration as a JSON object, passed to
`SOCIAL_AUTH_SAML_SECURITY_CONFIG`. For example, to disable the
`requestedAuthnContext` (needed for some identity providers such as
Microsoft Entra ID with multi-factor authentication):
```yaml
environment:
WEBLATE_SAML_SECURITY_CONFIG: '{"requestedAuthnContext": false}'
```
#### SEE ALSO
[python3-saml security settings](https://github.com/SAML-Toolkits/python3-saml#settings)
### WEBLATE_SAML_ID_ATTR_FULL_NAME
### WEBLATE_SAML_ID_ATTR_FIRST_NAME
### WEBLATE_SAML_ID_ATTR_LAST_NAME
### WEBLATE_SAML_ID_ATTR_USERNAME
### WEBLATE_SAML_ID_ATTR_EMAIL
### WEBLATE_SAML_ID_ATTR_USER_PERMANENT_ID
#### Versionadded
Added in version 4.18.
SAML attributes mapping.
#### Alte setări de autentificare
### WEBLATE_NO_EMAIL_AUTH
Dezactivează autentificarea e-mailurilor atunci când este setat la orice valoare. A se vedea [Dezactivarea autentificării prin parolă](https://docs.weblate.org/ro/latest/admin/auth.md#disable-email-auth).
### 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.
#### SEE ALSO
* [Autentificarea prin parolă](https://docs.weblate.org/ro/latest/admin/auth.md#password-authentication)
* [`PASSWORD_MINIMAL_STRENGTH`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PASSWORD_MINIMAL_STRENGTH)
### Configurarea bazei de date PostgreSQL
Baza de date este creată de `docker-compose.yml`, astfel încât aceste setări afectează atât containerele Weblate, cât și PostgreSQL.
#### SEE ALSO
[Configurarea bazei de date pentru Weblate](https://docs.weblate.org/ro/latest/admin/install.md#database-setup)
### POSTGRES_PASSWORD
Parola PostgreSQL.
#### SEE ALSO
[Passing secrets](#docker-secrets)
### POSTGRES_USER
Nume de utilizator PostgreSQL.
### POSTGRES_DB
Numele bazei de date PostgreSQL.
### POSTGRES_HOST
Numele de gazdă sau adresa IP a serverului PostgreSQL. Valoarea implicită este `database`.
### POSTGRES_PORT
Portul serverului PostgreSQL. Valoarea implicită este niciunul (utilizează valoarea implicită).
### 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).
### POSTGRES_ALTER_ROLE
Configures name of the PostgreSQL role to alter during the database migration, see [Configurarea Weblate pentru a utiliza PostgreSQL](https://docs.weblate.org/ro/latest/admin/install.md#config-postgresql).
Defaults to [`POSTGRES_USER`](#envvar-POSTGRES_USER).
### POSTGRES_CONN_MAX_AGE
#### Versionadded
Added in version 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
Schimbat în versiunea 5.1: The default behavior is to have unlimited persistent database connections.
Activarea persistenței conexiunii va determina, de obicei, mai multe conexiuni deschise la baza de date. Vă rugăm să ajustați configurația bazei de date înainte de activare.
Exemplu de configurare:
```yaml
environment:
POSTGRES_CONN_MAX_AGE: 3600
```
#### SEE ALSO
* [`CONN_MAX_AGE`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-CONN_MAX_AGE)
* [Persistent connections](https://docs.djangoproject.com/en/stable/ref/databases/#persistent-database-connections)
### POSTGRES_DISABLE_SERVER_SIDE_CURSORS
#### Versionadded
Added in version 4.9.1.
Dezactivați cursorii de pe server în baza de date. Acest lucru este necesar în unele configurații **pgbouncer**.
Exemplu de configurare:
```yaml
environment:
POSTGRES_DISABLE_SERVER_SIDE_CURSORS: 1
```
#### SEE ALSO
* [`DISABLE_SERVER_SIDE_CURSORS`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-DATABASE-DISABLE_SERVER_SIDE_CURSORS)
* [Transaction pooling and server-side cursors](https://docs.djangoproject.com/en/stable/ref/databases/#transaction-pooling-server-side-cursors)
### WEBLATE_DATABASES
#### Versionadded
Added in version 5.1.
Set to false to disable environment based configuration of the database
connection. Use [Overriding settings from the data volume](#docker-settings-override) to configure the database
connection manually.
### Setări de salvare a bazei de date
#### SEE ALSO
[Date descărcate pentru copii de rezervă](https://docs.weblate.org/ro/latest/admin/backup.md#backup-dumps)
### WEBLATE_DATABASE_BACKUP
Configurează descărcarea zilnică a bazei de date folosind [`DATABASE_BACKUP`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DATABASE_BACKUP). Valoarea implicită este `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.
#### SEE ALSO
[Configure cache](https://docs.weblate.org/ro/latest/admin/install.md#production-cache)
### REDIS_HOST
The datastore server hostname or IP address. Defaults to `cache`.
### REDIS_PORT
The datastore server port. Defaults to `6379`.
### REDIS_DB
The datastore database number, defaults to `1`.
### REDIS_USER
#### Versionadded
Added in version 5.13: The datastore database user, not used by default.
### REDIS_PASSWORD
The datastore server password, not used by default.
#### SEE ALSO
[Passing secrets](#docker-secrets)
### REDIS_TLS
Enables using SSL for the datastore connection.
### REDIS_VERIFY_SSL
Can be used to disable SSL certificate verification for the datastore connection.
### Configurarea serverului de e-mail
Pentru ca poșta electronică de ieșire să funcționeze, trebuie să furnizați un server de poștă electronică.
Exemplu de configurare TLS:
```yaml
environment:
WEBLATE_EMAIL_HOST: smtp.example.com
WEBLATE_EMAIL_HOST_USER: user
WEBLATE_EMAIL_HOST_PASSWORD: pass
```
Exemplu de configurare SSL:
```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
```
#### SEE ALSO
[Configurarea e-mailului de ieșire](https://docs.weblate.org/ro/latest/admin/install.md#out-mail)
### WEBLATE_EMAIL_HOST
Numele de gazdă sau adresa IP a serverului de poștă electronică.
#### SEE ALSO
* [`WEBLATE_EMAIL_PORT`](#envvar-WEBLATE_EMAIL_PORT)
* [`WEBLATE_EMAIL_USE_SSL`](#envvar-WEBLATE_EMAIL_USE_SSL)
* [`WEBLATE_EMAIL_USE_TLS`](#envvar-WEBLATE_EMAIL_USE_TLS)
* [`EMAIL_HOST`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_HOST)
### WEBLATE_EMAIL_PORT
Portul serverului de poștă electronică, valoarea implicită este 25.
#### SEE ALSO
[`EMAIL_PORT`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_PORT)
### WEBLATE_EMAIL_HOST_USER
Utilizator de autentificare prin e-mail.
#### SEE ALSO
[`EMAIL_HOST_USER`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_HOST_USER)
### WEBLATE_EMAIL_HOST_PASSWORD
Parola de autentificare a e-mailului.
#### SEE ALSO
* [Passing secrets](#docker-secrets)
* [`EMAIL_HOST_PASSWORD`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_HOST_PASSWORD)
### WEBLATE_EMAIL_USE_SSL
Dacă se utilizează o conexiune TLS (securizată) implicită atunci când se vorbește cu serverul SMTP. În cea mai mare parte a documentației despre e-mail, acest tip de conexiune TLS este denumit SSL. În general, este utilizat pe portul 465. Dacă întâmpinați probleme, consultați setarea TLS explicită [`WEBLATE_EMAIL_USE_TLS`](#envvar-WEBLATE_EMAIL_USE_TLS).
#### Versionchanged
Schimbat în versiunea 4.11: Suportul SSL/TLS este activat automat pe baza parametrului [`WEBLATE_EMAIL_PORT`](#envvar-WEBLATE_EMAIL_PORT).
#### SEE ALSO
* [`WEBLATE_EMAIL_PORT`](#envvar-WEBLATE_EMAIL_PORT)
* [`WEBLATE_EMAIL_USE_TLS`](#envvar-WEBLATE_EMAIL_USE_TLS)
* [`EMAIL_USE_SSL`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_USE_SSL)
### WEBLATE_EMAIL_USE_TLS
Dacă se utilizează o conexiune TLS (securizată) atunci când se vorbește cu serverul SMTP. Aceasta este utilizată pentru conexiunile TLS explicite, în general pe portul 587 sau 25. Dacă vă confruntați cu conexiuni care se blochează, consultați setarea TLS implicită [`WEBLATE_EMAIL_USE_SSL`](#envvar-WEBLATE_EMAIL_USE_SSL).
#### Versionchanged
Schimbat în versiunea 4.11: Suportul SSL/TLS este activat automat pe baza parametrului [`WEBLATE_EMAIL_PORT`](#envvar-WEBLATE_EMAIL_PORT).
#### SEE ALSO
* [`WEBLATE_EMAIL_PORT`](#envvar-WEBLATE_EMAIL_PORT)
* [`WEBLATE_EMAIL_USE_SSL`](#envvar-WEBLATE_EMAIL_USE_SSL)
* [`EMAIL_USE_TLS`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_USE_TLS)
### WEBLATE_EMAIL_BACKEND
Configurează back-end-ul Django care va fi folosit pentru trimiterea de e-mailuri.
Set to `django_ses.SESBackend` to use AWS SES.
#### SEE ALSO
* [Configurați trimiterea de e-mailuri](https://docs.weblate.org/ro/latest/admin/install.md#production-email)
* [`EMAIL_BACKEND`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-EMAIL_BACKEND)
### WEBLATE_AWS_SES_REGION_NAME
AWS region for SES (e.g. `us-east-1`). Sets
`AWS_SES_REGION_NAME` and derives
[`WEBLATE_AWS_SES_REGION_ENDPOINT`](#envvar-WEBLATE_AWS_SES_REGION_ENDPOINT) automatically unless
that variable is set explicitly. If not set, the region must be
available through the standard boto3 credential chain (e.g.
`AWS_DEFAULT_REGION` or an AWS profile).
### WEBLATE_AWS_SES_REGION_ENDPOINT
SES endpoint hostname. When set, it is passed to django-ses
directly regardless of [`WEBLATE_AWS_SES_REGION_NAME`](#envvar-WEBLATE_AWS_SES_REGION_NAME).
When not set but [`WEBLATE_AWS_SES_REGION_NAME`](#envvar-WEBLATE_AWS_SES_REGION_NAME) is
provided, defaults to `email..amazonaws.com`. Override
when using a VPC or custom endpoint.
### WEBLATE_USE_SES_V2
Set to `true` to use the SES v2 API (`SendEmail`) instead of
the legacy `SendRawEmail` call. Boolean setting (use `"true"`
or `"false"`).
### WEBLATE_AUTO_UPDATE
Configurează dacă și cum Weblate trebuie să actualizeze depozitele.
The default, `"false"`, fetches remote changes daily without merging them
into the working copy; it does not disable daily updates. Set to `"true"`
to also merge remote changes into the working copy.
#### SEE ALSO
[`AUTO_UPDATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-AUTO_UPDATE) for details on how updates are scheduled throughout
the day.
#### NOTE
Aceasta este o setare booleană (utilizați `"true"` sau `"false"`).
### Integrare site
### WEBLATE_GET_HELP_URL
Configurează [`GET_HELP_URL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GET_HELP_URL).
### WEBLATE_STATUS_URL
Configurează [`STATUS_URL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-STATUS_URL).
### WEBLATE_LEGAL_URL
Configurează [`LEGAL_URL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LEGAL_URL).
### WEBLATE_PRIVACY_URL
Configurează [`PRIVACY_URL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PRIVACY_URL).
### WEBLATE_PASSWORD_RESET_URL
Configures [`PASSWORD_RESET_URL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-PASSWORD_RESET_URL).
### Collecting error reports and monitoring performance
Se recomandă colectarea sistematică a erorilor de la instalare, a se vedea [Collecting error reports and monitoring performance](https://docs.weblate.org/ro/latest/admin/install.md#collecting-errors).
Pentru a activa suportul pentru Rollbar, setați următoarele:
### ROLLBAR_KEY
Tokenul tău de acces la serverul Rollbar post.
### ROLLBAR_ENVIRONMENT
Mediul dumneavoastră Rollbar, implicit `production`.
Pentru a activa suportul pentru Sentry, setați următoarele:
### SENTRY_DSN
Your Sentry DSN, see [`SENTRY_DSN`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SENTRY_DSN).
### SENTRY_ENVIRONMENT
Your Sentry Environment (optional), defaults to [`WEBLATE_SITE_DOMAIN`](#envvar-WEBLATE_SITE_DOMAIN).
### SENTRY_MONITOR_BEAT_TASKS
Whether to monitor Celery Beat tasks with Sentry, defaults to `True`.
### SENTRY_TRACES_SAMPLE_RATE
Configures [`SENTRY_TRACES_SAMPLE_RATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SENTRY_TRACES_SAMPLE_RATE).
**Exemplu:**
```yaml
environment:
SENTRY_TRACES_SAMPLE_RATE: 0.5
```
### SENTRY_PROFILES_SAMPLE_RATE
Configures [`SENTRY_PROFILES_SAMPLE_RATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SENTRY_PROFILES_SAMPLE_RATE).
**Exemplu:**
```yaml
environment:
SENTRY_PROFILES_SAMPLE_RATE: 0.5
```
### SENTRY_SEND_PII
Configures [`SENTRY_SEND_PII`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-SENTRY_SEND_PII).
To enable support for Google Cloud Error Reporting, set following:
### GOOGLE_CLOUD_ERROR_REPORTING_ENABLED
Enables [`GOOGLE_CLOUD_ERROR_REPORTING`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-GOOGLE_CLOUD_ERROR_REPORTING), defaults to `False`.
### GOOGLE_CLOUD_ERROR_REPORTING_PROJECT
Google Cloud project to report errors to. If omitted, the Google client uses
application default credentials to detect the project.
### GOOGLE_CLOUD_ERROR_REPORTING_SERVICE
Service name to use in Google Cloud Error Reporting, defaults to `weblate`.
To enable support for OpenTelemetry tracing, set following:
### OPENTELEMETRY_ENABLED
Enables [`OPENTELEMETRY_ENABLED`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-OPENTELEMETRY_ENABLED), defaults to `False`.
### OPENTELEMETRY_EXPORTER_OTLP_ENDPOINT
Configures [`OPENTELEMETRY_EXPORTER_OTLP_ENDPOINT`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-OPENTELEMETRY_EXPORTER_OTLP_ENDPOINT).
**Exemplu:**
```yaml
environment:
OPENTELEMETRY_ENABLED: true
OPENTELEMETRY_EXPORTER_OTLP_ENDPOINT: https://collector.example.com/v1/traces
OPENTELEMETRY_TRACES_SAMPLE_RATE: 0.1
```
### OPENTELEMETRY_EXPORTER_OTLP_HEADERS
Configures [`OPENTELEMETRY_EXPORTER_OTLP_HEADERS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-OPENTELEMETRY_EXPORTER_OTLP_HEADERS) as a comma-separated
`name:value` mapping.
### OPENTELEMETRY_EXTRA_RESOURCE_ATTRIBUTES
Configures [`OPENTELEMETRY_EXTRA_RESOURCE_ATTRIBUTES`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-OPENTELEMETRY_EXTRA_RESOURCE_ATTRIBUTES) as a
comma-separated `name:value` mapping.
### OPENTELEMETRY_SERVICE_NAME
Configures [`OPENTELEMETRY_SERVICE_NAME`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-OPENTELEMETRY_SERVICE_NAME).
### OPENTELEMETRY_TRACES_SAMPLE_RATE
Configures [`OPENTELEMETRY_TRACES_SAMPLE_RATE`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-OPENTELEMETRY_TRACES_SAMPLE_RATE).
### Localizare CDN
### WEBLATE_LOCALIZE_CDN_URL
### WEBLATE_LOCALIZE_CDN_PATH
#### Versionadded
Added in version 4.2.1.
Configuration for CDN add-ons, including [CDN de localizare JavaScript](https://docs.weblate.org/ro/latest/admin/addons.md#addon-weblate-cdn-cdnjs)
and [Translation files CDN](https://docs.weblate.org/ro/latest/admin/addons.md#addon-weblate-cdn-files).
[`WEBLATE_LOCALIZE_CDN_PATH`](#envvar-WEBLATE_LOCALIZE_CDN_PATH) este calea din container. Acesta trebuie să fie stocat pe volumul persistent și nu în memoria tranzitorie.
Una dintre posibilități este stocarea acestora în directorul de date Weblate:
```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 stores the files in configured location. See
[Localizare CDN](https://docs.weblate.org/ro/latest/admin/optionals.md#cdn-server-security) for secure serving guidance.
#### SEE ALSO
* [Traducerea HTML și JavaScript folosind Weblate CDN](https://docs.weblate.org/ro/latest/devel/html.md#weblate-cdn)
* [`LOCALIZE_CDN_URL`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LOCALIZE_CDN_URL)
* [`LOCALIZE_CDN_PATH`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-LOCALIZE_CDN_PATH)
### Changing enabled apps, checks, formats, add-ons, machinery, or autofixes
The built-in configuration of enabled checks, file formats, add-ons,
machinery, or autofixes can be adjusted by the following variables:
### WEBLATE_ADD_APPS
### WEBLATE_REMOVE_APPS
### WEBLATE_ADD_CHECK
### WEBLATE_REMOVE_CHECK
### WEBLATE_ADD_AUTOFIX
### WEBLATE_REMOVE_AUTOFIX
### WEBLATE_ADD_FORMATS
### WEBLATE_REMOVE_FORMATS
### WEBLATE_ADD_ADDONS
### WEBLATE_REMOVE_ADDONS
### WEBLATE_ADD_MACHINERY
#### Versionadded
Added in version 5.6.1.
### WEBLATE_REMOVE_MACHINERY
#### Versionadded
Added in version 5.6.1.
**Exemplu:**
```yaml
environment:
WEBLATE_REMOVE_AUTOFIX: weblate.trans.autofixes.whitespace.SameBookendingWhitespace
WEBLATE_REMOVE_FORMATS: weblate.formats.ttkit.PoFormat
WEBLATE_ADD_ADDONS: customize.addons.MyAddon,customize.addons.OtherAddon
```
#### SEE ALSO
* [`CHECK_LIST`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CHECK_LIST)
* [`AUTOFIX_LIST`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-AUTOFIX_LIST)
* [`WEBLATE_FORMATS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBLATE_FORMATS)
* [`WEBLATE_ADDONS`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBLATE_ADDONS)
* [`INSTALLED_APPS`](https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-INSTALLED_APPS)
* [`WEBLATE_MACHINERY`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-WEBLATE_MACHINERY)
### Setări container
### WEBLATE_WORKERS
#### Versionadded
Added in version 4.6.1.
Numărul de bază al proceselor de lucru care rulează în container. Dacă nu este setat, acesta este determinat automat la pornirea containerului pe baza numărului de nuclee CPU disponibile.
It is used to determine [`CELERY_MAIN_OPTIONS`](#envvar-CELERY_MAIN_OPTIONS),
[`CELERY_COMBINED_OPTIONS`](#envvar-CELERY_COMBINED_OPTIONS),
[`CELERY_NOTIFY_OPTIONS`](#envvar-CELERY_NOTIFY_OPTIONS), [`CELERY_MEMORY_OPTIONS`](#envvar-CELERY_MEMORY_OPTIONS),
[`CELERY_TRANSLATE_OPTIONS`](#envvar-CELERY_TRANSLATE_OPTIONS), [`CELERY_BACKUP_OPTIONS`](#envvar-CELERY_BACKUP_OPTIONS),
[`WEB_WORKERS`](#envvar-WEB_WORKERS), and [`WEB_BLOCKING_THREADS`](#envvar-WEB_BLOCKING_THREADS). You can use these
settings to fine-tune.
### CELERY_WORKER_MODE
#### Versionadded
Added in version 2026.9.1.
Selects how Celery workers are run in the container. Supported modes are:
`combined`
: Runs one prefork worker for all queues. This is the default and reduces
memory usage by sharing the application startup memory. Its concurrency
defaults to three times [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS), and its prefetch
multiplier defaults to one.
`split`
: Runs a separate prefork worker for each queue. This matches the behavior
of container versions before 2026.9.1 and allows each queue to be tuned
independently.
`single`
: Runs all queues in one process using the solo pool. This minimizes memory
usage, but noticeably reduces task throughput.
Explicit [`WEBLATE_SERVICE`](#envvar-WEBLATE_SERVICE) selection takes precedence over this
setting in horizontally scaled deployments.
### CELERY_COMBINED_OPTIONS
#### Versionadded
Added in version 2026.9.1.
Configures the worker used by `CELERY_WORKER_MODE=combined`. By default,
its concurrency is three times [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS). The worker uses a
prefetch multiplier of one unless overridden here.
```yaml
environment:
CELERY_COMBINED_OPTIONS: --concurrency 12 --prefetch-multiplier 1
```
#### SEE ALSO
* [Celery worker options](https://docs.celeryq.dev/en/stable/reference/celery.bin.worker.html)
* [Sarcini de fundal folosind Celery](https://docs.weblate.org/ro/latest/admin/install.md#celery)
### CELERY_MAIN_OPTIONS
### CELERY_NOTIFY_OPTIONS
### CELERY_MEMORY_OPTIONS
### CELERY_TRANSLATE_OPTIONS
### CELERY_BACKUP_OPTIONS
These variables allow you to adjust Celery worker options in
`CELERY_WORKER_MODE=split`. It can be useful to adjust concurrency
(`--concurrency 16`), prefetching
(`--prefetch-multiplier 4`), or use different pool implementation
(`--pool=gevent`). Command-line options take precedence over corresponding
Celery settings, allowing each worker category to use a different prefetch
multiplier. When any of these variables is set in `combined` or
`single` mode, the container logs a startup warning that it is ignored.
În mod implicit, numărul de lucrători simultani se bazează pe [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS).
**Exemplu:**
```yaml
environment:
CELERY_MAIN_OPTIONS: --concurrency 16 --prefetch-multiplier 1
```
#### SEE ALSO
* [Celery worker options](https://docs.celeryq.dev/en/stable/reference/celery.bin.worker.html)
* [Sarcini de fundal folosind Celery](https://docs.weblate.org/ro/latest/admin/install.md#celery)
### CELERY_BEAT_OPTIONS
Configures the Celery beat scheduler in all worker modes.
### CELERY_SINGLE_OPTIONS
Configures the worker used by `CELERY_WORKER_MODE=single`.
#### SEE ALSO
* [Celery worker options](https://docs.celeryq.dev/en/stable/reference/celery.bin.worker.html)
* [Single-process Celery setup](https://docs.weblate.org/ro/latest/admin/install.md#minimal-celery)
### CELERY_SINGLE_PROCESS
#### Versionadded
Added in version 5.7.1.
#### Deprecated
Învechit începând cu versiunea 2026.9.1.
Compatibility alias for `CELERY_WORKER_MODE=single`. When set to `1`
without [`CELERY_WORKER_MODE`](#envvar-CELERY_WORKER_MODE), the container starts in `single`
mode and logs a warning asking you to update the setting. If both variables
are set, [`CELERY_WORKER_MODE`](#envvar-CELERY_WORKER_MODE) takes precedence.
#### SEE ALSO
[Single-process Celery setup](https://docs.weblate.org/ro/latest/admin/install.md#minimal-celery)
### WEBLATE_ASGI
#### Versionadded
Added in version 2026.8.
Set to `1` to run the web application using ASGI instead of WSGI. This is
an opt-in setting intended for testing the transition to ASGI. WSGI remains
the default for now, but a future release will run ASGI only and remove this
setting.
```yaml
environment:
WEBLATE_ASGI: 1
```
#### SEE ALSO
[Sample configuration to start Granian with ASGI](https://docs.weblate.org/ro/latest/admin/install.md#running-granian-asgi)
### WEB_WORKERS
> Configure how many web application workers should be executed.
> It defaults to half of [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS), but is always at least 2.
> **Exemplu:**
> ```yaml
> environment:
> WEB_WORKERS: 4
> ```
#### Versionchanged
Schimbat în versiunea 5.13: [`WEB_WORKERS`](#envvar-WEB_WORKERS) configures how many worker processes will be used by **granian**.
### WEB_BLOCKING_THREADS
Configure how many blocking WSGI threads each **granian** worker can
use. It defaults to twice [`WEBLATE_WORKERS`](#envvar-WEBLATE_WORKERS) and is ignored when
[`WEBLATE_ASGI`](#envvar-WEBLATE_ASGI) is enabled.
The maximum number of simultaneous WSGI requests is approximately
[`WEB_WORKERS`](#envvar-WEB_WORKERS) multiplied by [`WEB_BLOCKING_THREADS`](#envvar-WEB_BLOCKING_THREADS). Each
thread can hold its own database connection, so keep the resulting total
within the database connection limit.
**Exemplu:**
```yaml
environment:
WEB_WORKERS: 2
WEB_BLOCKING_THREADS: 8
```
### WEBLATE_SERVICE
Definește ce servicii ar trebui să fie executate în interiorul containerului. Utilizați acest lucru pentru [Scalare pe orizontală](#docker-scaling).
Sunt definite următoarele servicii:
`celery-beat`
: Celery task scheduler, doar o singură instanță ar trebui să ruleze. Acest container este, de asemenea, responsabil pentru migrarea structurii bazei de date și trebuie să fie pornit înaintea celorlalte.
`celery-backup`
: Celery worker pentru copii de rezervă, o singură instanță trebuie să ruleze.
`celery-combined`
: Combined Celery worker for all task queues.
`celery-celery`
: Lucrător generic Celery.
`celery-memory`
: Memoria de traducere Celery worker.
`celery-notify`
: Notificări Celery worker.
`celery-single`
: Single-process Celery worker for all task queues.
`celery-translate`
: Traducere automată Celery worker.
`web`
: Serverul web.
#### SEE ALSO
[Background tasks internals](https://docs.weblate.org/ro/latest/contributing/internals.md#background-tasks-internals)
### WEBLATE_ANUBIS_URL
#### Versionadded
Added in version 5.11.4.
URL of [Anubis](https://anubis.techaro.lol/) 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](https://anubis.techaro.lol/docs/admin/configuration/subrequest-auth) to
make it work.
Use an `http://` or `https://` URL with a valid hostname or IPv4 address.
The URL can include a port and a simple slash-separated path using ASCII
letters, digits, `_`, and `-`. Credentials, queries, fragments, and IPv6
addresses are not supported.
#### SEE ALSO
* [Anubis Docker container integration](#docker-anubis)
* [Anubis](https://anubis.techaro.lol/)
## Volumele containerelor Docker
There are two volumes (`data` and `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
`/var/lib/postgresql` volume and Valkey in the `/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 `data` volume is mounted as `/app/data` and is used to store
Weblate persistent data such as cloned repositories or to customize Weblate
installation. [`DATA_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DATA_DIR) describes in more detail what is stored here.
The `data` volume is also place to store Weblate customization such as
[Overriding settings from the data volume](#docker-settings-override), [Înlocuirea logo-ului și a altor fișiere statice](#docker-static-override) or
[Customizing code](#docker-python-override).
The placement of the Docker volume on host system depends on your Docker
configuration, but usually it is stored in
`/var/lib/docker/volumes/weblate-docker_weblate-data/_data/` (the path
consist of name of your docker-compose directory, container, and volume names).
The `cache` volume is mounted as `/app/cache` and is used to store static
files and [`CACHE_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CACHE_DIR). Its content is recreated on container startup
and the volume can be mounted using ephemeral filesystem such as tmpfs, but
the mount has to allow execution because Weblate stores generated helper files
there.
When mounting `/app/cache` explicitly as `tmpfs` in Docker Compose,
enable execution:
```yaml
tmpfs:
- /app/cache:exec
```
When also setting ownership options, keep the `exec` option:
```yaml
tmpfs:
- /app/cache:exec,uid=1000,gid=1000
```
La crearea manuală a volumelor, directoarele trebuie să fie deținute de UID 1000, deoarece acesta este utilizatorul utilizat în container.
Weblate container can also be executed with a read-only root file system. In
this case, two additional `tmpfs` volumes should be mounted: `/tmp` and
`/run`.
#### SEE ALSO
* [Docker volumes documentation](https://docs.docker.com/engine/storage/volumes/)
* [`DATA_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-DATA_DIR)
* [`CACHE_DIR`](https://docs.weblate.org/ro/latest/admin/config.md#std-setting-CACHE_DIR)
### Read-only root filesystem
#### Versionadded
Added in version 4.18.
When running the container with a read-only root filesystem, two additional
tmpfs volumes are required - `/tmp` and `/run`.
## Configuration beyond environment variables
[Docker environment variables](#docker-environment) are intended to expose
most [configuration settings](https://docs.weblate.org/ro/latest/admin/config.md#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 [ask for it to be exposed in a
future version of Weblate](https://docs.weblate.org/ro/latest/contributing/issues.md#report-issue).
If you need to modify a setting that is not exposed as a Docker environment
variable, you can still do so, either [from the data volume](#docker-settings-override) or [extending the Docker image](#docker-custom-settings).
#### SEE ALSO
[Personalizarea Weblate](https://docs.weblate.org/ro/latest/admin/customize.md)
### Overriding settings from the data volume
You can create a file at `/app/data/settings-override.py`, i.e. at the
root of the [data volume](#docker-volume), to extend or override settings
defined through environment variables.
### Overriding settings by extending the Docker image
To override settings at the Docker image level instead of from the data volume:
1. [Create a custom Python package](https://docs.weblate.org/ro/latest/admin/customize.md#custom-module).
2. Add a module to your package that imports all settings from
`weblate.settings_docker`.
For example, within the example package structure defined at
[Crearea unui modul Python](https://docs.weblate.org/ro/latest/admin/customize.md#custom-module), you could create a file at
`weblate_customization/weblate_customization/settings.py` with the
following initial code:
```python
from weblate.settings_docker import *
```
3. 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:
```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
```
4. 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](https://docs.docker.com/reference/compose-file/build/) for details on building images from
source when using `docker-compose`.
5. 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.
### Înlocuirea logo-ului și a altor fișiere statice
Fișierele statice care vin cu Weblate pot fi înlocuite prin plasarea în `/app/data/python/customize/static` (a se vedea [Volumele containerelor Docker](#docker-volume)). De exemplu, crearea `/app/data/python/customize/static/favicon.ico` va înlocui faviconul.
#### HINT
Fișierele sunt copiate în locația corespunzătoare la pornirea containerului, astfel încât este necesară o repornire a Weblate după modificarea conținutului volumului.
This approach can be also used to override Weblate templates. For example,
custom [Legal module](https://docs.weblate.org/ro/latest/admin/optionals.md#legal) documents and styles can be provided as described in
[Customizing legal documents and styles](https://docs.weblate.org/ro/latest/admin/optionals.md#legal-customization).
Alternativ, puteți, de asemenea, să includeți propriul modul (a se vedea [Personalizarea Weblate](https://docs.weblate.org/ro/latest/admin/customize.md)) și să îl adăugați ca volum separat la containerul Docker, de exemplu:
```yaml
weblate:
volumes:
- weblate-data:/app/data
- ./weblate_customization/weblate_customization:/app/data/python/weblate_customization
environment:
WEBLATE_ADD_APPS: weblate_customization
```
### 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 `/app/data/python/customize`
(see [Volumele containerelor Docker](#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 [Întocmirea propriilor cecuri](https://docs.weblate.org/ro/latest/admin/checks.md#own-checks)) or to add
custom maintenance tasks to the Celery task scheduler.
```python
"""Custom scheduled task."""
from __future__ import annotations
# ruff: ignore[suspicious-subprocess-import]
import subprocess
from typing import TYPE_CHECKING
from celery.schedules import crontab
from weblate.utils.celery import app
if TYPE_CHECKING:
from celery import Celery
@app.task
def custom_task() -> None:
"""Execute custom task code."""
# ruff: ignore[start-process-with-partial-path]
subprocess.run(["sleep", "1"], check=True)
@app.on_after_finalize.connect
def setup_periodic_tasks(sender: Celery, **kwargs: object) -> None:
"""Configure when periodic task is triggered."""
sender.add_periodic_task(
crontab(hour=1, minute=0), custom_task.s(), name="custom-task"
)
```
## 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
### 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 `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 `docker-compose.override.yml`:
```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):
```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 Machine translation → Automatic suggestions
3. Add a new LibreTranslate service with:
* **Serviciu:**
Traducere Libre
* **URL-UL API:**
`http://libretranslate:5000`
* **Cheia API:**
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.
#### SEE ALSO
* [Traducere Libre](https://docs.weblate.org/ro/latest/admin/machine.md#mt-libretranslate)
* [LibreTranslate Docker documentation](https://docs.libretranslate.com/guides/installation/#with-docker)
* [Sugestii automate](https://docs.weblate.org/ro/latest/admin/machine.md#machine-translation-setup)
### Anubis Docker container integration
[Anubis](https://anubis.techaro.lol/) 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:
```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
`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](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](https://anubis.techaro.lol/docs/admin/policies/#storage-backends).
You can then turn on the Anubis usage in Weblate using:
```yaml
environment:
WEBLATE_ANUBIS_URL: http://anubis:8923
```
#### SEE ALSO
[`WEBLATE_ANUBIS_URL`](#envvar-WEBLATE_ANUBIS_URL)
## Configurarea serverului PostgreSQL
Containerul PostgreSQL utilizează configurația PostgreSQL implicită și nu va utiliza eficient nucleele CPU sau memoria. Se recomandă personalizarea configurației pentru a îmbunătăți performanța.
Configurația poate fi ajustată așa cum este descris în Database Configuration la [https://hub.docker.com/_/postgres](https://hub.docker.com/_/postgres). Configurația care corespunde mediului dumneavoastră poate fi generată folosind [https://pgtune.leopard.in.ua/](https://pgtune.leopard.in.ua/).
## Container internals
The container is using **supervisor** to start individual services. In
case of [Scalare pe orizontală](#docker-scaling), it only starts single service in a container.
To check the services status use:
```sh
docker compose exec --user weblate weblate supervisorctl status
```
The Celery services depend on [`CELERY_WORKER_MODE`](#envvar-CELERY_WORKER_MODE). The default
`combined` mode runs `celery-combined`, while `single` mode runs
`celery-single`. You can stop all task processing in the default mode using:
```sh
docker compose exec --user weblate weblate supervisorctl stop celery-combined
```
The `split` mode runs an individual service for each Celery queue (see
[Sarcini de fundal folosind Celery](https://docs.weblate.org/ro/latest/admin/install.md#celery) for details). In this mode, you can stop processing some tasks by
stopping the appropriate worker:
```sh
docker compose exec --user weblate weblate supervisorctl stop celery-translate
```