Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless disabled in component settings) saved in the database and can be reverted. Of course you can still also revert anything in underlaying version control permissions Database setup for Weblate PostgreSQL Creating database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating database in MySQL Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control example.com as the domain? Weblate uses Djangoʼs sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also Set correct sitename Why This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control example.com as the domain? Weblate uses Djangoʼs sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also Set correct sitename Why This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control example.com as the domain? Weblate uses Django’s sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also Set correct sitename Why This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control example.com as the domain? Weblate uses Django’s sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also Set correct sitename Why This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control example.com as the domain? Weblate uses Djangoʼs sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also Set correct sitename Why This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you

Translation history Every change is by default (unless turned off in component settings) saved in the database, and can be reverted. Optionally one can still also revert anything in the underlying version control example.com as the domain? Weblate uses Django’s sites framework and defines the sitename inside the database. You need to set the domain name to match your installation. See also Set correct sitename Why This is the best approach for a one-time translation using a compendium or a similar translation database. You can set up tmserver with all databases you have and let Weblate use it. This is good when you