private SSH key can not currently have a password, so make sure it is well protected. Hint: Make a backup of the generated private Weblate SSH key. 1.11. Version control integration 109 The Weblate Manual container: docker compose stop weblate cache 2. Backup the database: docker compose exec database pg_dumpall --clean --if-exists --username weblate␣ �→> backup.sql 3. Stop the database container: docker Start the database container: docker compose up -d database 7. Restore the database from the backup: cat backup.sql | docker compose exec -T database psql --username weblate -- �→dbname weblate Hint: Please

private SSH key can not currently have a password, so make sure it is well protected. Hint: Make a backup of the generated private Weblate SSH key. 1.11. Version control integration 109 The Weblate Manual container: docker compose stop weblate cache 2. Backup the database: docker compose exec database pg_dumpall --clean --if-exists --username weblate␣ �→> backup.sql 3. Stop the database container: docker Start the database container: docker compose up -d database 7. Restore the database from the backup: cat backup.sql | docker compose exec -T database psql --username weblate -- �→dbname weblate Hint: Please

private SSH key can not currently have a password, so make sure it is well protected. Hint: Make a backup of the generated private Weblate SSH key. 1.11. Version control integration 109 The Weblate Manual container: docker compose stop weblate cache 2. Backup the database: docker compose exec database pg_dumpall --clean --if-exists --username weblate␣ �→> backup.sql 3. Stop the database container: docker Start the database container: docker compose up -d database 7. Restore the database from the backup: cat backup.sql | docker compose exec -T database psql --username weblate -- �→dbname weblate Hint: Please

private SSH key can not currently have a password, so make sure it is well protected. Hint Make a backup of the generated private Weblate SSH key. Verifying SSH host keys Weblate automatically stores Weblate without any optional features: Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning While MySQL and MariaDB support is still maintained in Weblate, our primary focus is PostgreSQL

private SSH key can not currently have a password, so make sure it is well protected. Hint Make a backup of the generated private Weblate SSH key. Verifying SSH host keys Weblate automatically stores Weblate without any optional features: Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning While MySQL and MariaDB support is still maintained in Weblate, our primary focus is PostgreSQL

private SSH key can not currently have a password, so make sure it is well protected. Hint Make a backup of the generated private Weblate SSH key. Verifying SSH host keys Weblate automatically stores Weblate without any optional features: Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning While MySQL and MariaDB support is still maintained in Weblate, our primary focus is PostgreSQL

2. 备份数据库： docker compose exec database pg_dumpall --clean --if-exists --username weblate␣ �→> backup.sql 3. 停止数据库容器： docker compose stop database 4. 删除 PostgreSQL 卷： docker compose rm -v database 调整:file:‘docker-compose.yml‘以使用新的 PostgreSQL 版本。 6. 启动数据库容器： docker compose up -d database 7. 从备份恢复数据库： cat backup.sql | docker compose exec -T database psql --username weblate -- �→dbname weblate 提示: 请检查数据库名称匹配 CELERY_MAIN_OPTIONS, CELERY_NOTIFY_OPTIONS, CELERY_MEMORY_OPTIONS, CELERY_TRANSLATE_OPTIONS, CELERY_BACKUP_OPTIONS, CELERY_BEAT_OPTIONS, WEB_WORKERS 横向扩展 在 4.6 版本加入. 您可以运行多个 Weblate 容器来水平扩展服务。/app/data

2. 备份数据库： docker compose exec database pg_dumpall --clean --if-exists --username weblate␣ �→> backup.sql 3. 停止数据库容器： docker compose stop database 4. 删除 PostgreSQL 卷： docker compose rm -v database 调整:file:‘docker-compose.yml‘以使用新的 PostgreSQL 版本。 6. 启动数据库容器： docker compose up -d database 7. 从备份恢复数据库： cat backup.sql | docker compose exec -T database psql --username weblate -- �→dbname weblate 提示: 请检查数据库名称匹配 CELERY_MAIN_OPTIONS, CELERY_NOTIFY_OPTIONS, CELERY_MEMORY_OPTIONS, CELERY_TRANSLATE_OPTIONS, CELERY_BACKUP_OPTIONS, CELERY_BEAT_OPTIONS, WEB_WORKERS 横向扩展 在 4.6 版本加入. 您可以运行多个 Weblate 容器来水平扩展服务。/app/data

2. 备份数据库： docker compose exec database pg_dumpall --clean --if-exists --username weblate␣ �→> backup.sql 3. 停止数据库容器： docker compose stop database 4. 删除 PostgreSQL 卷： docker compose rm -v database 调整:file:‘docker-compose.yml‘以使用新的 PostgreSQL 版本。 6. 启动数据库容器： docker compose up -d database 7. 从备份恢复数据库： cat backup.sql | docker compose exec -T database psql --username weblate -- �→dbname weblate 提示: 请检查数据库名称匹配 CELERY_MAIN_OPTIONS, CELERY_NOTIFY_OPTIONS, CELERY_MEMORY_OPTIONS, CELERY_TRANSLATE_OPTIONS, CELERY_BACKUP_OPTIONS, CELERY_BEAT_OPTIONS, WEB_WORKERS 横向扩展 在 4.6 版本加入. 您可以运行多个 Weblate 容器来水平扩展服务。/app/data

进行安装时，您可以在安装时直接指定所需的功能： 或者你可以安装具有所有可选功能的 Weblate： 或者你可以安装没有任何可选功能的 Weblate： 数据库后端依赖项 Weblate 支持 PostgreSQL、MySQL 和 MariaDB，更多细节请参见 Weblate 的数 据库设置 和后端文档。 其他系统要求 必须在系统上安装以下依赖项： Git https://git-scm.com/ Pango、Cairo PostgreSQL 的 Azure 数据库时发生，但并不仅限于这种环境。请将 ALTER_ROLE 设置为数据库合并过程中 Weblate 应该更改的角色的名称。 MySQL 和 MariaDB 警告 虽然 Weblate 仍继续支持 MySQL 和 MariaDB，我们的主要精力已经在 PostgreSQL 上。新安装推荐使用 PostgreSQL，要迁移现有安装到 PostgreSQL，请见 从其它数据库迁移到 PostgreSQL 的实现更胜一筹。 Weblate 还可以使用 MySQL 或 MariaDB，使用与两个数据库相关的 Django 而 导致的警告，请参见 MySQL 注意事项 [https://docs.djangoproject.com/zh- hans/stable/ref/databases/#mysql-notes] 和 MariaDB 注意事项 [https://docs.djangoproject