feat(deploy): enable single-domain routing for one click deployment#1
Open
sivasubramanian95 wants to merge 2 commits intoFlowrabbitStudio:mainfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR enables single-domain deployment for Flowrabbit (one-click platform friendly) by switching default routing to path-based rules, while preserving optional legacy host-based compatibility
through an override compose file.
Problem
The previous setup depended on multiple subdomains (
api.*,studio.*,proxy.*,apps.*,docs.*) and host-based Traefik routing, which makes one-click deployments difficult.What Changed
docker-compose.yamlto single-domain path routing:/-> studio/apps-> apps/docs-> docsFLR_PUBLIC_URL-based URL composition.docker-compose.local.yamlfor localhost override.docker-compose.legacy-hosts.yamlfor optional host-based compatibility mode..env.exampleand required env-based secrets in compose.Validation
docker compose configpasses for:http://localhost/-> 200http://localhost/api/rest/status.json-> 200http://localhost/docs/status.json-> 200http://localhost/apps-> 200Compatibility / Notes
docker compose -f docker-compose.yaml -f docker-compose.legacy-hosts.yaml up -d