github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-03-12 10:05:25 -05:00
Code Issues 155 Packages Projects Releases Wiki Activity

[PR #402] [MERGED] Update Keycloak deployment for Dokploy with reverse proxy support #431

New Issue
Closed
opened 2025-11-22 20:38:30 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-22 20:38:30 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/402
Author: @mwolf1989
Created: 9/28/2025
Status: ✅ Merged
Merged: 10/26/2025
Merged by: @Siumauricio

Base: main ← Head: update-and-fix-keycloak

📝 Commits (3)

  • 84788b2 Update KC envs and bump version
  • 825f8cf Update blueprints/keycloak/docker-compose.yml
  • 42251d5 Update blueprints/keycloak/docker-compose.yml

📊 Changes

1 file changed (+16 additions, -13 deletions)

View changed files

📝 blueprints/keycloak/docker-compose.yml (+16 -13)

📄 Description

This PR updates the Keycloak Docker Compose configuration to ensure compatibility with Dokploy’s reverse proxy setup.

  • Upgraded Keycloak to quay.io/keycloak/keycloak:26.3.5.
  • Replaced deprecated KEYCLOAK_ADMIN environment variables with KC_BOOTSTRAP_ADMIN_USERNAME and KC_BOOTSTRAP_ADMIN_PASSWORD.
  • Added KC_HOSTNAME to align with the configured domain.
  • Enabled KC_HTTP_ENABLED and KC_HEALTH_ENABLED for easier monitoring.
  • Configured KC_PROXY_HEADERS=xforwarded to properly handle HTTPS and forwarded headers behind a proxy.
  • Simplified networking by removing unnecessary hostname v1 options.
  • Add healthcheck for postgres
  • remove version from docker compose since this is not needed anymore

This ensures that Keycloak runs reliably behind Dokploy’s reverse proxy without mixed content or CSP errors.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/402 **Author:** [@mwolf1989](https://github.com/mwolf1989) **Created:** 9/28/2025 **Status:** ✅ Merged **Merged:** 10/26/2025 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `main` ← **Head:** `update-and-fix-keycloak` --- ### 📝 Commits (3) - [`84788b2`](https://github.com/Dokploy/templates/commit/84788b2fc8b89ee282c7cbe08e267190e37a7afc) Update KC envs and bump version - [`825f8cf`](https://github.com/Dokploy/templates/commit/825f8cf0fa84a4f907bf1c7d7ab6bde290159797) Update blueprints/keycloak/docker-compose.yml - [`42251d5`](https://github.com/Dokploy/templates/commit/42251d53ba979a5c456793fe5e08ee84d3c32965) Update blueprints/keycloak/docker-compose.yml ### 📊 Changes **1 file changed** (+16 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/keycloak/docker-compose.yml` (+16 -13) </details> ### 📄 Description This PR updates the Keycloak Docker Compose configuration to ensure compatibility with Dokploy’s reverse proxy setup. - Upgraded Keycloak to quay.io/keycloak/keycloak:26.3.5. - Replaced deprecated KEYCLOAK_ADMIN environment variables with KC_BOOTSTRAP_ADMIN_USERNAME and KC_BOOTSTRAP_ADMIN_PASSWORD. - Added KC_HOSTNAME to align with the configured domain. - Enabled KC_HTTP_ENABLED and KC_HEALTH_ENABLED for easier monitoring. - Configured KC_PROXY_HEADERS=xforwarded to properly handle HTTPS and forwarded headers behind a proxy. - Simplified networking by removing unnecessary hostname v1 options. - Add healthcheck for postgres - remove version from docker compose since this is not needed anymore This ensures that Keycloak runs reliably behind Dokploy’s reverse proxy without mixed content or CSP errors. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-22 20:38:30 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#431
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?