feat: use secret_key config field instead of api_key (#2444)

Fixes #2426
This commit is contained in:
Jonas L 2023-03-22 10:14:11 +01:00 committed by GitHub
parent 74af2112a6
commit d800c5e280
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 31 additions and 1 deletions

View file

@ -1,6 +1,7 @@
general:
public_url: http://localhost:8080
api_key: some_secret_api_key
secret_key: some_secret_key
database:
host: postgres

View file

@ -7,6 +7,10 @@ general:
# The internal API authentication key.
# > this field is REQUIRED
api_key:
# The Django API secret key. If not defined, the value of [general.api_key] will be
# used as fallback.
# > this field will be REQUIRED starting with LibreTime 4.0.0
secret_key:
# List of origins allowed to access resources on the server, the public url
# origin is automatically included.

View file

@ -7,6 +7,10 @@ general:
# The internal API authentication key.
# > this field is REQUIRED
api_key: some_secret_api_key
# The Django API secret key. If not defined, the value of [general.api_key] will be
# used as fallback.
# > this field will be REQUIRED starting with LibreTime 4.0.0
secret_key:
# List of origins allowed to access resources on the server, the public url
# origin is automatically included.