fix(email): route /verify-email past DISABLE_WEB_UI; split password reset URL#32
Merged
alejandro-runner merged 1 commit intosynvya-stagingfrom Apr 17, 2026
Merged
Conversation
Synvya deployments run keycast with DISABLE_WEB_UI=true and redirect unknown routes to www.synvya.com. That swallowed the /verify-email SvelteKit route so invited users landed on the marketing site instead of verifying their email. Allowlist /verify-email (plus SvelteKit /_app static assets) in the disabled-UI branch, and add PASSWORD_RESET_BASE_URL so the reset link can point at account.{staging.,}synvya.com where Synvya hosts its own reset form that POSTs to /api/auth/reset-password. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
/verify-emailredirect bug. Synvya keycast runs withDISABLE_WEB_UI=trueandWEB_UI_REDIRECT_URL=https://www.synvya.com, so the fallback was catching/verify-email(a SvelteKit SPA route) and bouncing invited users to the marketing site before they could verify. Allowlist that route in the disabled-UI branch: serveindex.htmlwith runtime env injection, plusServeDir(web_build_dir)underneath so the SPA's/_app/*assets load. Unknown routes still redirect./reset-passwordpage onaccount.{staging.,}synvya.com(it already POSTs to keycast's/api/auth/reset-password). NewPASSWORD_RESET_BASE_URLenv var (defaults toBASE_URL) is threaded throughDevEmailSender,SendGridEmailSender, andSesEmailSender.scripts/load-secrets.shsets it to the correct per-env URL, anddocker-compose.synvya.ymlrequires it (:?error).CLAUDE.md.Verification URL is unchanged — it still uses
BASE_URL(auth.{staging.,}synvya.com), and the allowlist makes that work again.Test plan
cargo check -p keycastandcargo check -p keycast_api --features awspass (verified locally).https://auth.staging.synvya.com/verify-email?token=...and successfully verifies (no redirect to www.synvya.com).https://account.staging.synvya.com/reset-password?token=....PASSWORD_RESET_BASE_URLinto/opt/synvya/.envand keycast picks it up (checkdocker compose logs keycastfor the "reset base URL" log line)./foo) on staging and confirm it still redirects tohttps://www.synvya.com.🤖 Generated with Claude Code