org /…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS configuration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note The proxy configuration needs to be done under user running Weblate (see also different environments). HTTP proxy Weblate does execute VCS commands and those accept proxy configuration from environment. The recommended approach is to define proxy settings in settings.py: import

org /…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS configuration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note The proxy configuration needs to be done under user running Weblate (see also different environments). HTTP proxy Weblate does execute VCS commands and those accept proxy configuration from environment. The recommended approach is to define proxy settings in settings.py: import

org /…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS configuration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note The proxy configuration needs to be done under user running Weblate (see also different environments). HTTP proxy Weblate does execute VCS commands and those accept proxy configuration from environment. The recommended approach is to define proxy settings in settings.py: import

org /…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS configuration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note The proxy configuration needs to be done under user running Weblate (see also different environments). HTTP proxy Weblate does execute VCS commands and those accept proxy configuration from environment. The recommended approach is to define proxy settings in settings.py: import

org /…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS configuration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note The proxy configuration needs to be done under user running Weblate (see also different environments). HTTP proxy Weblate does execute VCS commands and those accept proxy configuration from environment. The recommended approach is to define proxy settings in settings.py: import

org/…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS config- uration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note: The proxy configuration needs to be done under user running Weblate (see also automatically generated SSL certificates on public installation, you need to add a reverse HTTPS proxy an additional Docker container, https-portal will be used for that. This is made use of in the docker-compose-https

org/…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS configuration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note: The proxy configuration needs to be done under user running Weblate (see also automatically generated SSL certificates on public installation, you need to add a reverse HTTPS proxy an additional Docker container, https-portal will be used for that. This is made use of in the docker-compose-https

org/…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS config- uration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note: The proxy configuration needs to be done under user running Weblate (see also automatically generated SSL certificates on public installation, you need to add a reverse HTTPS proxy an additional Docker container, https-portal will be used for that. This is made use of in the docker-compose-https

org/…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS config- uration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note: The proxy configuration needs to be done under user running Weblate (see also automatically generated SSL certificates on public installation, you need to add a reverse HTTPS proxy an additional Docker container, https-portal will be used for that. This is made use of in the docker-compose-https

org/…`. Using proxy If you need to access HTTP/HTTPS VCS repositories using a proxy server, configure the VCS to use it. This can be done using the http_proxy, https_proxy, and all_proxy environment variables it in the VCS config- uration, for example: git config --global http.proxy http://user:password@proxy.example.com:80 Note: The proxy configuration needs to be done under user running Weblate (see also automatically generated SSL certificates on public installation, you need to add a reverse HTTPS proxy an additional Docker container, https-portal will be used for that. This is made use of in the docker-compose-https