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 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 the 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 the 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 Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Enable indexing offloading Use powerful database engine Enable 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 the 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 Filling up the database Production setup Disable debug mode Properly configure admins Set correct site name Correctly configure HTTPS Enable indexing offloading Use powerful database engine Enable 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 the underlaying version control need to configure the database connection (possibly adding user and creating the database). Check Configuration for Weblate specific configuration options. 4. Create the database which will be used by by Weblate, see Database setup for Weblate. 5. Build Django tables, static files and initial data (see Filling up the database and Serving static files): ./manage.py migrate ./manage.py collectstatic

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 need to configure the database connection (possibly adding user and creating the database). Check Configuration for Weblate specific configuration options. 4. Create the database which will be used by by Weblate, see Database setup for Weblate. 5. Build Django tables, static files and initial data (see Filling up the database and Serving static files): ./manage.py migrate ./manage.py collectstatic

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 for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development server. 1. Install development files for libraries needed settings file for Weblate: export DJANGO_SETTINGS_MODULE=weblate.settings 9. Create the SQLite database and its structure for Weblate: weblate migrate 10. Create the administrator user account and copy

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 for you, you can install it using a virtual environment for Python 2, a simple (and slow!) SQLite database, and the lightweight Django development server. 1. Install development files for libraries needed settings file for Weblate: export DJANGO_SETTINGS_MODULE=weblate.settings 9. Create the SQLite database and its structure for Weblate: weblate migrate 10. Create the administrator user account and copy

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 permissions Database setup for Weblate PostgreSQL Creating a database in PostgreSQL Configuring Weblate to use PostgreSQL MySQL or MariaDB Unicode issues in MySQL Transaction locking Creating a database in Installation Filling up the database Production setup Disable debug mode Properly configure admins Set correct sitename Correctly configure HTTPS Use a 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 the underlying 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 Correctly configure HTTPS Use powerful database engine Enable caching Avatar