mirror of
https://github.com/telekom-security/tpotce.git
synced 2025-05-02 21:28:52 +00:00
Comment ENV opt-in for SentryPeer
This commit is contained in:
parent
dcf15ca489
commit
15f7a17935
4 changed files with 18 additions and 18 deletions
|
@ -13,9 +13,9 @@ services:
|
|||
# cpu_count: 1
|
||||
# cpus: 0.25
|
||||
environment:
|
||||
- SENTRYPEER_WEB_GUI=1
|
||||
- SENTRYPEER_PEER_TO_PEER=1
|
||||
- SENTRYPEER_BOOTSTRAP_NODE=bootstrap.sentrypeer.org
|
||||
# - SENTRYPEER_WEB_GUI=0
|
||||
- SENTRYPEER_PEER_TO_PEER=false
|
||||
# - SENTRYPEER_BOOTSTRAP_NODE=bootstrap.sentrypeer.org
|
||||
- SENTRYPEER_VERBOSE=1
|
||||
- SENTRYPEER_DEBUG=1
|
||||
networks:
|
||||
|
|
|
@ -374,11 +374,11 @@ services:
|
|||
sentrypeer:
|
||||
container_name: sentrypeer
|
||||
restart: always
|
||||
## SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
|
||||
## In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
|
||||
## the bad actors in its logs. Therefore this option is opt-in based.
|
||||
environment:
|
||||
- SENTRYPEER_PEER_TO_PEER=0
|
||||
# SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
|
||||
# In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
|
||||
# the bad actors in its logs. Therefore this option is opt-in based.
|
||||
# environment:
|
||||
# - SENTRYPEER_PEER_TO_PEER=0
|
||||
networks:
|
||||
- sentrypeer_local
|
||||
ports:
|
||||
|
|
|
@ -374,11 +374,11 @@ services:
|
|||
sentrypeer:
|
||||
container_name: sentrypeer
|
||||
restart: always
|
||||
## SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
|
||||
## In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
|
||||
## the bad actors in its logs. Therefore this option is opt-in based.
|
||||
environment:
|
||||
- SENTRYPEER_PEER_TO_PEER=0
|
||||
# SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
|
||||
# In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
|
||||
# the bad actors in its logs. Therefore this option is opt-in based.
|
||||
# environment:
|
||||
# - SENTRYPEER_PEER_TO_PEER=0
|
||||
networks:
|
||||
- sentrypeer_local
|
||||
ports:
|
||||
|
|
|
@ -374,11 +374,11 @@ services:
|
|||
sentrypeer:
|
||||
container_name: sentrypeer
|
||||
restart: always
|
||||
## SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
|
||||
## In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
|
||||
## the bad actors in its logs. Therefore this option is opt-in based.
|
||||
environment:
|
||||
- SENTRYPEER_PEER_TO_PEER=0
|
||||
# SentryPeer offers to exchange bad actor data via DHT / P2P mode by setting the ENV to true (1)
|
||||
# In some cases (i.e. internally deployed T-Pots) this might be confusing as SentryPeer will show
|
||||
# the bad actors in its logs. Therefore this option is opt-in based.
|
||||
# environment:
|
||||
# - SENTRYPEER_PEER_TO_PEER=0
|
||||
networks:
|
||||
- sentrypeer_local
|
||||
ports:
|
||||
|
|
Loading…
Reference in a new issue