horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

to allow representation of higher Unicode planes (for example emojis). Configure the server with innodb_large_prefix to allow longer indices on text fields. Set the isolation level to READ COMMITTED. The documentation on those details. It is absolutely critical to reduce issues when installing that the setting innodb_file_per_table is set properly and MySQL/MariaDB restarted before you start your Weblate install datadir=/var/lib/mysql log-error=/var/log/mariadb/mariadb.log innodb_large_prefix=1 innodb_file_format=Barracuda innodb_file_per_table=1 innodb_buffer_pool_size=2G sql_mode=STRICT_TRANS_TABLES Hint In

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED

horizontally. The /app/data volume has to be shared by all containers, it is recommended to use cluster filesystem such as GlusterFS for this. The /app/cache volume should be separate for each container Please follow carefully the documentation as some of the services should be running just once in the cluster and the ordering of the services matters as well. You can find example setup in the docker-compose allow representation of higher Unicode planes (for example emojis). • Configure the server with innodb_large_prefix to allow longer indices on text fields. • Set the isolation level to READ COMMITTED