Problem
Workspace pages are served by the SaaS app under /workspaces (https://<tenant>.app.myaltimate.com/workspaces). The separate <tenant>.ws.myaltimate.com host that served them before is being retired, but every workspace URL the CLI builds still points there:
- the browser hand-off page
altimate-code link opens (/create-and-link)
- the loopback success page's bounce to the new workspace, and the cancel page's bounce to the list
- the "Manage it at" links printed by
link and shown in the TUI
Proposal
Resolve the workspace base to the SaaS app's /workspaces mount and build every workspace URL relative to it. The hand-off page URL is currently built with new URL("/create-and-link", base), which drops any path on the base, so that join has to change too.
ALTIMATE_WORKSPACE_WEB_URL (dev override) should name the mount as well, e.g. http://acme.localhost:3000/workspaces.
Problem
Workspace pages are served by the SaaS app under
/workspaces(https://<tenant>.app.myaltimate.com/workspaces). The separate<tenant>.ws.myaltimate.comhost that served them before is being retired, but every workspace URL the CLI builds still points there:altimate-code linkopens (/create-and-link)linkand shown in the TUIProposal
Resolve the workspace base to the SaaS app's
/workspacesmount and build every workspace URL relative to it. The hand-off page URL is currently built withnew URL("/create-and-link", base), which drops any path on the base, so that join has to change too.ALTIMATE_WORKSPACE_WEB_URL(dev override) should name the mount as well, e.g.http://acme.localhost:3000/workspaces.