This repository was archived by the owner on Jul 13, 2026. It is now read-only.
feat: exobase-managed hosting as the default deploy path - #15
Merged
Merged
Conversation
"Deploy" now targets an Exobase-operated Coolify instance configured via
server-only env vars (EXOBASE_COOLIFY_URL/TOKEN) — users just think
"Exobase", the way Replit users think Replit. Bringing your own Coolify
instance moves behind an Advanced disclosure in Settings > Hosting, and
BYO still wins when connected (someone who connected their own instance
did so deliberately).
Guardrails for the shared box (v1, pre-identity; real per-account quotas
land with the Phase 2 identity work):
- Apps namespaced per anonymous user (exo-{id}- prefix) with a cap of 3;
redeploys verify namespace ownership.
- Hard container limits (512m memory, 0.5 cpu) on every managed create.
- Per-IP deploy rate limit (5 per 10 min) — which surfaced that the
rate-limiter's '/api/*' catch-all was declared first and matched
everything, making every specific rule dead code, and that
'github-*'-style patterns never matched at all ('/*'-only wildcard
check). Both fixed: specific rules first, trailing-'*' now a prefix
wildcard.
Also: managed-status endpoint (boolean only — the instance URL/token
never leave the server), anon-id helper extracted from useNangoConnect
for reuse, "Open your API tokens page" deep link on the BYO form once
the instance URL parses.
Verified: typecheck/lint/build pass; in the preview, the Hosting section
shows the managed-default copy with BYO collapsed under Advanced, and
the token deep link resolves from the typed URL. Managed deploys
themselves need the env vars + a real instance to exercise.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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
The Replit model: users click Deploy and apps ship to Exobase-operated infrastructure — they never see or configure the underlying Coolify instance ("I just think Replit. I want that to be the same here").
api.coolify-deploytargets the instance from server-onlyEXOBASE_COOLIFY_URL/EXOBASE_COOLIFY_TOKENenv vars. The client only ever learns a boolean ("managed hosting available"), never the URL or token. Deploy menu reads "Deploy on Exobase".{instance}/security/api-tokensas soon as the URL parses — generate, paste, done./api/*catch-all was declared first and matched every request, so every specific rule (llmcall, waitlist, github) was dead code — andgithub-*-style patterns never matched at all. Specific rules now come first and trailing-*is a proper prefix wildcard.Real per-account quotas/billing land with Phase 2's identity work (plan updated).
Test plan
pnpm run typecheck/lint/buildpassEXOBASE_COOLIFY_*env vars point at a real instance🤖 Generated with Claude Code