template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will start 7. Start the development server (see Running server for production setup): weblate runserver A�er installation Congratulations, your Weblate server is now running and you can start using it. You

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will configuration in /app/data/settings- override.py (see Docker container volumes). This is executed a�er all environment settings are loaded, so it gets completely set up, and can be used to customize anything

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will configuration in /app/data/settings- override.py (see Docker container volumes). This is executed a�er all environment settings are loaded, so it gets completely set up, and can be used to customize anything

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will -aweblate app create -t python-2.7 --from-code https://github.com/WeblateOrg/weblate.git --no-git 2. A�er installation everything should be preconfigured, and you can immediately start adding a translation

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will configuration in /app/data/settings- override.py (see Docker container volumes). This is executed a�er all environment settings are loaded, so it gets completely set up, and can be used to customize anything

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will configuration in /app/data/settings- override.py (see Docker container volumes). This is executed a�er all environment settings are loaded, so it gets completely set up, and can be used to customize anything

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will configuration in /app/data/settings- override.py (see Docker container volumes). This is executed a�er all environment settings are loaded, so it gets completely set up, and can be used to customize anything

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will configuration in /app/data/settings- override.py (see Docker container volumes). This is executed a�er all environment settings are loaded, so it gets completely set up, and can be used to customize anything

template file, which you can use for starting new translations (using msginit) or updating existing ones a�er code change (you would use msgmerge for that). The resulting file is simply a structured text file: host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. A�er adding it please verify that the fingerprint matches the server youʼre adding, the fingerprints will -aweblate app create -t python-2.7 --from-code https://github.com/WeblateOrg/weblate.git --no-git 2. A�er installation everything should be preconfigured, and you can immediately start adding a translation

MySQL by default uses has different transaction locking scheme than other databases and in case you see er- rors like Deadlock found when trying to get lock; try restarting transaction it might be good idea you have update in same directory, stale *.pyc files might be left around and cause various import er- rors. To recover from this, delete all of them in Weblate’s directory, for example by find . -name