No description
  • Python 87.8%
  • Dockerfile 12.2%
Find a file
mich 5dfc1abae9
All checks were successful
Build apprise image / Build container image (push) Successful in 23s
Update .forgejo/workflows/build.yaml
2026-01-02 10:28:07 +00:00
.forgejo/workflows Update .forgejo/workflows/build.yaml 2026-01-02 10:28:07 +00:00
app small fixes 2025-10-27 11:23:09 +01:00
app.env.example initial copy 2025-08-21 09:11:59 +02:00
docker-compose.example.yml initial copy 2025-08-21 09:11:59 +02:00
docker-compose.yml initial copy 2025-08-21 09:11:59 +02:00
Dockerfile small fixes 2025-10-27 11:23:09 +01:00
LICENSE Initial commit 2025-08-21 09:02:50 +02:00
manifest.tmpl initial copy 2025-08-21 09:11:59 +02:00
README.md initial copy 2025-08-21 09:11:09 +02:00
requirements.txt Update requirements.txt 2025-10-27 10:09:43 +00:00

Apprise-Microservice

Build Status Docker Stars Docker Pulls

A small JSON API server for delivering notifications using Apprise.

  • Notification services can be configured using an environment variable.
  • The service listens for JSON-formatted notification messages on port 5000.

This service is suitable as a sidecar service to another service in a container-based cluster.

Usage

These are quickstart instructions using Docker Compose.

  1. Copy app.env.example to app.env
  2. Set NOTIFICATION_URLS in app.env according to the documentation. You can add multiple targets, separated by commas.
  3. Start the container:
    docker-compose up
    
  4. In another terminal, you should now be able to trigger a notification using curl:
    curl -X POST --data '{"title": "my notification title", "body": "what a great notification service!"}' localhost:5000
    

See the file docker-compose.example.yml for a better example on how this supposed to work.

Using secrets

If running on a docker swarm cluster docker secrets can be used to set the notification URLS to avoid leaking credentials through environment variables:

  1. Set up the secret with the same content as you would with the regular environment variable
  2. Attach the secret to the service
  3. Set the NOTIFICATION_URLS_FILE to the path where the secret is mounted in the service