mirror of
http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git
synced 2025-07-01 22:26:41 +00:00
update alerter config to use docker configuration
This commit is contained in:
parent
47f11d8c1f
commit
403b8fbfd4
1 changed files with 14 additions and 0 deletions
|
@ -92,6 +92,7 @@ Now that we laid out the justifications for this setup, let's set it up on our s
|
|||
environment:
|
||||
- USER_UID=1000
|
||||
- USER_GID=1000
|
||||
- FORGEJO__webhook__ALLOWED_HOST_LIST="alerter" # add this to enable the alerter
|
||||
restart: always
|
||||
networks:
|
||||
- forgejo
|
||||
|
@ -399,8 +400,21 @@ As there is no way to send emails in a secure, anonymous way ForgeJo can be conf
|
|||
- Using the [simpleX](../simplexalerts/index.md) alerter tutorial, set up an instance listening on localhost:7897, configured with a group to receive your alerts. For the next part
|
||||
of this tutorial we will be using a group called "forgejotest"
|
||||
|
||||
#### Docker-compose configuration
|
||||
|
||||
add the following service entry:
|
||||
|
||||
alerter:
|
||||
image: simplex-alerter:latest
|
||||
restart: always
|
||||
volumes:
|
||||
- /my/alerter/data/folder:/simplex
|
||||
- /my/alerter/data/folder:/alerterconfig
|
||||
|
||||
|
||||
### Forgejo Configuration
|
||||
|
||||
|
||||
First, brows to the repository you want to activate notification for, then go to settings:
|
||||
|
||||

|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue