Optional Weblate modules

Several optional modules are available for your setup.

Git exporter

バージョン 2.10 で追加.

Provides you read-only access to the underlying Git repository using HTTP(S).

導入

  1. Add weblate.gitexport to installed apps in settings.py:

INSTALLED_APPS += (
    'weblate.gitexport',
)
  1. Export existing repositories by migrating your database after installation:

weblate migrate

Usage

The module automatically hooks into Weblate and sets the exported repository URL in the Component configuration. The repositories are accessible under the /git/ part of the Weblate URL, for example https://example.org/git/weblate/master/:

git clone 'https://example.org/git/weblate/master/'

Repositories are available anonymously unless プロジェクト単位のアクセス制御 is turned on. This requires authenticate using your API token (it can be obtained in your ユーザー情報):

git clone 'https://user:KEY@example.org/git/weblate/master/'

請求

バージョン 2.4 で追加.

This is used on Hosted Weblate to define billing plans, track invoices and usage limits.

導入

1. Add weblate.billing to installed apps in settings.py:

INSTALLED_APPS += (
    'weblate.billing',
)
  1. Run the database migration to optionally install additional database structures for the module:

weblate migrate

Usage

After installation you can control billing in the admin interface. Users with billing enabled will get new Billing tab in their ユーザー情報.

The billing module additionally allows project admins to create new projects and components without being superusers (see Adding translation projects and components). This is possible when following conditions are met:

  • The billing is in its configured limits (any overusage results in blocking of project/component creation) and paid (if its price is non zero)

  • The user is admin of existing project with billing or user is owner of billing (the latter is necessary when creating new billing for users to be able to import new projects).

Upon project creation user is able to choose which billing should be charged for the project in case he has access to more of them.

Avatars

Avatars are downloaded and cached server-side to reduce information leaks to the sites serving them by default. The built-in support for fetching avatars from e-mails addresses configured for it can be turned off using ENABLE_AVATARS.

Weblate currently supports:

Spam protection

You can protect against suggestion spamming by unauthenticated users by using the akismet.com service.

  1. Install the akismet Python module

  2. Configure the Akismet API key.

注釈

This (among other things) relies on IP address of the client, please see Running behind reverse proxy for properly configuring that.

Signing Git commits with GnuPG

バージョン 3.1 で追加.

All commits can be signed by the GnuPG key of the Weblate instance.

1. Turn on WEBLATE_GPG_IDENTITY. (Weblate will generate a GnuPG key when needed and will use it to sign all translation commits.)

This feature needs GnuPG 2.1 or newer installed.

You can find the key in the DATA_DIR and the public key is shown on the "About" page:

../_images/about-gpg.png

2. Alternatively you can also import existing keys into Weblate, just set HOME=$DATA_DIR/home when invoking gpg.

レート制限

バージョン 3.2 で変更: レート制限では、さらに詳細な設定が可能になりました。

Several operations in Weblate are rate limited. At most RATELIMIT_ATTEMPTS attempts are allowed within RATELIMIT_WINDOW seconds. The user is then blocked for RATELIMIT_LOCKOUT. There are also settings specific to scopes, for example RATELIMIT_CONTACT_ATTEMPTS or RATELIMIT_TRANSLATE_ATTEMPTS. The table below is a full list of available scopes.

次の操作は、レート制限の対象となります。

名前

範囲

許可した試行回数

ウィンドウ レート制限

ブロック期間

登録

REGISTRATION

5

300

600

管理者へメッセージの送信

MESSAGE

5

300

600

ログイン時のパスワード認証

LOGIN

5

300

600

サイト全体の検索

SEARCH

6

60

60

翻訳

TRANSLATE

30

60

600

用語集に用語を追加

GLOSSARY

30

60

600

ユーザーがログインに AUTH_LOCK_ATTEMPTS 回失敗した場合、パスワードのリセット処理を完了するまで、アカウントのパスワード認証を無効にします。