Add make server-up for production stack with Caddy

Replaces the complicated `docker compose --profile server -p neowiki-neowiki
--project-directory Docker up -d` invocation in Docker/README.md. The explicit
project name was needed so that subsequent `make install-db` etc. would attach
to the same containers; wrapping it in a target keeps the project-name
plumbing out of the docs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: malberts

Docker/README.md

@@ -40,10 +40,8 @@ To deploy on a server with automatic HTTPS via Caddy:
 
 2. From the extension root, bring up the stack including Caddy:
    ```bash
-   docker compose --profile server -p neowiki-neowiki --project-directory Docker up -d
+   make server-up
    ```
-   (Or equivalently `cd Docker && docker compose --profile server up -d` if you do
-   not need the make-driven project name.)
 
 3. Run the install/load steps from the try-it-out section above.
 

Makefile

@@ -49,11 +49,14 @@ help:
 
 # ---- Lifecycle (host only) ---------------------------------------------------
 
-.PHONY: up dev dev-tools _dev-tools-impl stop down logs ps bash
+.PHONY: up server-up dev dev-tools _dev-tools-impl stop down logs ps bash
 
 up: ## Bring up try-it-out stack (no profile, prebuilt image)
 	$(DC) up -d
 
+server-up: ## Bring up production stack including Caddy (HTTPS on 80/443)
+	$(DC) --profile server up -d
+
 dev: bootstrap ensure-port ## Bring up dev stack (build image, install, seed, wait for health)
 	@$(MAKE) --no-print-directory _dev-impl