From eb37ceca51f61e1c32a268e8666dfa23cfe2cc25 Mon Sep 17 00:00:00 2001 From: sysadmin Date: Mon, 16 Mar 2026 16:39:23 -0400 Subject: [PATCH] Actualizar README.md --- README.md | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 02f5e69..c71c4f1 100644 --- a/README.md +++ b/README.md @@ -13,19 +13,13 @@ En un tiempo breve se habilitará una actualización para implementar una versi # Nginx y Let’s Encrypt con Docker Compose -This approach automatically obtains and renews [Let's Encrypt](https://letsencrypt.org/) TLS certificates and set up HTTPS in Nginx for your domain name using Docker Compose. +Este enfoque obtiene y renueva automáticamente los certificados TLS [Let's Encrypt](https://letsencrypt.org/) y configura HTTPS en Nginx para su dominio utilizando docker compose. -The idea is simple. There are 3 containers: +La idea es simple. Hay 3 contenedores que trabajan así: -* Nginx -* Certbot - for obtaining and renewing certificates -* Cron - for triggering certificates renewal once a day - -The sequence of actions: - -* Nginx generates self-signed "dummy" certificates to pass ACME challenge for obtaining Let's Encrypt certificates -* Certbot waits for Nginx to become ready and obtains certificates -* Cron triggers Certbot to try to renew certificates and Nginx to reload configuration on a daily basis +* Nginx, generates self-signed "dummy" certificates to pass ACME challenge for obtaining Let's Encrypt certificates +* Certbot - for obtaining and renewing certificates, waits for Nginx to become ready and obtains certificates +* Cron - for triggering certificates renewal once a day, triggers Certbot to try to renew certificates and Nginx to reload configuration on a daily basis * The Nginx container uses updates symbolic links that point to either "dummy" certificates or Let's Encrypt certificates.