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 the underlaying version control pending changes (see Lazy commits). This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to pull from the upstream repo. This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your

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 the underlaying version control pending changes (see Lazy commits). This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to pull from the upstream repo. This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your

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 the underlaying version control pending changes (see Lazy commits). This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to pull from the upstream repo. This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your

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 the underlaying version control pending changes (see Lazy commits). This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated if you grant Weblate push access to pull from the upstream repo. This can be achieved in the user interface (in the Repository maintenance) or from command line using Weblate Client. This can be automated by installing a webhook on your

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

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

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

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

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 Creating database for Weblate Creating database in PostgreSQL Creating database in MySQL Other configurations Configuring outgoing mail Installation Filling up the database Production setup debug mode Properly configure admins Set correct site name Enable indexing offloading Use powerful database engine Enable caching Avatar caching Configure email addresses Allowed hosts setup Federated avatar

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