Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s also Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

3 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s also: Fulltext search, OFFLOAD_INDEXING Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)

3 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s Weblate Documentation, Release 2.4 Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = and preconfigured as follows: 4.3. Weblate deployments 41 Weblate Documentation, Release 2.4 • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)

Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

4 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)

files Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

files Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: SQLite embedded database (DATABASES) Random admin password Random Django secret key (SECRET_KEY) Indexing

4 Creating database for Weblate It is recommended to run Weblate on some database server. Using SQLite backend is really good for testing purposes only. See also: Use powerful database engine, Django’s OFFLOAD_INDEXING, Running maintenance tasks Use powerful database engine Use powerful database engine (SQLite is usually not good enough for production environment), for example setup for MySQL: DATABASES = Configuration After installation on OpenShift Weblate is ready to use and preconfigured as follows: • SQLite embedded database (DATABASES) • Random admin password • Random Django secret key (SECRET_KEY)