worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers matches the number of processors See also: How to use Django with uWSGI Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to under path Changed in version 1.3: This is supported since Weblate 1.3. It is recommended to use prefork MPM when using WSGI with Weblate. A sample Apache configuration to serve Weblate under /weblate

worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers matches the number of processors adb.log innodb_large_prefix=1 innodb_file_format=Barracuda innodb_file_per_table=1 innodb_buffer_pool_size=2G sql_mode=STRICT_TRANS_TABLES 170 Chapter 2. Administrator docs The Weblate Manual, Release docs The Weblate Manual, Release 4.5.3 Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to

worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers matches the number of processors adb.log innodb_large_prefix=1 innodb_file_format=Barracuda innodb_file_per_table=1 innodb_buffer_pool_size=2G sql_mode=STRICT_TRANS_TABLES 170 Chapter 2. Administrator docs The Weblate Manual, Release docs The Weblate Manual, Release 4.5.2 Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to

worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers is based on WEBLATE_WORKERS. Example: adb.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 case you are getting #1071 - Specified key was too See also: How to use Django with uWSGI Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to

worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers matches the number of processors adb.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 case you are getting #1071 - Specified key was too 179 The Weblate Manual, Release 4.5 Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to

worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers matches the number of processors adb.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 case you are getting #1071 - Specified key was too 181 The Weblate Manual, Release 4.5.1 Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to

worker options. It can be useful to adjust concurrency (-- concurrency 16) or use different pool implementation (--pool=gevent). By default, the number of concurrent workers matches the number of processors adb.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 case you are getting #1071 - Specified key was too See also: How to use Django with uWSGI Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to

db.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 case you are getting #1071 - Specified key was too com/en/stable/howto/deployment/wsgi/uwsgi/] Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to ment/wsgi/gunicorn/] Running Weblate under path New in version 1.3. It is recommended to use prefork MPM when using WSGI with Weblate. A sample Apache configuration to serve Weblate under /weblate

db.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 case you are getting #1071 - Specified key was too com/en/stable/howto/deployment/wsgi/uwsgi/] Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to ment/wsgi/gunicorn/] Running Weblate under path New in version 1.3. It is recommended to use prefork MPM when using WSGI with Weblate. A sample Apache configuration to serve Weblate under /weblate

adb.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 case you are getting #1071 - Specified key was too com/en/stable/howto/deployment/wsgi/uwsgi/] Sample configuration for Apache It is recommended to use prefork MPM when using WSGI with Weblate. The following configuration runs Weblate as WSGI, you need to ment/wsgi/gunicorn/] Running Weblate under path New in version 1.3. It is recommended to use prefork MPM when using WSGI with Weblate. A sample Apache configuration to serve Weblate under /weblate