升級 Weblate¶
Docker 映像升級¶
The official Weblate Docker image (see 使用 Docker 安裝) integrates all upgrade steps. Typically, no manual interaction is needed beyond pulling the latest (or at least newer) version.
也參考
通用的升級說明¶
Always look for new changes to 軟體要求 before upgrading.
Once all requirements are installed or upgraded, ensure your
settings.py
matches the changes in the configuration (consult
settings_example.py
for correct values).
Always check Version-specific instructions before upgrading. If you are skipping any version(s), be sure to follow instructions for all versions you are skipping during such upgrade. It’s sometimes better to upgrade gradually to an intermediate version to ensure a smooth migration. Upgrading across multiple releases should work, but is not as well tested as single version upgrades!
備註
Always back up the full database before upgrading, so that you can roll back the database if the upgrade fails, see 備份和移動 Weblate.
Stop the WSGI and Celery processes to avoid old processes running while upgrading. Otherwise incompatible changes in the database might occur.
Upgrade Weblate
對於 pip 安裝,可以通過後面的來實現:
pip install -U "Weblate[all]==version"
或者,如果您只想取得最新發佈的版本:
pip install -U "Weblate[all]"
If you don’t want to install all of the optional dependencies do:
pip install -U Weblate
Using Git checkout, you need to fetch new source code and update your installation:
cd weblate-src git pull # Update Weblate inside your virtualenv . ~/weblate-env/bin/pip install -e '.[all]' # Install dependencies directly when not using virtualenv pip install --upgrade -e . # Install optional dependencies directly when not using virtualenv pip install --upgrade -e '.[all]'
New Weblate releases might have new Python 相依性, check if they cover the features you want.
Upgrade the configuration file by following either
settings_example.py
, or Version-specific instructions.Upgrade the database:
weblate migrate --noinput
收集升級的靜態文件(請參見 正在執行伺服器 和 靜態檔案服務):
weblate collectstatic --noinput --clear
壓縮 JavaScript 和 CSS 文件(可選步驟,請參見 壓縮客戶端素材 ):
weblate compress
If you are running an installation from Git, you should also regenerate locale files every time you upgrade. You can do this by invoking:
weblate compilemessages
驗證您的設定合理(還請參見 生產設定):
weblate check --deploy
Restart the Celery worker (see 使用 Celery 的後台任務).
Version-specific instructions¶
在 5.0 版的變更: Version specific instructions are now included in the release notes, see Weblate 5.7.
Upgrade from an older major version¶
Upgrades across major versions are not supported. Always upgrade to the latest patch level for the initial major release. Upgrades skipping this step are not supported and will break.
If you are upgrading from the 2.x release, always first upgrade to 3.0.1.
If you are upgrading from the 3.x release, always first upgrade to 4.0.4.
If you are upgrading from the 4.x release, always first upgrade to 5.0.2.
從其它資料庫遷移到 PostgreSQL¶
If you are not running Weblate with a different database than PostgreSQL, consider migrating to PostgreSQL for better performance by doing the following steps. Remember to stop both, the web and Celery servers beforehand, otherwise you might end up with inconsistent data.
建立 PostgreSQL資料庫¶
It is usually a good idea to run Weblate in a separate database, and a separate user account:
# If PostgreSQL was not installed before, set the main password
sudo -u postgres psql postgres -c "\password postgres"
# Create a database user called "weblate"
sudo -u postgres createuser -D -P weblate
# Create the database "weblate" owned by "weblate"
sudo -u postgres createdb -E UTF8 -O weblate weblate
使用 pgloader 遷移到 PostgreSQL¶
The pgloader is a generic migration tool to migrate data to PostgreSQL. You can use it to migrate your Weblate database.
Adjust your
settings.py
to use PostgreSQL as database.遷移 PostgreSQL 中的模式:
weblate migrate weblate sqlflush | weblate dbshell
3. Run the pgloader to transfer the data. The following script can be used to migrate the database, but you might want to learn more about pgloader to better understand what it does, and tweak it to match your setup:
LOAD DATABASE FROM mysql://weblate:password@localhost/weblate INTO postgresql://weblate:password@localhost/weblate WITH include no drop, truncate, create no tables, create no indexes, no foreign keys, disable triggers, reset sequences, data only ALTER SCHEMA 'weblate' RENAME TO 'public' ;
Migrating from Pootle¶
As Weblate was originally written as a replacement for Pootle, it is supported
to migrate the user accounts from it. You can dump the users from Pootle and
import them using importusers
.