1
0
Fork 0
mirror of https://github.com/YunoHost-Apps/weblate_ynh.git synced 2024-10-01 13:35:04 +02:00
Weblate package for YunoHost
Find a file
2017-10-19 11:01:39 +02:00
conf Add upgrade support to 2.17.1 2017-10-18 23:10:32 +02:00
scripts add new helper ynh_check_if_checksum_is_different 2017-10-19 11:01:39 +02:00
sources First version, all tests are to be done 2017-09-13 14:49:10 +02:00
.gitignore Initial commit 2017-09-13 12:17:55 +02:00
check_process Improve root installation 2017-10-17 15:46:35 +02:00
LICENSE switch from GPL3 to AGPL3 2017-09-13 17:19:18 +02:00
manifest.json Add upgrade support to 2.17.1 2017-10-18 23:10:32 +02:00
README.md Improve readme for upgrades 2017-10-18 23:11:10 +02:00

Weblate translation platform for YunoHost

The YunoHost team uses Weblate for translations: https://translate.yunohost.org

Admin account

An admin user is created at installation, the login is what you provided at installation, the password is weblate.

Github

You'll need to give weblate a github user and a token. Please read github's documentation about token. This user will only be used to open the pull-request, each translation keep his author.

Settings and upgrades

Almost everything related to Weblate's configuration is handled in a settings.py file. You'll probably edit it to enable or disable diverse features, it is stored in $final_path/venv/lib/python2.7/site-packages/weblate/settings.py.

Unfortunatly, this settings file also gets upgrades for each release.

This package will :

  • generate a default settings file for your current installation,
  • send you a diff with your actual settings (the content will be sent to root, and only basic information for weblate's admin),
  • generate a default settings file the new weblate's version, that will replace your actual settings.py.

You'll have to manually add your previous changes to this new settings.py.

Miscellaneous

Weblate and databases

Weblate recommands PostgreSQL, but YunoHost uses Mysql.

Carefull, this application install PostgreSQL and change the default configuration to ask for every connexion and every user a password (local all all password).

LDAP connexion

It doesn't work yet, but while it looks doable, I'm unsure it is a good idea to connect this kind of tools to your LDAP.