chiko/77thevcalntfysrv
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added Apprise to Docker Compose

Browse Source
This commit is contained in:
chiko committed 2026-10-09 01:30:54 +02:00
1 parent a2814cc327
commit bffc8fbd1a
3 files changed
+26 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

README.md
+2 -2
View File
@@ -31,7 +31,7 @@ For production, run `npm run build` followed by `npm start`, and keep the proces
## Docker
Build and start the service with Docker Compose:
Build and start the calendar service and Apprise with Docker Compose:
```sh
Copy-Item .env.example .env
@@ -39,7 +39,7 @@ Copy-Item .env.example .env
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`).
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: