Solved TAIGA and Peertube variable bug

This commit is contained in:
Kevin Veen-Birkenbach 2025-05-15 15:22:24 +02:00
parent fd698e9cc6
commit a42d5e39cf
No known key found for this signature in database
GPG Key ID: 44D8F11FD62F878E
2 changed files with 2 additions and 2 deletions

View File

@ -11,7 +11,7 @@ PEERTUBE_DB_HOSTNAME={{database_host}}
PEERTUBE_WEBSERVER_HOSTNAME={{domains[application_id]}} PEERTUBE_WEBSERVER_HOSTNAME={{domains[application_id]}}
PEERTUBE_TRUST_PROXY=["127.0.0.1", "loopback"] PEERTUBE_TRUST_PROXY=["127.0.0.1", "loopback"]
applications[application_id].credentials.secret={{applications[application_id].credentials.secret}} PEERTUBE_SECRET={{applications[application_id].credentials.secret}}
# E-mail configuration # E-mail configuration
PEERTUBE_SMTP_USERNAME={{ users['no-reply'].email }} PEERTUBE_SMTP_USERNAME={{ users['no-reply'].email }}

View File

@ -6,7 +6,7 @@ TAIGA_SUBPATH = "" # it'll be appended to the TAIGA_DOMAIN (use either
WEBSOCKETS_SCHEME = wss # events connection protocol (use either "ws" or "wss") WEBSOCKETS_SCHEME = wss # events connection protocol (use either "ws" or "wss")
# Taiga's Secret Key - Variable to provide cryptographic signing # Taiga's Secret Key - Variable to provide cryptographic signing
applications[application_id].credentials.secret_key = "{{applications[application_id].credentials.secret_key}}" # Please, change it to an unpredictable value!! TAIGA_SECRET_KEY = "{{applications[application_id].credentials.secret_key}}"
SECRET_KEY = "{{applications[application_id].credentials.secret_key}}" SECRET_KEY = "{{applications[application_id].credentials.secret_key}}"
# Taiga's Database settings - Variables to create the Taiga database and connect to it # Taiga's Database settings - Variables to create the Taiga database and connect to it