extended support for GitHub, Gerrit and Subversion) and ref:vcs- mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With dependencies Weblate supports PostgreSQL, MySQL and MariaDB, see Database setup for Weblate and backends documentation for more details. Other system requirements The following dependencies have to be

extended support for GitHub, Gerrit and Subversion) and ref:vcs- mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With PostgreSQL: DATABASES = { 'default': { # Database engine 'ENGINE': 'django.db.backends.postgresql', # Database name 'NAME': 'weblate', # Database user 'USER':

extended support for GitHub, Gerrit and Subversion) and ref:vcs- mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With PostgreSQL: DATABASES = { 'default': { # Database engine 'ENGINE': 'django.db.backends.postgresql', # Database name 'NAME': 'weblate', # Database user 'USER':

(with extended support for GitHub, Gerrit and Subversion) and Mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With settings.py 片段： DATABASES = { 'default': { # Database engine 'ENGINE': 'django.db.backends.postgresql', # Database name 'NAME': 'weblate', # Database user 'USER':

(with extended support for GitHub, Gerrit and Subversion) and Mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With settings.py 片段： DATABASES = { "default": { # Database engine "ENGINE": "django.db.backends.postgresql", # Database name "NAME": "weblate", # Database user "USER":

(with extended support for GitHub, Gerrit and Subversion) and Mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With settings.py 片段： DATABASES = { "default": { # Database engine "ENGINE": "django.db.backends.postgresql", # Database name "NAME": "weblate", # Database user "USER":

extended support for GitHub, Gerrit and Subversion) and ref:vcs-mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. 1.11.1 Accessing repositories The VCS repository you want to use has to be accessible to Weblate WEBLATE_REGISTRATION_ALLOW_BACKENDS 配置可用于通过REGISTRATION_ALLOW_BACKENDS 创建新帐户的身份验证方法。 示例： environment: WEBLATE_REGISTRATION_OPEN: 0 WEBLATE_REGISTRATION_ALLOW_BACKENDS: azuread-oauth2,azuread-tenant-

extended support for GitHub, Gerrit and Subversion) and ref:vcs-mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. 1.11.1 Accessing repositories The VCS repository you want to use has to be accessible to Weblate WEBLATE_REGISTRATION_ALLOW_BACKENDS 配置可用于通过REGISTRATION_ALLOW_BACKENDS 创建新帐户的身份验证方法。 示例： environment: WEBLATE_REGISTRATION_OPEN: 0 WEBLATE_REGISTRATION_ALLOW_BACKENDS: azuread-oauth2,azuread-tenant-

extended support for GitHub, Gerrit and Subversion) and ref:vcs-mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. 1.11.1 Accessing repositories The VCS repository you want to use has to be accessible to Weblate WEBLATE_REGISTRATION_ALLOW_BACKENDS 配置可用于通过REGISTRATION_ALLOW_BACKENDS 创建新帐户的身份验证方法。 示例： environment: WEBLATE_REGISTRATION_OPEN: 0 WEBLATE_REGISTRATION_ALLOW_BACKENDS: azuread-oauth2,azuread-tenant-

(with extended support for GitHub, Gerrit and Subversion) and Mercurial, but it is possible to write backends for other VCSes. You can also use Git remote helpers in Git to access other VCSes. Weblate also supports Git (with extended support for GitHub, Gerrit and Subversion) and Mercurial as version control backends. Accessing repositories The VCS repository you want to use has to be accessible to Weblate. With settings.py 片段： DATABASES = { "default": { # Database engine "ENGINE": "django.db.backends.postgresql", # Database name "NAME": "weblate", # Database user "USER":