Update authentik and fix tandoor typo

This commit is contained in:
Tobias Reisinger 2023-03-24 19:37:09 +01:00
parent 843dadf285
commit b22698a79b
Signed by: serguzim
GPG key ID: 13AD60C237A28DFE
2 changed files with 4 additions and 4 deletions

View file

@ -2,7 +2,7 @@ version: '3.2'
services: services:
server: server:
image: goauthentik.io/server:2022.11 image: ghcr.io/goauthentik/server:2023.3
restart: unless-stopped restart: unless-stopped
command: server command: server
volumes: volumes:
@ -20,7 +20,7 @@ services:
- authentik - authentik
worker: worker:
image: goauthentik.io/server:2022.11 image: ghcr.io/goauthentik/server:2023.3
restart: unless-stopped restart: unless-stopped
command: worker command: worker
user: root user: root

View file

@ -7,7 +7,7 @@ SQL_DEBUG=0
# TANDOOR_PORT=8080 # TANDOOR_PORT=8080
# hosts the application can run under e.g. recipes.mydomain.com,cooking.mydomain.com,... # hosts the application can run under e.g. recipes.mydomain.com,cooking.mydomain.com,...
ALLOWED_HOSTS=recipies.serguzim.me ALLOWED_HOSTS=recipes.serguzim.me
# random secret key, use for example `base64 /dev/urandom | head -c50` to generate one # random secret key, use for example `base64 /dev/urandom | head -c50` to generate one
SECRET_KEY= SECRET_KEY=
@ -118,7 +118,7 @@ ENABLE_METRICS=1
# see docs for more information https://vabene1111.github.io/recipes/features/authentication/ # see docs for more information https://vabene1111.github.io/recipes/features/authentication/
#SOCIAL_PROVIDERS=allauth.socialaccount.providers.openid #SOCIAL_PROVIDERS=allauth.socialaccount.providers.openid
#SOCIALACCOUNT_PROVIDERS="{'openid': {'SERVERS': [{'id': 'auth.serguzim.me', 'name': 'auth.serguzim.me', 'openid_url': 'https://auth.serguzim.me/application/o/recipies_serguzim_me/'},]}}" #SOCIALACCOUNT_PROVIDERS="{'openid': {'SERVERS': [{'id': 'auth.serguzim.me', 'name': 'auth.serguzim.me', 'openid_url': 'https://auth.serguzim.me/application/o/recipes_serguzim_me/'},]}}"
# Should a newly created user from a social provider get assigned to the default space and given permission by default ? # Should a newly created user from a social provider get assigned to the default space and given permission by default ?
# ATTENTION: This feature might be deprecated in favor of a space join and public viewing system in the future # ATTENTION: This feature might be deprecated in favor of a space join and public viewing system in the future