Added Docker Compose optimizations

README.md

@@ -41,6 +41,14 @@ Copy-Item .env.example .env
 docker compose up -d --build
 ```
 
+To attach the calendar app to an existing reverse-proxy Docker network, copy `compose.override.yaml.example` to `compose.override.yaml` on the server and set `PROXY_NETWORK` in `.env` to that network’s name. Compose automatically merges the local override file. The network must already exist; Apprise stays on the private Compose network while the calendar app joins both networks.
+
+```powershell
+Copy-Item compose.override.yaml.example compose.override.yaml
+# Set PROXY_NETWORK in .env to your existing network's name.
+docker compose up -d --build
+```
+
 The calendar service listens on port `3000`; set `HOST_PORT` in the shell or Compose `.env` file to change the host port. Apprise listens on the private Compose network at `apprise:8000` and is not published directly to the internet. SQLite data is stored in the persistent `event-data` Docker volume. Follow both services with `docker compose logs -f`, stop them with `docker compose down`, and remove the database volume only when you intend to delete the stored events and notification history (`docker compose down -v`).
 
 To build and run without Compose: