Management commands¶
Nota
Running management commands under different user than is running your webserver can cause wrong permissions on some files, please check Filesystem permissions for more details.
The ./manage.py is extended with following commands:
checkgit <project|project/component>¶
-
manage.py checkgit¶
Prints current state of backend git repository.
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
commitgit <project|project/component>¶
-
manage.py commitgit¶
Commits any possible pending changes to backend git repository.
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
commit_pending <project|project/component>¶
-
manage.py commit_pending¶
Commits pending changes older than given age (using --age parameter,
defaults to 24 hours).
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
This is most useful if executed periodically from cron or similar tool:
./manage.py commit_pending --all --age=48
dumpuserdata <file.json>¶
-
manage.py dumpuserdata¶
Dumps userdata to file for later use by importuserdata
This is useful when migrating of merging Weblate instances.
import_project <project> <gitrepo> <branch> <filemask>¶
-
manage.py import_project¶
Batch imports components into project based on file mask.
<project> names an existing project, into which the components should be imported.
The <gitrepo> defines URL of Git repository to use, and <branch> the git branch. To import additional translation components, from an existing Weblate component, use a weblate://<project>/<component> URL for the <gitrepo>.
The repository is searched for directories matching a double wildcard (**) in the <filemask>. Each of these is then added as a component, named after the matched directory. Existing components will be skipped.
To customise the component’s name, use the --name-template option.
Its parameter is a python formatting string, which will expect the
match from <filemask>.
By format string passed by the --base-file-template option you can customize
base file for monolingual translations.
You can also specify file format to use (see Supported formats) by the
--file-format parameter. The default is autodetection.
In case you need to specify version control system to use, you can do this using
--vcs parameter. The default version control is Git.
To give you some examples, let’s try importing two projects.
As first we import The Debian Handbook translations, where each language has separate folder with translations of each chapter:
./manage.py import_project \
debian-handbook \
git://anonscm.debian.org/debian-handbook/debian-handbook.git \
squeeze/master \
'*/**.po'
Another example can be Tanaguru tool, where we need to specify file format, base file template and has all components and translations located in single folder:
./manage.py import_project \
--file-format=properties \
--base-file-template=web-app/tgol-web-app/src/main/resources/i18n/%s-I18N.properties \
tanaguru \
https://github.com/Tanaguru/Tanaguru \
master \
web-app/tgol-web-app/src/main/resources/i18n/**-I18N_*.properties
importuserdata <file.json>¶
-
manage.py importuserdata¶
Imports userdata from file created by dumpuserdata
importusers <file.json>¶
-
manage.py importusers¶
Imports users from JSON dump of Django auth_users database.
You can dump users from existing Django installation using:
./manage.py dumpdata auth.User > users.json
list_ignored_checks¶
-
manage.py list_ignored_checks¶
Lists most frequently ignored checks. This can be useful for tuning your setup, if users have to ignore too many of consistency checks.
loadpo <project|project/component>¶
-
manage.py loadpo¶
Reloads translations from disk (eg. in case you did some updates in VCS repository).
You can use --force to force update even if the files should be up
to date. Additionally you can limit languages to process with --lang.
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
lock_translation <project|project/component>¶
-
manage.py lock_translation¶
Locks given component for translating. This is useful in case you want to do some maintenance on underlaying repository.
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
Ver también
pushgit <project|project/component>¶
-
manage.py pushgit¶
Pushes committed changes to upstream VCS repository. With --force-commit
it also commits any pending changes.
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
rebuild_index <project|project/component>¶
-
manage.py rebuild_index¶
Rebuilds index for fulltext search. This might be lengthy operation if you have huge set of translation units.
You can use --clean to remove all words from database prior updating.
Ver también
update_index¶
-
manage.py update_index¶
Updates index for fulltext search when OFFLOAD_INDEXING is enabled.
It is recommended to run this frequently (eg. every 5 minutes) to have index uptodate.
Ver también
unlock_translation <project|project/component>¶
-
manage.py unlock_translation¶
Unnocks given component for translating. This is useful in case you want to do some maintenance on underlaying repository.
You can either define which project or component to update (eg.
weblate/master) or use --all to update all existing components.
Ver también
setupgroups¶
-
manage.py setupgroups¶
Configures default groups and (if called with --move) assigns all users
to default group.
The option --no-update disables update of existing groups (only adds
new ones).
Ver también
setuplang¶
-
manage.py setuplang¶
Setups list of languages (it has own list and all defined in translate-toolkit).
The option --no-update disables update of existing languages (only adds
new ones).