- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 21 for certificates (0.18 sec)
-
docs/en/docs/deployment/https.md
The domains are securely verified and the certificates are generated automatically. This also allows automating the renewal of these certificates.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 12K bytes - Viewed (0) -
docs/en/docs/deployment/concepts.md
And there has to be something in charge of **renewing the HTTPS certificates**, it could be the same component or it could be something different. ### Example Tools for HTTPS Some of the tools you could use as a TLS Termination Proxy are: * Traefik * Automatically handles certificates renewals ✨ * Caddy * Automatically handles certificates renewals ✨ * Nginx
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 18K bytes - Viewed (0) -
docs/en/docs/project-generation.md
- 📞 [Traefik](https://traefik.io) as a reverse proxy / load balancer. - 🚢 Deployment instructions using Docker Compose, including how to set up a frontend Traefik proxy to handle automatic HTTPS certificates.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Mar 21 21:12:21 GMT 2024 - 1.8K bytes - Viewed (0) -
docs/pt/docs/deployment/https.md
Antes de Let's Encrypt, esses certificados HTTPS eram vendidos por terceiros confiáveis. O processo de aquisição de um desses certificados costumava ser complicado, exigia bastante papelada e os certificados eram bastante caros. Mas então <a href="https://letsencrypt.org/" class="external-link" target="_blank">Let's Encrypt</a> foi criado.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Oct 05 10:40:05 GMT 2021 - 3.9K bytes - Viewed (0) -
docs/fr/docs/deployment/docker.md
Il est intégré à Let's Encrypt. Ainsi, il peut gérer toutes les parties HTTPS, y compris l'acquisition et le renouvellement des certificats. Il est également intégré à Docker. Ainsi, vous pouvez déclarer vos domaines dans les configurations de chaque application et faire en sorte qu'elles lisent ces configurations, génèrent les certificats HTTPS et servent via HTTPS à votre application automatiquement, sans nécessiter aucune modification de leurs configurations.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 12 00:06:16 GMT 2022 - 7.5K bytes - Viewed (0) -
docs/pt/docs/project-generation.md
* Balanceamento de carga entre _frontend_ e _backend_ com **Traefik**, então você pode ter ambos sob o mesmo domínio, separados por rota, mas servidos por diferentes containers. * Integração Traefik, incluindo geração automática de certificados **HTTPS** Let's Encrypt. * GitLab **CI** (integração contínua), incluindo testes _frontend_ e _backend_. ## Full Stack FastAPI Couchbase
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Oct 17 05:50:32 GMT 2020 - 6.3K bytes - Viewed (0) -
docs/fr/docs/project-generation.md
* Intégration Traefik, comprenant la génération automatique de certificat **HTTPS** Let's Encrypt. * GitLab **CI** (intégration continue), comprenant des tests pour le frontend et le backend. ## Full Stack FastAPI Couchbase
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Jul 02 14:18:06 GMT 2021 - 6.7K bytes - Viewed (0) -
docs/pt/docs/deployment.md
Agora, pela perspectiva de um desenvolvedor, aqui estão algumas coisas para se ter em mente enquanto se pensa sobre HTTPS: * Para HTTPS, o servidor precisa ter "certificados" gerados por terceiros. * Esses certificados são na verdade adquiridos por terceiros, não "gerados". * Certificados tem um prazo de uso. * Eles expiram. * E então eles precisam ser renovados, adquiridos novamente por terceiros.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Aug 18 16:16:54 GMT 2022 - 16.8K bytes - Viewed (0) -
docs/zh/docs/deployment/https.md
要从用户的视角**了解 HTTPS 的基础知识**,请查看 <a href="https://howhttps.works/" class="external-link" target="_blank">https://howhttps.works/</a>。 现在,从**开发人员的视角**,在了解 HTTPS 时需要记住以下几点: * 要使用 HTTPS,**服务器**需要拥有由**第三方**生成的**"证书(certificate)"**。 * 这些证书实际上是从第三方**获取**的,而不是“生成”的。 * 证书有**生命周期**。 * 它们会**过期**。 * 然后它们需要**更新**,**再次从第三方获取**。 * 连接的加密发生在 **TCP 层**。 * 这是 HTTP 协议**下面的一层**。 * 因此,**证书和加密**处理是在 **HTTP之前**完成的。
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 09 15:38:25 GMT 2024 - 10.6K bytes - Viewed (0) -
docs/en/docs/img/deployment/https/https03.drawio
<mxGeometry x="510" y="400" width="310" height="320" as="geometry"/> </mxCell> <mxCell id="50" value="<font style="font-size: 24px" face="Roboto">HTTPS certificates<br></font>" style="text;html=1;strokeColor=none;fillColor=none;align=center;verticalAlign=middle;whiteSpace=wrap;rounded=0;strokeWidth=3;fontFamily=Roboto Mono, mono;FType=g;" parent="1" vertex="1">
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 12 00:06:16 GMT 2022 - 12.3K bytes - Viewed (0)