Trez/docker-mods-uptime-kuma-timeout-fix
4
0
Fork 0
mirror of https://github.com/TrezOne/docker-mods-uptime-kuma-timeout-fix.git synced 2026-07-18 08:48:27 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #964 from paul-arthurthiery/swag-crowdsec-api-key-readme-update

Browse Source
This commit is contained in:
Adam
2024-10-08 16:56:02 +01:00
committed by GitHub
parent f45c53b14f 78c1192dfe
commit e3ccf285d8
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -19,9 +19,10 @@ If adding multiple mods, enter them in an array separated by `|`, such as `DOCKE
If running CrowdSec in a container it must be on a common docker network with SWAG. If running CrowdSec in a container it must be on a common docker network with SWAG.
Generate an API key for the bouncer with `cscli bouncers add bouncer-swag` or `docker exec -t crowdsec cscli bouncers add bouncer-swag`, if you're running CrowdSec in a container. You have 2 options to generate a Crowdsec API key:
Make a note of the API key as you can't retrieve it later without removing and re-adding the bouncer. 1. Create an arbitrary string and pass it as the `BOUNCER_KEY_swag` environment variable in your crowdsec image
2. Generate an API key for the bouncer with `cscli bouncers add bouncer-swag` or `docker exec -t crowdsec cscli bouncers add bouncer-swag`, if you're running CrowdSec in a container. Make a note of the API key as you can't retrieve it later without removing and re-adding the bouncer.
Set the following environment variables on your SWAG container. Set the following environment variables on your SWAG container.