Weblate on a single host (Weblate, database and webserver): • 2 GB of RAM • 2 CPU cores • 1 GB of storage space The more memory the better - it is used for caching on all levels (filesystem, database and components at least 4 GB of RAM is recommended. 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 WEBLATE_EMAIL_USE_SSL, EMAIL_USE_TLS WEBLATE_EMAIL_BACKEND Configures Django back-end to use for sending e-mails. See also: Configure e-mail sending, EMAIL_BACKEND Error reporting It is recommended to collect

Translate Toolkit [http://docs.translatehouse.org/projects/translate- toolkit/en/latest/api/storage.html#translate.storage.base.TranslationUnit] and XLIFF. New in version 2.10. GET /api/units/ Returns list python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database

Translate Toolkit [http://docs.translatehouse.org/projects/translate- toolkit/en/latest/api/storage.html#translate.storage.base.TranslationUnit] and XLIFF. New in version 2.10. GET /api/units/ Returns list python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database

Translate Toolkit [http://docs.translatehouse.org/projects/translate- toolkit/en/latest/api/storage.html#translate.storage.base.TranslationUnit] and XLIFF. New in version 2.10. GET /api/units/ Returns list python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database

Translate Toolkit [http://docs.translatehouse.org/projects/translate- toolkit/en/latest/api/storage.html#translate.storage.base.TranslationUnit] and XLIFF. New in version 2.10. GET /api/units/ Returns list python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database

python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database by adjusting the CACHES configuration variable, for example: CACHES = { "default": { "BACKEND": "django_redis.cache.RedisCache", "LOCATION": "redis://127.0.0.1:6379/0", # If redis

python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database by adjusting the CACHES configuration variable, for example: CACHES = { "default": { "BACKEND": "django_redis.cache.RedisCache", "LOCATION": "redis://127.0.0.1:6379/0", # If redis

python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database by adjusting the CACHES configuration variable, for example: CACHES = { "default": { "BACKEND": "django_redis.cache.RedisCache", "LOCATION": "redis://127.0.0.1:6379/0", # If redis

Translate Toolkit [http://docs.translatehouse.org/projects/translate- toolkit/en/latest/api/storage.html#translate.storage.base.TranslationUnit] and XLIFF. New in version 2.10. GET /api/units/ Returns list python-zeep.org/ aeidon (optional for Subtitle files) https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database

Translate Toolkit [http://docs.translatehouse.org/projects/translate- toolkit/en/latest/api/storage.html#translate.storage.base.TranslationUnit] and XLIFF. New in version 2.10. GET /api/units/ Returns list "Weblate[all]" Or you can install Weblate without any optional features: pip install Weblate Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and SESSION_ENGINE Configure how your sessions will be stored. In case you keep the default database backend engine, you should schedule: weblate clearsessions to remove stale session data from the database