Merge pull request #44 from fisuda/feature/configurability

[WIP] Allow to configure LOGOUT_REDIRECT_URL settings through environment variables

Author: aarranz

1.3/settings.py

@@ -141,6 +141,7 @@
     "KEYCLOAK_SERVER",
     "KEYCLOAK_REALM",
     "KEYCLOAK_KEY",
+    "LOGOUT_REDIRECT_URL",
     "SECRET_KEY",
     "SESSION_COOKIE_NAME",
     "SOCIAL_AUTH_FIWARE_KEY",
@@ -151,6 +152,7 @@
 SENSITIVE_SETTINGS = (
     "EMAIL_HOST_PASSWORD",
     "KEYCLOAK_KEY",
+    "LOGOUT_REDIRECT_URL",
     "SECRET_KEY",
     "SOCIAL_AUTH_FIWARE_KEY",
     "SOCIAL_AUTH_FIWARE_SECRET",

README.md

@@ -72,9 +72,9 @@ In addition to those environment variables, this docker image also allows you to
 configure the following Django settings using environment variables with the
 same name: `CSRF_COOKIE_AGE`, `CSRF_COOKIE_HTTPONLY`, `CSRF_COOKIE_NAME`,
 `CSRF_COOKIE_SECURE`, `EMAIL_HOST`, `EMAIL_HOST_PASSWORD`, `EMAIL_PORT`,
-`EMAIL_HOST_USER`, `EMAIL_USE_SSL`, `EMAIL_USE_TLS`, `SECRET_KEY`,
+`EMAIL_HOST_USER`, `EMAIL_USE_SSL`, `EMAIL_USE_TLS`, `LOGOUT_REDIRECT_URL`, `SECRET_KEY`,
 `SESSION_COOKIE_AGE`, `SESSION_COOKIE_NAME`, `SESSION_COOKIE_HTTPONLY` and
-`SESSION_COOKIE_SECURE`. See [Django documentation](DJANGO_SETTINGS) for more
+`SESSION_COOKIE_SECURE`. See [Django documentation][DJANGO_SETTINGS] for more
 details.
 
 When running WireCloud with TLS behind a reverse proxy such as Apache/NGINX

dev/settings.py

@@ -140,6 +140,7 @@
     "KEYCLOAK_SERVER",
     "KEYCLOAK_REALM",
     "KEYCLOAK_KEY",
+    "LOGOUT_REDIRECT_URL",
     "SECRET_KEY",
     "SESSION_COOKIE_NAME",
     "SOCIAL_AUTH_FIWARE_KEY",
@@ -150,6 +151,7 @@
 SENSITIVE_SETTINGS = (
     "EMAIL_HOST_PASSWORD",
     "KEYCLOAK_KEY",
+    "LOGOUT_REDIRECT_URL",
     "SECRET_KEY",
     "SOCIAL_AUTH_FIWARE_KEY",
     "SOCIAL_AUTH_FIWARE_SECRET",