 The Weblate Manual 4.3.1UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 664 页 | 9.34 MB | 1 年前3 The Weblate Manual 4.3.1UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 664 页 | 9.34 MB | 1 年前3
 The Weblate Manual 4.1.1and setting there LANG="C.UTF-8". Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Running server You will need several services to run Weblate, the recommended setup consists0 码力 | 602 页 | 9.26 MB | 1 年前3 The Weblate Manual 4.1.1and setting there LANG="C.UTF-8". Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Running server You will need several services to run Weblate, the recommended setup consists0 码力 | 602 页 | 9.26 MB | 1 年前3
 The Weblate Manual 4.2.1UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 639 页 | 9.32 MB | 1 年前3 The Weblate Manual 4.2.1UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 639 页 | 9.32 MB | 1 年前3
 The Weblate Manual 4.1.1deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Additionally, Weblate container will now accept ports: - 80:8080 - 443:4443 Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 401 页 | 3.86 MB | 1 年前3 The Weblate Manual 4.1.1deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Additionally, Weblate container will now accept ports: - 80:8080 - 443:4443 Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 401 页 | 3.86 MB | 1 年前3
 The Weblate Manual 4.2.2deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 414 页 | 3.96 MB | 1 年前3 The Weblate Manual 4.2.2deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 414 页 | 3.96 MB | 1 年前3
 The Weblate Manual 4.2.2UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 639 页 | 9.32 MB | 1 年前3 The Weblate Manual 4.2.2UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 639 页 | 9.32 MB | 1 年前3
 The Weblate Manual 4.2deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 413 页 | 3.95 MB | 1 年前3 The Weblate Manual 4.2deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 413 页 | 3.95 MB | 1 年前3
 The Weblate Manual 4.2UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 637 页 | 9.32 MB | 1 年前3 The Weblate Manual 4.2UTF-8' export LC_ALL='en_US.UTF-8' Using custom certificate authority Weblate does verify SSL certificates during HTTP requests. In case you are using custom certificate authority which is not trusted debian this can be done by placing the CA certificate into /usr/local/share/ca-certificates/ and running update-ca-certificates). Once this is done, system tools will trust the certificate and this includes (the path is Debian specific): import os os.environ["REQUESTS_CA_BUNDLE"] = "/etc/ssl/certs/ca- certificates.crt" Compressing client assets Weblate comes with a bunch of JavaScript and CSS files. For performance0 码力 | 637 页 | 9.32 MB | 1 年前3
 The Weblate Manual 4.2.1deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 414 页 | 3.96 MB | 1 年前3 The Weblate Manual 4.2.1deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 414 页 | 3.96 MB | 1 年前3
 The Weblate Manual 4.3deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 424 页 | 3.98 MB | 1 年前3 The Weblate Manual 4.3deployment instructions, this section only mentions differences compared to it. Using own SSL certificates New in version 3.8-3. In case you have own SSL certificate you want to use, simply place the Docker container volumes): • ssl/fullchain.pem containing the certificate including any needed CA certificates • ssl/privkey.pem containing the private key Both of these files must be owned by the same user values from your environment. Automatic SSL certificates using Let’s Encrypt In case you want to use Let’s Encrypt automatically generated SSL certificates on public installation, you need to add a reverse0 码力 | 424 页 | 3.98 MB | 1 年前3
共 217 条
- 1
- 2
- 3
- 4
- 5
- 6
- 22














