From 0f89923d2d1af9cb9879e05b23f32c5329bcfe0e Mon Sep 17 00:00:00 2001 From: Agathe Porte Date: Mon, 20 Jul 2026 18:11:15 +0000 Subject: [PATCH] doc: websites: explain global aliases required (#1494) Add a note explaining that a globally aliased bucket is required for successfully exposing it as a website. Reviewed-on: https://git.deuxfleurs.fr/Deuxfleurs/garage/pulls/1494 --- doc/book/cookbook/exposing-websites.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/book/cookbook/exposing-websites.md b/doc/book/cookbook/exposing-websites.md index 74a5613d..bebb4184 100644 --- a/doc/book/cookbook/exposing-websites.md +++ b/doc/book/cookbook/exposing-websites.md @@ -25,6 +25,13 @@ garage bucket website --allow my-website Now it will be **publicly** exposed on the web endpoint (by default listening on port 3902). +> The bucket needs to have a *global alias* to be exposed as a website. If the +> bucket was created with `garage bucket create` it will have an alias; +> if created via the S3 API [you will have to manually add the alias +> ](https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/742) first. +> Creating globally aliased buckets from the S3 API is [currently under +> discussion](https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/649). + ## How exposed websites work Our website serving logic is as follow: