Update docs

This commit is contained in:
Alan Grainger
2026-10-08 21:09:29 +13:00
parent ac83705fd7
commit 360c46fbc8
2 changed files with 14 additions and 1 deletions
+2 -1
View File
@@ -68,6 +68,7 @@ The upload service follows the same rules as IPP in every other way. It needs no
uploads with the visitor's share key, so Immich itself checks the share's "Allow public user to upload" option on
every file. It never shows anything from your library, and it streams each file to Immich without storing it.
The setup is in [Let visitors send photos back](/visitor-uploads).
The setup is in [Let visitors send photos back](/visitor-uploads), which also explains
[why uploading is a separate container](/visitor-uploads#why-is-uploading-a-separate-container).
Ready to set it up? Head to [Installation](/installation).
+12
View File
@@ -277,6 +277,18 @@ Immich keeps the one copy and adds it to the share. The visitor's list shows the
No. The upload page shows nothing from the share, only the visitor's own uploads in progress, and nothing can be
deleted or edited from it. The owner manages uploads in Immich.
### Why is uploading a separate container
Three reasons, in order of importance:
- **IPP stays read-only.** The gallery container has no code that accepts a file or writes to Immich. If you do not
run the upload service, nothing in IPP can write to your library, and that holds no matter what a visitor sends.
- **A problem with uploads cannot take down the gallery.** A visitor who floods the upload service with files or
connections can exhaust that container, and the gallery keeps serving from its own.
- **You can treat the two differently.** Viewing and uploading can run on separate domains or separate servers,
with different rate limits, geoblocks or access rules in your reverse proxy. A single container would still let
you split by path, but not to the same degree.
### Why does the rate limit count all visitors together
Behind a reverse proxy every visitor reaches the upload service from the proxy's address, so