bbs.profullstack/logicsrc
1
0
Fork 0
mirror of https://github.com/profullstack/logicsrc.git synced 2026-08-13 14:37:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix(cli): default logicsrc login to app.logicsrc.com (#107)

Browse source 
The default was the apex, which runs the marketing app -- so every path the CLI
needs (/cli/device/code, /cli/device/token, /cli/authorize, /cli/token,
/api/me) returns 404 there. Point it at the host that actually serves them.

app.logicsrc.com is now a custom domain on the credentials service with a valid
certificate, verified live: /cli/device/code returns 200 and issues a real user
code, /api/me returns 401 rather than 404, which is routing working correctly
for an unauthenticated request.

The apex can forward these paths instead -- that is what the rewrites in
apps/logicsrc-web/next.config.ts do -- but that needs a second service deployed
to be true, while this needs nothing beyond the domain that already exists. The
rewrites stay useful as a convenience; they are no longer load-bearing.

$LOGICSRC_API still overrides, unchanged.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Anthony Ettinger 2026-07-30 11:07:49 -07:00 • committed by GitHub
parent 898d5503b8
commit 7c9796ae51
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 10 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

18
plugins/credential-sharing/src/identity.ts
View file

@ -39,16 +39,18 @@ export function identityPath(): string {
} }
/** /**
* Where `logicsrc login` goes when nothing else is configured: the production * Where `logicsrc login` goes when nothing else is configured.
* origin, not a generated Railway hostname.
* *
* REQUIRES that logicsrc.com serve the credentials app's CLI routes * This is the credentials app (apps/pwa) on its own hostname, which is what
* (`/cli/device/code`, `/cli/device/token`, `/cli/authorize`, `/cli/token`, * actually serves the CLI routes — /cli/device/code, /cli/device/token,
* `/api/me` — see apps/pwa/src/routes/cli.mjs). Until the apex is pointed at * /cli/authorize, /cli/token and /api/me (see apps/pwa/src/routes/cli.mjs).
* that service, login fails with a 404 on the first request; set $LOGICSRC_API *
* to the deployment origin to work around it. * NOT the apex: logicsrc.com runs the marketing app, so every one of those
* paths 404s there. The apex can forward them (see the rewrites in
* apps/logicsrc-web/next.config.ts), but pointing straight at the host that
* serves them needs no proxy hop and no deploy of a second service to work.
*/ */
export const DEFAULT_API_URL = "https://logicsrc.com"; export const DEFAULT_API_URL = "https://app.logicsrc.com";
/** An explicitly configured API origin, if any. `LOGICSRC_API` is the documented one. */ /** An explicitly configured API origin, if any. `LOGICSRC_API` is the documented one. */
export function envApiUrl(): string | undefined { export function envApiUrl(): string | undefined {