Configuration
All settings are stored in settings.py
(as is usual for Django).
Not
After changing any of these settings, you need to restart Weblate - both WSGI and Celery processes.
In case it is run as mod_wsgi
, you need to restart Apache to reload the
configuration.
Ayrıca bakınız
Please also check Django’s documentation for parameters configuring Django itself.
ANONYMOUS_USER_NAME
Username of users that are not signed in.
Ayrıca bakınız
AUDITLOG_EXPIRY
3.6 sürümünde geldi.
How many days Weblate should keep audit logs, which contain info about account activity.
Defaults to 180 days.
AUTH_LOCK_ATTEMPTS
2.14 sürümünde geldi.
Maximum number of failed authentication attempts before rate limiting is applied.
This is currently applied in the following locations:
Logins. Deletes the account password, preventing the user from signing in without requesting a new password.
Password resets. Prevents new e-mails from being sent, avoiding spamming users with too many password reset attempts.
Defaults to 10.
Ayrıca bakınız
AUTO_UPDATE
3.2 sürümünde geldi.
3.11 sürümünde değişti: The original on/off option was changed to differentiate which strings are accepted.
Updates all repositories on a daily basis.
İpucu
Useful if you are not using Bildirim kancaları to update Weblate repositories automatically.
Not
On/off options exist in addition to string selection for backward compatibility.
Options are:
"none"
No daily updates.
"remote"
alsoFalse
Only update remotes.
"full"
alsoTrue
Update remotes and merge working copy.
Not
This requires that Background tasks using Celery is working, and will take effect after it is restarted.
AVATAR_URL_PREFIX
Prefix for constructing avatar URLs as:
${AVATAR_URL_PREFIX}/avatar/${MAIL_HASH}?${PARAMS}
.
The following services are known to work:
- Gravatar (default), as per https://gravatar.com/
AVATAR_URL_PREFIX = 'https://www.gravatar.com/'
- Libravatar, as per https://www.libravatar.org/
AVATAR_URL_PREFIX = 'https://www.libravatar.org/'
Ayrıca bakınız
AUTH_TOKEN_VALID
2.14 sürümünde geldi.
How long the authentication token and temporary password from password reset e-mails is valid for. Set in number of seconds, defaulting to 172800 (2 days).
AUTH_PASSWORD_DAYS
2.15 sürümünde geldi.
How many days using the same password should be allowed.
Not
Password changes made prior to Weblate 2.15 will not be accounted for in this policy.
Defaults to 180 days.
AUTOFIX_LIST
List of automatic fixes to apply when saving a string.
Not
Provide a fully-qualified path to the Python class that implementing the autofixer interface.
Available fixes:
weblate.trans.autofixes.whitespace.SameBookendingWhitespace
Matches whitespace at the start and end of the string to the source.
weblate.trans.autofixes.chars.ReplaceTrailingDotsWithEllipsis
Replaces trailing dots (…) if the source string has a corresponding ellipsis (…).
weblate.trans.autofixes.chars.RemoveZeroSpace
Removes zero-width space characters if the source does not contain any.
weblate.trans.autofixes.chars.RemoveControlChars
Removes control characters if the source does not contain any.
weblate.trans.autofixes.html.BleachHTML
Removes unsafe HTML markup from strings flagged as
safe-html
(see Güvenli olmayan HTML).
You can select which ones to use:
AUTOFIX_LIST = (
"weblate.trans.autofixes.whitespace.SameBookendingWhitespace",
"weblate.trans.autofixes.chars.ReplaceTrailingDotsWithEllipsis",
)
Ayrıca bakınız
BACKGROUND_TASKS
4.5.2 sürümünde geldi.
Defines how often lengthy maintenance tasks should be triggered for a component.
Right now this controls:
Kendiliğinden çeviri eklentisi
Checks and fixups recalculation
Olası seçenekler:
monthly
(this is the default)weekly
daily
never
Not
Increasing the frequency is not recommended when Weblate contains thousands of components.
BASE_DIR
Base directory where Weblate sources are located. Used to derive several other paths by default:
Default value: Top level directory of Weblate sources.
BASIC_LANGUAGES
4.4 sürümünde geldi.
List of languages to offer users for starting new translation. When not specified built-in list is used which includes all commonly used languages, but without country specific variants.
This only limits non privileged users to add unwanted languages. The project admins are still presented with full selection of languages defined in Weblate.
Not
This does not define new languages for Weblate, it only filters existing ones in the database.
Example:
BASIC_LANGUAGES = {"cs", "it", "ja", "en"}
Ayrıca bakınız
BORG_EXTRA_ARGS
4.9 sürümünde geldi.
You can pass additional arguments to borg create when built-in backups are triggerd.
Example:
BORG_EXTRA_ARGS = ["--exclude", "vcs/"]
Ayrıca bakınız
CSP_SCRIPT_SRC, CSP_IMG_SRC, CSP_CONNECT_SRC, CSP_STYLE_SRC, CSP_FONT_SRC
Customize Content-Security-Policy
header for Weblate. The header is
automatically generated based on enabled integrations with third-party services
(Matomo, Google Analytics, Sentry, …).
All these default to empty list.
Example:
# Enable Cloudflare Javascript optimizations
CSP_SCRIPT_SRC = ["ajax.cloudflare.com"]
Ayrıca bakınız
CHECK_LIST
List of quality checks to perform on a translation.
Not
Provide a fully-qualified path to the Python class implementing the check interface.
Adjust the list of checks to include ones relevant to you.
All built-in Quality checks are turned on by default, from where you can change these settings. By default they are commented out in Sample configuration so that default values are used. New checks then carried out for each new Weblate version.
You can turn off all checks:
CHECK_LIST = ()
You can turn on only a few:
CHECK_LIST = (
"weblate.checks.chars.BeginNewlineCheck",
"weblate.checks.chars.EndNewlineCheck",
"weblate.checks.chars.MaxLengthCheck",
)
Not
Changing this setting only affects newly changed translations, existing checks
will still be stored in the database. To also apply changes to the stored translations, run
updatechecks
.
Ayrıca bakınız
COMMIT_PENDING_HOURS
2.10 sürümünde geldi.
Number of hours between committing pending changes by way of the background task.
CONTACT_FORM
4.6 sürümünde geldi.
Configures how e-mail from the contact form is being sent. Choose a configuration that matches your mail server configuration.
"reply-to"
The sender is used in as Reply-To, this is the default behaviour.
"from"
The sender is used in as From. Your mail server needs to allow sending such e-mails.
DATA_DIR
The folder Weblate stores all data in. It contains links to VCS repositories, a fulltext index and various configuration files for external tools.
The following subdirectories usually exist:
home
Home directory used for invoking scripts.
ssh
SSH keys and configuration.
static
Default location for static Django files, specified by
STATIC_ROOT
. See Serving static files.The Docker container uses a separate volume for this, see Docker container volumes.
media
Default location for Django media files, specified by
MEDIA_ROOT
. Contains uploaded screenshots, see Visual context for strings.vcs
Çeviriler için sürüm denetimi depoları.
backups
Daily backup data, please check Dumped data for backups for details.
celery
Celery scheduler data, see Background tasks using Celery.
fonts
:User-uploaded fonts, see Managing fonts.
Not
This directory has to be writable by Weblate. Running it as uWSGI means
the www-data
user should have write access to it.
The easiest way to achieve this is to make the user the owner of the directory:
sudo chown www-data:www-data -R $DATA_DIR
Defaults to $BASE_DIR/data
.
Ayrıca bakınız
BASE_DIR
,
Filesystem permissions,
Backing up and moving Weblate
DATABASE_BACKUP
3.1 sürümünde geldi.
Whether the database backups should be stored as plain text, compressed or skipped. The authorized values are:
"plain"
"compressed"
"none"
Ayrıca bakınız
DEFAULT_ACCESS_CONTROL
3.3 sürümünde geldi.
The default access control setting for new projects:
0
Public
1
Protected
100
Private
200
Custom
Use Custom if you are managing ACL manually, which means not relying on the internal Weblate management.
Ayrıca bakınız
DEFAULT_AUTO_WATCH
4.5 sürümünde geldi.
Configures whether Automatically watch projects on contribution
should be turned on for new users. Defaults to True
.
Ayrıca bakınız
DEFAULT_RESTRICTED_COMPONENT
4.1 sürümünde geldi.
The default value for component restriction.
Ayrıca bakınız
DEFAULT_ADD_MESSAGE, DEFAULT_ADDON_MESSAGE, DEFAULT_COMMIT_MESSAGE, DEFAULT_DELETE_MESSAGE, DEFAULT_MERGE_MESSAGE
Default commit messages for different operations, please check Component configuration for details.
DEFAULT_ADDONS
Default addons to install on every created component.
Not
This setting affects only newly created components.
Example:
DEFAULT_ADDONS = {
# Add-on with no parameters
"weblate.flags.target_edit": {},
# Add-on with parameters
"weblate.autotranslate.autotranslate": {
"mode": "suggest",
"filter_type": "todo",
"auto_source": "mt",
"component": "",
"engines": ["weblate-translation-memory"],
"threshold": "80",
},
}
Ayrıca bakınız
DEFAULT_COMMITER_EMAIL
2.4 sürümünde geldi.
Committer e-mail address defaulting to noreply@weblate.org
.
Ayrıca bakınız
DEFAULT_COMMITER_NAME
2.4 sürümünde geldi.
Committer name defaulting to Weblate
.
Ayrıca bakınız
DEFAULT_LANGUAGE
4.3.2 sürümünde geldi.
Default source language to use for example in Kaynak dil.
Defaults to en. The matching language object needs to exist in the database.
Ayrıca bakınız
DEFAULT_MERGE_STYLE
3.4 sürümünde geldi.
Merge style for any new components.
rebase - default
merge
Ayrıca bakınız
DEFAULT_TRANSLATION_PROPAGATION
2.5 sürümünde geldi.
Default setting for translation propagation, defaults to True
.
Ayrıca bakınız
DEFAULT_PULL_MESSAGE
Title for new pull requests,
defaulting to 'Update from Weblate'
.
ENABLE_AVATARS
Whether to turn on Gravatar-based avatars for users. By default this is on.
Avatars are fetched and cached on the server, lowering the risk of leaking private info, speeding up the user experience.
Ayrıca bakınız
ENABLE_HOOKS
Whether to enable anonymous remote hooks.
Ayrıca bakınız
ENABLE_HTTPS
Whether to send links to Weblate as HTTPS or HTTP. This setting affects sent e-mails and generated absolute URLs.
In the default configuration this is also used for several Django settings related to HTTPS - it enables secure cookies, toggles HSTS or enables redirection to HTTPS URL.
The HTTPS redirection might be problematic in some cases and you might hit
issue with infinite redirection in case you are using a reverse proxy doing SSL
termination which does not correctly pass protocol headers to Django. Please
tweak your reverse proxy configuration to emit X-Forwarded-Proto
or
Forwarded
headers or configure SECURE_PROXY_SSL_HEADER
to
let Django correctly detect the SSL status.
ENABLE_SHARING
Turn on/off the Share menu so users can share translation progress on social networks.
GET_HELP_URL
4.5.2 sürümünde geldi.
URL where support for your Weblate instance can be found.
GITLAB_CREDENTIALS
4.3 sürümünde geldi.
List for credentials for GitLab servers.
İpucu
Use this in case you want Weblate to interact with more of them, for single
GitLab endpoint stick with GITLAB_USERNAME
and GITLAB_TOKEN
.
GITLAB_CREDENTIALS = {
"gitlab.com": {
"username": "weblate",
"token": "your-api-token",
},
"gitlab.example.com": {
"username": "weblate",
"token": "another-api-token",
},
}
GITLAB_USERNAME
GitLab username used to send merge requests for translation updates.
Ayrıca bakınız
GITLAB_TOKEN
4.3 sürümünde geldi.
Çeviri güncellemeleri için API çağrıları yapmak üzere kullanılan GitLab kişisel erişim belirteci.
Ayrıca bakınız
GITHUB_CREDENTIALS
4.3 sürümünde geldi.
List for credentials for GitHub servers.
İpucu
Use this in case you want Weblate to interact with more of them, for single
GitHub endpoint stick with GITHUB_USERNAME
and GITHUB_TOKEN
.
GITHUB_CREDENTIALS = {
"api.github.com": {
"username": "weblate",
"token": "your-api-token",
},
"github.example.com": {
"username": "weblate",
"token": "another-api-token",
},
}
GITHUB_USERNAME
GitHub username used to send pull requests for translation updates.
Ayrıca bakınız
GITHUB_TOKEN
4.3 sürümünde geldi.
GitHub personal access token used to make API calls to send pull requests for translation updates.
Ayrıca bakınız
GITHUB_CREDENTIALS
,
GitHub,
Creating a GitHub personal access token
GOOGLE_ANALYTICS_ID
Google Analytics ID to turn on monitoring of Weblate using Google Analytics.
HIDE_REPO_CREDENTIALS
Hide repository credentials from the web interface. In case you have repository URL with user and password, Weblate will hide it when related info is shown to users.
For example instead of https://user:password@git.example.com/repo.git
it
will show just https://git.example.com/repo.git
. It tries to clean up VCS
error messages too in a similar manner.
Not
This is turned on by default.
HIDE_VERSION
4.3.1 sürümünde geldi.
Hides version information from unauthenticated users. This also makes all documentation links point to latest version instead of the documentation matching currently installed version.
Hiding version is recommended security practice in some corporations, but it doesn’t prevent attacker to figure out version by probing the behavior.
Not
Bu, varsayılan olarak kapalıdır.
IP_BEHIND_REVERSE_PROXY
2.14 sürümünde geldi.
Indicates whether Weblate is running behind a reverse proxy.
If set to True
, Weblate gets IP address from a header defined by
IP_PROXY_HEADER
.
Uyarı
Ensure you are actually using a reverse proxy and that it sets this header, otherwise users will be able to fake the IP address.
Not
This is not on by default.
Ayrıca bakınız
Running behind reverse proxy,
Rate limiting,
IP_PROXY_HEADER
,
IP_PROXY_OFFSET
IP_PROXY_HEADER
2.14 sürümünde geldi.
Indicates which header Weblate should obtain the IP address from when
IP_BEHIND_REVERSE_PROXY
is turned on.
Defaults to HTTP_X_FORWARDED_FOR
.
IP_PROXY_OFFSET
2.14 sürümünde geldi.
Indicates which part of IP_PROXY_HEADER
is used as client IP
address.
Depending on your setup, this header might consist of several IP addresses,
(for example X-Forwarded-For: a, b, client-ip
) and you can configure
which address from the header is used as client IP address here.
Uyarı
Setting this affects the security of your installation, you should only configure it to use trusted proxies for determining IP address.
Defaults to 0.
LEGAL_URL
3.5 sürümünde geldi.
URL where your Weblate instance shows its legal documents.
İpucu
Useful if you host your legal documents outside Weblate for embedding them inside Weblate, please check Yasal for details.
Example:
LEGAL_URL = "https://weblate.org/terms/"
Ayrıca bakınız
LICENSE_EXTRA
Additional licenses to include in the license choices.
Not
Each license definition should be tuple of its short name, a long name and an URL.
For example:
LICENSE_EXTRA = [
(
"AGPL-3.0",
"GNU Affero General Public License v3.0",
"https://www.gnu.org/licenses/agpl-3.0-standalone.html",
),
]
LICENSE_FILTER
4.3 sürümünde değişti: Setting this to blank value now disables license alert.
Filter list of licenses to show. This also disables the license alert when set to empty.
Not
This filter uses the short license names.
For example:
LICENSE_FILTER = {"AGPL-3.0", "GPL-3.0-or-later"}
Following disables the license alert:
LICENSE_FILTER = set()
Ayrıca bakınız
LICENSE_REQUIRED
Defines whether the license attribute in Component configuration is required.
Not
This is off by default.
LIMIT_TRANSLATION_LENGTH_BY_SOURCE_LENGTH
Whether the length of a given translation should be limited. The restriction is the length of the source string * 10 characters.
İpucu
Set this to False
to allow longer translations (up to 10.000 characters) irrespective of source string length.
Not
Defaults to True
.
LOCALIZE_CDN_URL and LOCALIZE_CDN_PATH
These settings configure the JavaScript yerelleştirme CDN’i addon.
LOCALIZE_CDN_URL
defines root URL where the localization CDN is
available and LOCALIZE_CDN_PATH
defines path where Weblate should
store generated files which will be served at the LOCALIZE_CDN_URL
.
İpucu
On Hosted Weblate, this uses https://weblate-cdn.com/
.
Ayrıca bakınız
LOGIN_REQUIRED_URLS
A list of URLs you want to require logging into. (Besides the standard rules built into Weblate).
İpucu
This allows you to password protect a whole installation using:
LOGIN_REQUIRED_URLS = (r"/(.*)$",)
REST_FRAMEWORK["DEFAULT_PERMISSION_CLASSES"] = [
"rest_framework.permissions.IsAuthenticated"
]
İpucu
It is desirable to lock down API access as well, as shown in the above example.
Ayrıca bakınız
LOGIN_REQUIRED_URLS_EXCEPTIONS
List of exceptions for LOGIN_REQUIRED_URLS
.
If not specified, users are allowed to access the sign in page.
Some of exceptions you might want to include:
LOGIN_REQUIRED_URLS_EXCEPTIONS = (
r"/accounts/(.*)$", # Required for sign in
r"/static/(.*)$", # Required for development mode
r"/widgets/(.*)$", # Allowing public access to widgets
r"/data/(.*)$", # Allowing public access to data exports
r"/hooks/(.*)$", # Allowing public access to notification hooks
r"/api/(.*)$", # Allowing access to API
r"/js/i18n/$", # JavaScript localization
)
MATOMO_SITE_ID
ID of a site in Matomo (formerly Piwik) you want to track.
Not
This integration does not support the Matomo Tag Manager.
Ayrıca bakınız
MATOMO_URL
Full URL (including trailing slash) of a Matomo (formerly Piwik) installation you want to use to track Weblate use. Please check <https://matomo.org/> for more details.
İpucu
This integration does not support the Matomo Tag Manager.
For example:
MATOMO_SITE_ID = 1
MATOMO_URL = "https://example.matomo.cloud/"
Ayrıca bakınız
MT_SERVICES
3.0 sürümünde değişti: The setting was renamed from MACHINE_TRANSLATION_SERVICES
to
MT_SERVICES
to be consistent with other machine translation settings.
List of enabled machine translation services to use.
Not
Many of the services need additional configuration like API keys, please check their documentation Makine çevirisi for more details.
İpucu
When using Docker container, this configuration is automatically generated based on provided API keys, see Machine translation settings.
MT_SERVICES = (
"weblate.machinery.apertium.ApertiumAPYTranslation",
"weblate.machinery.deepl.DeepLTranslation",
"weblate.machinery.glosbe.GlosbeTranslation",
"weblate.machinery.google.GoogleTranslation",
"weblate.machinery.libretranslate.LibreTranslateTranslation",
"weblate.machinery.microsoft.MicrosoftCognitiveTranslation",
"weblate.machinery.microsoftterminology.MicrosoftTerminologyService",
"weblate.machinery.mymemory.MyMemoryTranslation",
"weblate.machinery.tmserver.AmagamaTranslation",
"weblate.machinery.tmserver.TMServerTranslation",
"weblate.machinery.yandex.YandexTranslation",
"weblate.machinery.weblatetm.WeblateTranslation",
"weblate.machinery.saptranslationhub.SAPTranslationHub",
"weblate.memory.machine.WeblateMemory",
)
Ayrıca bakınız
MT_APERTIUM_APY
URL of the Apertium-APy server, https://wiki.apertium.org/wiki/Apertium-apy
Ayrıca bakınız
MT_AWS_ACCESS_KEY_ID
Access key ID for Amazon Translate.
Ayrıca bakınız
MT_AWS_SECRET_ACCESS_KEY
API secret key for Amazon Translate.
Ayrıca bakınız
MT_AWS_REGION
Region name to use for Amazon Translate.
Ayrıca bakınız
MT_BAIDU_ID
Client ID for the Baidu Zhiyun API, you can register at https://api.fanyi.baidu.com/api/trans/product/index
Ayrıca bakınız
Baidu API machine translation, Makine çevirisi, Otomatik öneriler
MT_BAIDU_SECRET
Client secret for the Baidu Zhiyun API, you can register at https://api.fanyi.baidu.com/api/trans/product/index
Ayrıca bakınız
Baidu API machine translation, Makine çevirisi, Otomatik öneriler
MT_DEEPL_API_URL
4.7 sürümünde değişti: The full API URL is now configured to allow using the free plan. Before, it was only possible to
configure the API version using MT_DEEPL_API_VERSION
.
API URL to use with the DeepL service. At the time of writing, there is the v1 API as well as a free and a paid version of the v2 API.
https://api.deepl.com/v2/
(default in Weblate)Is meant for API usage on the paid plan, and the subscription is usage-based.
https://api-free.deepl.com/v2/
Is meant for API usage on the free plan, and the subscription is usage-based.
https://api.deepl.com/v1/
Is meant for CAT tools and is usable with a per-user subscription.
Previously Weblate was classified as a CAT tool by DeepL, so it was supposed to use the v1 API, but now is supposed to use the v2 API. Therefore it defaults to v2, and you can change it to v1 in case you have an existing CAT subscription and want Weblate to use that.
The easiest way to find out which one to use is to open an URL like the following in your browser:
https://api.deepl.com/v2/translate?text=Hello&target_lang=FR&auth_key=XXX
Replace the XXX with your auth_key. If you receive a JSON object which contains “Bonjour”, you have the correct URL; if not, try the other three.
Ayrıca bakınız
MT_DEEPL_KEY
API key for the DeepL API, you can register at https://www.deepl.com/pro.html
Ayrıca bakınız
MT_LIBRETRANSLATE_API_URL
4.7.1 sürümünde geldi.
API URL for the LibreTranslate instance to use.
https://libretranslate.com/
(official public instance)Requires an API key to use outside of the website.
Mirrors are documented on the LibreTranslate GitHub repository, some of which can be used without authentication:
https://github.com/LibreTranslate/LibreTranslate#user-content-mirrors
Ayrıca bakınız
MT_LIBRETRANSLATE_KEY
4.7.1 sürümünde geldi.
API key for the LibreTranslate instance specified in MT_LIBRETRANSLATE_API_URL.
Ayrıca bakınız
MT_GOOGLE_KEY
API key for Google Translate API v2, you can register at https://cloud.google.com/translate/docs
Ayrıca bakınız
MT_GOOGLE_CREDENTIALS
API v3 JSON credentials file obtained in the Google cloud console. Please provide a full OS path. Credentials are per service-account affiliated with certain project. Please check https://cloud.google.com/docs/authentication/getting-started for more details.
MT_GOOGLE_PROJECT
Google Cloud API v3 project id with activated translation service and billing activated. Please check https://cloud.google.com/appengine/docs/standard/nodejs/building-app/creating-project for more details
MT_GOOGLE_LOCATION
API v3 Google Cloud App Engine may be specific to a location.
Change accordingly if the default global
fallback does not work for you.
Please check https://cloud.google.com/appengine/docs/locations for more details
Ayrıca bakınız
MT_MICROSOFT_BASE_URL
Region base URL domain as defined in the “Base URLs” section.
Defaults to api.cognitive.microsofttranslator.com
for Azure Global.
For Azure China, please use api.translator.azure.cn
.
MT_MICROSOFT_COGNITIVE_KEY
Client key for the Microsoft Cognitive Services Translator API.
MT_MICROSOFT_REGION
Region prefix as defined in the “Authenticating with a Multi-service resource” section.
MT_MICROSOFT_ENDPOINT_URL
Region endpoint URL domain for access token as defined in the “Authenticating with an access token” section.
Defaults to api.cognitive.microsoft.com
for Azure Global.
For Azure China, please use your endpoint from the Azure Portal.
MT_MODERNMT_KEY
ModernMT makine çeviri motoru için API anahtarı.
Ayrıca bakınız
MT_MODERNMT_URL
URL of ModernMT. It defaults to https://api.modernmt.com/
for the cloud
service.
Ayrıca bakınız
MT_MYMEMORY_EMAIL
MyMemory identification e-mail address. It permits 1000 requests per day.
Ayrıca bakınız
MyMemory, Makine çevirisi, Otomatik öneriler, MyMemory: API technical specifications
MT_MYMEMORY_KEY
MyMemory access key for private translation memory, use it with MT_MYMEMORY_USER
.
Ayrıca bakınız
MyMemory, Makine çevirisi, Otomatik öneriler, MyMemory: API key generator
MT_MYMEMORY_USER
MyMemory user ID for private translation memory, use it with MT_MYMEMORY_KEY
.
Ayrıca bakınız
MyMemory, Makine çevirisi, Otomatik öneriler, MyMemory: API key generator
MT_NETEASE_KEY
App key for NetEase Sight API, you can register at https://sight.youdao.com/
Ayrıca bakınız
NetEase Sight API machine translation, Makine çevirisi, Otomatik öneriler
MT_NETEASE_SECRET
App secret for the NetEase Sight API, you can register at https://sight.youdao.com/
Ayrıca bakınız
NetEase Sight API machine translation, Makine çevirisi, Otomatik öneriler
MT_TMSERVER
URL where tmserver is running.
Ayrıca bakınız
MT_YANDEX_KEY
API key for the Yandex Translate API, you can register at https://yandex.com/dev/translate/
Ayrıca bakınız
MT_YOUDAO_ID
Client ID for the Youdao Zhiyun API, you can register at https://ai.youdao.com/product-fanyi-text.s.
Ayrıca bakınız
Youdao Zhiyun API machine translation, Makine çevirisi, Otomatik öneriler
MT_YOUDAO_SECRET
Client secret for the Youdao Zhiyun API, you can register at https://ai.youdao.com/product-fanyi-text.s.
Ayrıca bakınız
Youdao Zhiyun API machine translation, Makine çevirisi, Otomatik öneriler
MT_SAP_BASE_URL
API URL to the SAP Translation Hub service.
Ayrıca bakınız
MT_SAP_SANDBOX_APIKEY
API key for sandbox API usage
Ayrıca bakınız
MT_SAP_USERNAME
Your SAP username
Ayrıca bakınız
MT_SAP_PASSWORD
Your SAP password
Ayrıca bakınız
MT_SAP_USE_MT
Whether to also use machine translation services, in addition to the term database.
Possible values: True
or False
Ayrıca bakınız
NEARBY_MESSAGES
How many strings to show around the currently translated string. This is just a default value, users can adjust this in Kullanıcı profili.
DEFAULT_PAGE_LIMIT
4.7 sürümünde geldi.
Default number of elements to display when pagination is active.
PAGURE_CREDENTIALS
4.3.2 sürümünde geldi.
List for credentials for Pagure servers.
İpucu
Use this in case you want Weblate to interact with more of them, for single
Pagure endpoint stick with PAGURE_USERNAME
and PAGURE_TOKEN
.
PAGURE_CREDENTIALS = {
"pagure.io": {
"username": "weblate",
"token": "your-api-token",
},
"pagure.example.com": {
"username": "weblate",
"token": "another-api-token",
},
}
PAGURE_USERNAME
4.3.2 sürümünde geldi.
Çeviri güncellemeleri için birleştirme istekleri gönderirken kullanılacak Pagure kullanıcı adı.
Ayrıca bakınız
PAGURE_TOKEN
4.3.2 sürümünde geldi.
Çeviri güncellemeleri için API çağrıları yaparken kullanılacak Pagure kişisel erişim belirteci.
Ayrıca bakınız
PRIVACY_URL
4.8.1 sürümünde geldi.
URL where your Weblate instance shows its privacy policy.
İpucu
Useful if you host your legal documents outside Weblate for embedding them inside Weblate, please check Yasal for details.
Example:
PRIVACY_URL = "https://weblate.org/terms/"
Ayrıca bakınız
RATELIMIT_ATTEMPTS
3.2 sürümünde geldi.
Maximum number of authentication attempts before rate limiting is applied.
Defaults to 5.
Ayrıca bakınız
RATELIMIT_WINDOW
3.2 sürümünde geldi.
How long authentication is accepted after rate limiting applies.
An amount of seconds defaulting to 300 (5 minutes).
Ayrıca bakınız
RATELIMIT_LOCKOUT
3.2 sürümünde geldi.
How long authentication is locked after rate limiting applies.
An amount of seconds defaulting to 600 (10 minutes).
Ayrıca bakınız
REGISTRATION_ALLOW_BACKENDS
4.1 sürümünde geldi.
List of authentication backends to allow registration from. This only limits new registrations, users can still authenticate and add authentication using all configured authentication backends.
It is recommended to keep REGISTRATION_OPEN
enabled while limiting
registration backends, otherwise users will be able to register, but Weblate
will not show links to register in the user interface.
Example:
REGISTRATION_ALLOW_BACKENDS = ["azuread-oauth2", "azuread-tenant-oauth2"]
İpucu
The backend names match names used in URL for authentication.
Ayrıca bakınız
REGISTRATION_CAPTCHA
A value of either True
or False
indicating whether registration of new
accounts is protected by CAPTCHA. This setting is optional, and a default of
True
will be assumed if it is not supplied.
If turned on, a CAPTCHA is added to all pages where a users enters their e-mail address:
New account registration.
Password recovery.
Adding e-mail to an account.
Contact form for users that are not signed in.
REGISTRATION_EMAIL_MATCH
2.17 sürümünde geldi.
Allows you to filter which e-mail addresses can register.
Defaults to .*
, which allows any e-mail address to be registered.
You can use it to restrict registration to a single e-mail domain:
REGISTRATION_EMAIL_MATCH = r"^.*@weblate\.org$"
REGISTRATION_OPEN
Whether registration of new accounts is currently permitted.
This optional setting can remain the default True
, or changed to False
.
This setting affects built-in authentication by e-mail address or through the
Python Social Auth (you can whitelist certain back-ends using
REGISTRATION_ALLOW_BACKENDS
).
Not
If using third-party authentication methods such as LDAP authentication, it just hides the registration form, but new users might still be able to sign in and create accounts.
Ayrıca bakınız
REGISTRATION_ALLOW_BACKENDS
,
REGISTRATION_EMAIL_MATCH
,
Kimlik doğrulama
REPOSITORY_ALERT_THRESHOLD
4.0.2 sürümünde geldi.
Threshold for triggering an alert for outdated repositories, or ones that contain too many changes. Defaults to 25.
Ayrıca bakınız
REQUIRE_LOGIN
4.1 sürümünde geldi.
This enables LOGIN_REQUIRED_URLS
and configures REST framework to
require authentication for all API endpoints.
Not
This is implemented in the Sample configuration. For Docker, use
WEBLATE_REQUIRE_LOGIN
.
SENTRY_DSN
3.9 sürümünde geldi.
Sentry DSN to use for Collecting error reports.
Ayrıca bakınız
SIMPLIFY_LANGUAGES
Use simple language codes for default language/country combinations. For
example an fr_FR
translation will use the fr
language code. This is usually
the desired behavior, as it simplifies listing languages for these default
combinations.
Turn this off if you want to different translations for each variant.
SITE_DOMAIN
Configures site domain. This is necessary to produce correct absolute links in many scopes (for example activation e-mails, notifications or RSS feeds).
In case Weblate is running on non-standard port, include it here as well.
Examples:
# Production site with domain name
SITE_DOMAIN = "weblate.example.com"
# Local development with IP address and port
SITE_DOMAIN = "127.0.0.1:8000"
Not
This setting should only contain the domain name. For configuring protocol,
(enabling and enforcing HTTPS) use ENABLE_HTTPS
and for changing
URL, use URL_PREFIX
.
İpucu
On a Docker container, the site domain is configured through
WEBLATE_ALLOWED_HOSTS
.
SITE_TITLE
Site title to be used for the website and sent e-mails.
SPECIAL_CHARS
Additional characters to include in the visual keyboard, Visual keyboard.
The default value is:
SPECIAL_CHARS = ("\t", "\n", "\u00a0", "…")
SINGLE_PROJECT
3.8 sürümünde geldi.
Redirects users directly to a project or component instead of showing
the dashboard. You can either set it to True
and in this case it only works in
case there is actually only single project in Weblate. Alternatively set
the project slug, and it will redirect unconditionally to this project.
3.11 sürümünde değişti: The setting now also accepts a project slug, to force displaying that single project.
Example:
SINGLE_PROJECT = "test"
SSH_EXTRA_ARGS
4.9 sürümünde geldi.
Allows to add custom parameters when Weblate is invoking SSH. This is useful when connecting to servers using legacy encryption or other non-standard features.
For example when SSH connection in Weblate fails with Unable to negotiate with legacyhost: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1, you can enable that using:
SSH_EXTRA_ARGS = "-oKexAlgorithms=+diffie-hellman-group1-sha1"
İpucu
The string is evaluated by shell, so make sure to quote any whitespace and special characters.
Ayrıca bakınız
STATUS_URL
The URL where your Weblate instance reports its status.
SUGGESTION_CLEANUP_DAYS
3.2.1 sürümünde geldi.
Automatically deletes suggestions after a given number of days.
Defaults to None
, meaning no deletions.
UPDATE_LANGUAGES
4.3.2 sürümünde geldi.
Controls whether languages database should be updated when running database
migration and is enabled by default. This setting has no effect on invocation
of setuplang
.
Ayrıca bakınız
URL_PREFIX
This setting allows you to run Weblate under some path (otherwise it relies on being run from the webserver root).
Not
To use this setting, you also need to configure your server to strip this prefix.
For example with WSGI, this can be achieved by setting WSGIScriptAlias
.
İpucu
The prefix should start with a /
.
Example:
URL_PREFIX = "/translations"
Not
This setting does not work with Django’s built-in server, you would have to
adjust urls.py
to contain this prefix.
VCS_BACKENDS
Configuration of available VCS backends.
Not
Weblate tries to use all supported back-ends you have the tools for.
İpucu
You can limit choices or add custom VCS back-ends by using this.
VCS_BACKENDS = ("weblate.vcs.git.GitRepository",)
Ayrıca bakınız
VCS_CLONE_DEPTH
3.10.2 sürümünde geldi.
Configures how deep cloning of repositories Weblate should do.
Not
Currently this is only supported in Git. By default Weblate does shallow clones of the repositories to make cloning faster and save disk space. Depending on your usage (for example when using custom Eklentiler), you might want to increase the depth or turn off shallow clones completely by setting this to 0.
İpucu
In case you get fatal: protocol error: expected old/new/ref, got 'shallow
<commit hash>'
error when pushing from Weblate, turn off shallow clones completely by setting:
VCS_CLONE_DEPTH = 0
WEBLATE_ADDONS
List of addons available for use. To use them, they have to be enabled for a given translation component. By default this includes all built-in addons, when extending the list you will probably want to keep existing ones enabled, for example:
WEBLATE_ADDONS = (
# Built-in addons
"weblate.addons.gettext.GenerateMoAddon",
"weblate.addons.gettext.UpdateLinguasAddon",
"weblate.addons.gettext.UpdateConfigureAddon",
"weblate.addons.gettext.MsgmergeAddon",
"weblate.addons.gettext.GettextCustomizeAddon",
"weblate.addons.gettext.GettextAuthorComments",
"weblate.addons.cleanup.CleanupAddon",
"weblate.addons.consistency.LangaugeConsistencyAddon",
"weblate.addons.discovery.DiscoveryAddon",
"weblate.addons.flags.SourceEditAddon",
"weblate.addons.flags.TargetEditAddon",
"weblate.addons.flags.SameEditAddon",
"weblate.addons.flags.BulkEditAddon",
"weblate.addons.generate.GenerateFileAddon",
"weblate.addons.json.JSONCustomizeAddon",
"weblate.addons.properties.PropertiesSortAddon",
"weblate.addons.git.GitSquashAddon",
"weblate.addons.removal.RemoveComments",
"weblate.addons.removal.RemoveSuggestions",
"weblate.addons.resx.ResxUpdateAddon",
"weblate.addons.autotranslate.AutoTranslateAddon",
"weblate.addons.yaml.YAMLCustomizeAddon",
"weblate.addons.cdn.CDNJSAddon",
# Add-on you want to include
"weblate.addons.example.ExampleAddon",
)
Not
Removing the addon from the list does not uninstall it from the components. Weblate will crash in that case. Please uninstall addon from all components prior to removing it from this list.
Ayrıca bakınız
WEBLATE_EXPORTERS
4.2 sürümünde geldi.
List of a available exporters offering downloading translations or glossaries in various file formats.
Ayrıca bakınız
WEBLATE_FORMATS
3.0 sürümünde geldi.
List of file formats available for use.
Not
The default list already has the common formats.
Ayrıca bakınız
WEBLATE_GPG_IDENTITY
3.1 sürümünde geldi.
Identity used by Weblate to sign Git commits, for example:
WEBLATE_GPG_IDENTITY = "Weblate <weblate@example.com>"
The Weblate GPG keyring is searched for a matching key (home/.gnupg
under
DATA_DIR
). If not found, a key is generated, please check
Signing Git commits with GnuPG for more details.
Ayrıca bakınız
WEBSITE_REQUIRED
Defines whether Proje web sitesi has to be specified when creating a project. Turned on by default as that suits public server setups.
COMMENT_CLEANUP_DAYS
3.6 sürümünde geldi.
Delete comments after a given number of days. Defaults to
None
, meaning no deletion at all.