Repository navigation
fix: close hosted signups and point the readme at self-hosting - #295
Merged
Merged
Conversation
FrkAk
force-pushed
the
fix/close-hosted-signups
branch
from
September 29, 2026 14:31
28fe0f4 to
f2720d5
Compare
FrkAk
marked this pull request as ready for review
September 29, 2026 14:40
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
The hosted version at app.piyaz.ai is shutting down, so this closes new signups on the hosted production deploy and makes the README describe self-hosting only.
deploy:cfandpreview:cfno longer passSIGNUPS_ENABLED=true, so the production build bakes signups off andsignupsDisabled()serves the invite-only page and rejects/sign-up/email. Existing accounts keep signing in.signupsDisabled()only closes signup whenDEPLOY_TARGET=cloudflare, so self-hosted builds stay open (covered by the existing "signup open on self-host" test).deploy:cf:devkeeps the opt-in.<your-instance>/api/mcp.Type of change
Testing
bun run devbun run lint)bun run typecheck)bun run build:cf && bun run smoke:cf) — required when this PR touchesapp/api/**,middleware.ts,worker-cf.ts, or a.node.ts/.workers.tspairtests/config/env.test.tsnow pins that the production scripts omit the opt-in and the dev script keeps it.Notes for reviewer
Takes effect on the next release deploy. The sign-up page copy still reads "Invite only for now". Plugin MCP configs,
server.json, the get-started modal and the legal pages still point at app.piyaz.ai; flagged for a follow-up.Docs impact
Compliance impact