The main container now runs quire serve on port 3000, not lighttpd
on 8080. Gitweb is a separate container mounting the repos volume
read-only. Removed the stale note about interim lighttpd.

Assisted-by: GLM-5.1 via pi

diff --git a/docs/host/README.md b/docs/host/README.md
index 00fe1db..aae172f 100644
--- a/docs/host/README.md
+++ b/docs/host/README.md
@@ -33,13 +33,21 @@ Reference configs for dispatching SSH connections into the quire container.
            --user "$(id -u git):$(id -g git)" \
            -e HOME=/tmp \
            -v /var/quire:/var/quire \
-           -p 127.0.0.1:8080:8080 \
+           -p 127.0.0.1:3000:3000 \
            quire
 
    In a compose file, the equivalent is `user: "${QUIRE_UID}:${QUIRE_GID}"`
    with the values templated from `id -u git` / `id -g git` during host
    setup.
 
+   If you want the interim gitweb view, run it as a separate container
+   mounting the same volume (read-only is sufficient):
+
+       docker run -d --name quire-gitweb \
+           -v /var/quire/repos:/var/quire/repos:ro \
+           -p 127.0.0.1:8080:8080 \
+           quire-gitweb
+
 5. Create a test repo inside the container:
 
        docker exec quire-container quire repo new foo.git
@@ -63,9 +71,6 @@ otherwise match a container user. `HOME=/tmp` is set because the host
 uid has no `/etc/passwd` entry inside the container, and git needs a
 writable `HOME` for its config probing.
 
-The HTTP port (8080) is published to host loopback only. A reverse proxy
+The HTTP port (3000) is published to host loopback only. A reverse proxy
 on the host terminates TLS and reverse-proxies to it; nothing else
 should reach it directly.
-
-Currently the container runs lighttpd + gitweb as an interim web view.
-This will be replaced by `quire serve` once the built-in web view is ready.