The realtime service URL of the official kong.yml is pointed to http://realtime-dev.supabase-realtime:4000/socket, where supabase-realtime is the container name set in docker-compose.yml. This fixed container name doesn't work with dokploy because the container prefix is randomly generated.
This PR is to expose the CONTAINER_PREFIX environment variable to kong service, then utilize it to format the correct URL for the realtime service.
🔄 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/563
**Author:** [@yeliu84](https://github.com/yeliu84)
**Created:** 12/1/2025
**Status:** ✅ Merged
**Merged:** 2/15/2026
**Merged by:** [@Siumauricio](https://github.com/Siumauricio)
**Base:** `canary` ← **Head:** `fix-supabase-kong-realtime-service-resolution`
---
### 📝 Commits (1)
- [`e66c889`](https://github.com/Dokploy/templates/commit/e66c8893b0fe097f9e4d4c9520198ece44934b4e) Fix realtime service name resolution
### 📊 Changes
**2 files changed** (+4 additions, -3 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/supabase/docker-compose.yml` (+1 -0)
📝 `blueprints/supabase/template.toml` (+3 -3)
</details>
### 📄 Description
The realtime service URL of the official `kong.yml` is pointed to `http://realtime-dev.supabase-realtime:4000/socket`, where `supabase-realtime` is the container name set in `docker-compose.yml`. This fixed container name doesn't work with dokploy because the container prefix is randomly generated.
This PR is to expose the CONTAINER_PREFIX environment variable to kong service, then utilize it to format the correct URL for the realtime service.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/563
Author: @yeliu84
Created: 12/1/2025
Status: ✅ Merged
Merged: 2/15/2026
Merged by: @Siumauricio
Base:
canary← Head:fix-supabase-kong-realtime-service-resolution📝 Commits (1)
e66c889Fix realtime service name resolution📊 Changes
2 files changed (+4 additions, -3 deletions)
View changed files
📝
blueprints/supabase/docker-compose.yml(+1 -0)📝
blueprints/supabase/template.toml(+3 -3)📄 Description
The realtime service URL of the official
kong.ymlis pointed tohttp://realtime-dev.supabase-realtime:4000/socket, wheresupabase-realtimeis the container name set indocker-compose.yml. This fixed container name doesn't work with dokploy because the container prefix is randomly generated.This PR is to expose the CONTAINER_PREFIX environment variable to kong service, then utilize it to format the correct URL for the realtime service.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.