https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements ALTER_ROLE to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Hint Some Weblate features will perform better with PostgreSQL. This includes searching and translation MySQL or MariaDB, please see MySQL notes [https://docs.djangoproject.com/en/stable/ref/databases/#mysql-notes] and MariaDB notes [https://docs.djangoproject.com/en/stable/ref/databases/#mariadb-notes]

https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements ALTER_ROLE to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Hint Some Weblate features will perform better with PostgreSQL. This includes searching and translation MySQL or MariaDB, please see MySQL notes [https://docs.djangoproject.com/en/stable/ref/databases/#mysql-notes] and MariaDB notes [https://docs.djangoproject.com/en/stable/ref/databases/#mariadb-notes]

features: pip install Weblate Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning: While MySQL and MariaDB support is still maintained in Weblate, our primary focus is Post- greSQL. It is PostgreSQL implementation is superior. Weblate can be also used with MySQL or MariaDB, please see MySQL notes and MariaDB notes for caveats using Django with those. Because of the limitations it is recommended

features: pip install Weblate Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning: While MySQL and MariaDB support is still maintained in Weblate, our primary focus is Post- greSQL. It is PostgreSQL implementation is superior. Weblate can be also used with MySQL or MariaDB, please see MySQL notes and MariaDB notes for caveats using Django with those. Because of the limitations it is recommended

features: pip install Weblate Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning: While MySQL and MariaDB support is still maintained in Weblate, our primary focus is Post- greSQL. It is PostgreSQL implementation is superior. Weblate can be also used with MySQL or MariaDB, please see MySQL notes and MariaDB notes for caveats using Django with those. Because of the limitations it is recommended

without any optional features: Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning While MySQL and MariaDB support is still maintained in Weblate, our primary focus is PostgreSQL. It is recommended MySQL or MariaDB, please see MySQL notes [https://docs.djangoproject.com/en/stable/ref/databases/#mysql-notes] and MariaDB notes [https://docs.djangoproject.com/en/stable/ref/databases/#mariadb-notes]

without any optional features: Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning While MySQL and MariaDB support is still maintained in Weblate, our primary focus is PostgreSQL. It is recommended MySQL or MariaDB, please see MySQL notes [https://docs.djangoproject.com/en/stable/ref/databases/#mysql-notes] and MariaDB notes [https://docs.djangoproject.com/en/stable/ref/databases/#mariadb-notes]

without any optional features: Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements name of the role Weblate should alter during the database migration. MySQL and MariaDB Warning While MySQL and MariaDB support is still maintained in Weblate, our primary focus is PostgreSQL. It is recommended MySQL or MariaDB, please see MySQL notes [https://docs.djangoproject.com/en/stable/ref/databases/#mysql-notes] and MariaDB notes [https://docs.djangoproject.com/en/stable/ref/databases/#mariadb-notes]

https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements ALTER_ROLE to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Hint: Some Weblate features will perform better with PostgreSQL. This includes searching and translation PostgreSQL implementation is superior. Weblate can be also used with MySQL or MariaDB, please see MySQL notes and MariaDB notes for caveats using Django with those. Because of the limitations it is recommended

https://pypi.org/project/aeidon/ Database backend dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements ALTER_ROLE to change name of the role Weblate should alter during the database migration. MySQL and MariaDB Hint: Some Weblate features will perform better with PostgreSQL. This includes searching and translation PostgreSQL implementation is superior. Weblate can be also used with MySQL or MariaDB, please see MySQL notes and MariaDB notes for caveats using Django with those. Because of the limitations it is recommended