From d40514b36825444e466ae84b2eeab8fccf96f658 Mon Sep 17 00:00:00 2001
From: "dobby-yivi-agent[bot]"
 <275734547+dobby-yivi-agent[bot]@users.noreply.github.com>
Date: Tue, 26 May 2026 23:40:31 +0000
Subject: [PATCH] docs(README): correct deploy claim; CI builds and pushes the
 image only

The Releasing section claimed the site is deployed automatically. CI
only builds and pushes ghcr.io/encryption4all/postguard-docs:edge;
the NGINX container on the production host still has to pull the new
tag and restart out of band. Mirrors the wording already in
docs/repos/postguard-outlook-addon.md.

Closes #109
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 78f0045..18169d8 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,7 @@ npm run docs:preview   # preview the built site
 
 ## Releasing
 
-The site is deployed automatically via GitHub Actions. Pushing to `main` triggers a Docker image build (NGINX-based static hosting) which is deployed to production.
+Pushing to `main` triggers `.github/workflows/ci.yml`, which builds and pushes the Docker image to `ghcr.io/encryption4all/postguard-docs:edge`. There is no automatic deploy step. The host running production at `docs.postguard.eu` (an NGINX container serving the built `docs/.vitepress/dist`) has to pull the new `edge` tag and restart the container to pick up changes.
 
 ## License