oxeo0/opsec-blogposts
1
0
Fork 0
mirror of http://git.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/nihilist/opsec-blogposts.git synced 2025-07-02 11:56:40 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

update alerter config to use docker configuration

Browse source
This commit is contained in:
midas@devnull 2025-06-15 18:40:47 +02:00
parent 47f11d8c1f
commit 403b8fbfd4
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
forgejo-anon/index.md
View file

@ -92,6 +92,7 @@ Now that we laid out the justifications for this setup, let's set it up on our s
environment: environment:
- USER_UID=1000 - USER_UID=1000
- USER_GID=1000 - USER_GID=1000
- FORGEJO__webhook__ALLOWED_HOST_LIST="alerter" # add this to enable the alerter
restart: always restart: always
networks: networks:
- forgejo - 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 - 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" 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 ### Forgejo Configuration
First, brows to the repository you want to activate notification for, then go to settings: First, brows to the repository you want to activate notification for, then go to settings:
![](new_notif.png) ![](new_notif.png)