Adding development-containers that we used to develop fail2ban-ui, can also be used for easy and fast stack-testing

This commit is contained in:
2026-01-19 18:21:24 +01:00
parent 1190aa4f38
commit 62ab6dede3
9 changed files with 1421 additions and 0 deletions

View File

@@ -0,0 +1,25 @@
# Environment variables for keycloak OIDC development setup
# Copy this file to .env and update with your server's IP address or hostname
#
# Usage:
# cp .env.example .env
# # Edit .env with your server details
# podman compose up -d
# Your server's public URL for fail2ban-ui (used for redirect URIs)
# This is the URL that browsers will use to access fail2ban-ui
# Example for remote server: http://172.16.10.18:3080
# Example for localhost: http://localhost:3080
PUBLIC_FRONTEND_URL=http://172.16.10.18:3080
# Your server's public URL for Keycloak (usually same host, different port)
# This is the URL that browsers will use to access Keycloak
# Example for remote server: http://172.16.10.18:3000
# Example for localhost: http://localhost:3000
KEYCLOAK_URL=http://172.16.10.18:3000
# Keycloak's public URL (used for issuer in discovery document)
# Should match KEYCLOAK_URL
# Example for remote server: http://172.16.10.18:3000
# Example for localhost: http://localhost:3000
KEYCLOAK_PUBLIC_URL=http://172.16.10.18:3000