Upgrading Weblate¶
Upgrading¶
Generic upgrade instructions¶
Distinto en la versión 1.2: Since version 1.2 the migration is done using South module, to upgrade to 1.2, please see Version specific instructions.
Distinto en la versión 1.9: Since version 1.9, Weblate also supports Django 1.7 migrations, please check Upgrading to Django 1.7 for more information.
Before upgrading, please check current Requirements as they might have changed.
To upgrade database structure, you should run following commands:
./manage.py syncdb
./manage.py migrate
To upgrade default set of privileges definitions (optional), run:
./manage.py setupgroups
To upgrade default set of language definitions (optional), run:
./manage.py setuplang
Version specific instructions¶
Upgrade from 0.5 to 0.6¶
On upgrade to version 0.6 you should run ./manage.py syncdb
and
./manage.py setupgroups --move
to setup access control as described
in installation section.
Upgrade from 0.6 to 0.7¶
On upgrade to version 0.7 you should run ./manage.py syncdb
to
setup new tables and ./manage.py rebuild_index
to build index for
fulltext search.
Upgrade from 0.7 to 0.8¶
On upgrade to version 0.8 you should run ./manage.py syncdb
to setup
new tables, ./manage.py setupgroups
to update privileges setup and
./manage.py rebuild_index
to rebuild index for fulltext search.
Upgrade from 0.8 to 0.9¶
On upgrade to version 0.9 file structure has changed. You need to move
repos
and whoosh-index
to weblate
folder. Also running
./manage.py syncdb
, ./manage.py setupgroups
and
./manage.py setuplang
is recommended to get latest updates of
privileges and language definitions.
Upgrade from 0.9 to 1.0¶
On upgrade to version 1.0 one field has been added to database, you need to invoke following SQL command to adjust it:
ALTER TABLE `trans_subproject` ADD `template` VARCHAR(200);
Upgrade from 1.0 (1.1) to 1.2¶
On upgrade to version 1.2, the migration procedure has changed. It now uses South for migrating database. To switch to this new migration schema, you need to run following commands:
./manage.py syncdb
./manage.py migrate trans 0001 --fake
./manage.py migrate accounts 0001 --fake
./manage.py migrate lang 0001 --fake
Also please note that there are several new requirements and version 0.8 of django-registration is now being required, see Requirements for more details.
Once you have done this, you can use Generic upgrade instructions.
Upgrade from 1.2 to 1.3¶
Since 1.3, settings.py
is not shipped with Weblate, but only example
settings as settings_example.py
it is recommended to use it as new base
for your setup.
Upgrade from 1.4 to 1.5¶
Several internal modules and paths have been renamed and changed, please adjust
your settings.py
to match that (consult settings_example.py
for
correct values).
- Many modules lost their
weblate.
prefix. - Checks were moved to submodules.
- Locales were moved to top level directory.
The migration of database structure to 1.5 might take quite long, it is recommended to put your site offline, while the migration is going on.
Nota
If you have update in same directory, stale *.pyc
files might be
left around and cause various import errors. To recover from this, delete
all of them in Weblate’s directory, for example by
find . -name '*.pyc' -delete
.
Upgrade from 1.6 to 1.7¶
The migration of database structure to 1.7 might take quite long, it is recommended to put your site offline, while the migration is going on.
If you are translating monolingual files, it is recommended to rerun quality checks as they might have been wrongly linked to units in previous versions.
Upgrade from 1.7 to 1.8¶
The migration of database structure to 1.8 might take quite long, it is recommended to put your site offline, while the migration is going on.
Authentication setup has been changed and some internal modules have changed
name, please adjust your settings.py
to match that (consult
settings_example.py
for correct values).
Also please note that there are several new requirements, see Requirements for more details.
Upgrade from 1.8 to 1.9¶
Several internal modules and paths have been renamed and changed, please adjust
your settings.py
to match that (consult settings_example.py
for
correct values).
Ver también
If you are upgrading to Django 1.7 in same step, please consult Upgrading to Django 1.7.
Upgrade from 1.9 to 2.0¶
Several internal modules and paths have been renamed and changed, please adjust
your settings.py
to match that (consult settings_example.py
for
correct values).
This upgrade also requires you to upgrade python-social-auth from 0.1.x to 0.2.x series, what will most likely to need to fake one of their migrations (see Upgrading PSA with South for more information):
./manage.py migrate --fake default
Ver también
If you are upgrading to Django 1.7 in same step, please consult Upgrading to Django 1.7.
Upgrade from 2.0 to 2.1¶
The filesystem paths configuration has changed, the GIT_ROOT
and
WHOOSH_INDEX
are gone and now all data resides in
DATA_DIR
. The existing data should be automatically migrated by
supplied migration, but in case of non standard setup, you might need to move
these manually.
Ver también
If you are upgrading to Django 1.7 in same step, please consult Upgrading to Django 1.7.
Upgrading to Django 1.7¶
Please adjust your settings.py
to match several changes in the
configuration (consult settings_example.py
for correct values).
Django 1.7 has a new feature to handle database schema upgrade called «migrations» which is incompatible with South (used before by Weblate).
Before migrating to Django 1.7, you first need to apply all migrations from
South. If you already have upgraded Django to 1.7, you can do this using
virtualenv and examples/migrate-south
script:
examples/migrate-south --settings weblate.settings
Once you have done that, you can run Django 1.7 migrations and work as usual.
Migrating from Pootle¶
As Weblate was originally written as replacement from Pootle, it is supported
to migrate user accounts from Pootle. All you need to do is to copy
auth_user
table from Pootle, user profiles will be automatically created
for users as they log in and they will be asked to update their settings.
Alternatively you can use importusers
to import dumped user
credentials.