Dockerized

README.md

@@ -29,6 +29,27 @@ A `.env` file is optional at startup; without one, the server still runs, but no
 
 For production, run `npm run build` followed by `npm start`, and keep the process running with your preferred process manager or service host.
 
+## Docker
+
+Build and start the service with Docker Compose:
+
+```sh
+Copy-Item .env.example .env
+# Edit .env and configure Apprise, ntfy, and Discord settings.
+docker compose up -d --build
+```
+
+The service listens on port `3000`; set `HOST_PORT` in the shell or Compose `.env` file to change the host port. SQLite data is stored in the persistent `event-data` Docker volume. Follow logs with `docker compose logs -f`, stop 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:
+
+```sh
+docker build -t 77th-ev-cal-ntfy-srv .
+docker run -d --name 77th-ev-cal-ntfy-srv --restart unless-stopped \
+  --env-file .env -p 3000:3000 -v event-data:/app/data \
+  77th-ev-cal-ntfy-srv
+```
+
 ## Endpoints
 
 - `GET /health` — service and polling status