MSD: support CIAB routes at my.woo.localhost and my.woo.com by fushar · Pull Request #108550 · Automattic/wp-calypso

fushar · 2026-02-06T01:04:25Z

Part of DOTMSD-1073
Alternative to #108536

Proposed Changes

Add app-side routing to route CIAB hostnames (my.woo.localhost and my.woo.com) to serve app-ciab.

The basic idea is that we serve app-ciab at / base path for the above hostnames, and /ciab for any other MSD hostnames.

Important

We will need to solve how to get the "current dashboard" in this logic, as the above hostnames will no longer have the /ciab base path:

wp-calypso/client/dashboard/utils/link.ts

Line 118 in 9e300a8

export function dashboardLink( path: string = '' ) {

So interaction with Stepper / wpcom could still break. It is out of scope for this PR now.

Why are these changes being made?

See: pMz3w-nnj-p2

Testing Instructions

Check out this PR locally, run yarn start:
- Visit calypso.localhost:3000/sites; verify you see Hosting Dashboard v1
  - Verify you can also visit nav-unification pages like calypso.localhost:3000/home/:siteSlug.
- Visit my.localhost:3000; verify you see MSD (dotcom)
- Visit my.localhost:3000/ciab; verify you see MSD (CIAB)
- Visit my.woo.localhost:3000; verify you see MSD (CIAB)
Check out this PR locally, run yarn start-dashboard:
- Visit my.localhost:3000; verify you see MSD (dotcom)
- Visit my.localhost:3000/ciab; verify you see MSD (CIAB)
- Visit my.woo.localhost:3000; verify you see MSD (CIAB)
Visit <Calypso Live>/sites; verify you see Hosting Dashboard v1
- Verify you can also visit nav-unification pages like calypso.localhost:3000/home/:siteSlug.
Visit<Dashboard Live>; verify you see MSD (dotcom)
Visit<Dashboard Live>/ciab; verify you see MSD (CIAB)

Pre-merge Checklist

Has the general commit checklist been followed? (PCYsg-hS-p2)
Have you written new tests for your changes?
Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
Have you checked for TypeScript, React or other console errors?
Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
- For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

github-actions · 2026-02-06T01:04:36Z

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168601

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168601&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168601&env=a8c-for-agencies

Dashboard live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-168601&env=dashboard

matticbot · 2026-02-06T01:13:06Z

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

agents-manager
blaze-dashboard
happy-blocks
help-center
notifications
odyssey-stats
wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug my-woo-envs-alt on your sandbox.

p-jackson

Yes I think this is a good track to take. The server continues to decide which AppConfig is getting used, and webpack bundler continues to make a bundle specifically for each MSD variant. So I like that.

I don't like that the hostname config value will be incorrect from the client-side's point of view. In pMz3w-nnj-p2#comment-131646 I suggest also server-rendering the hostname config value based on the incoming request. Ultimately I think we'll need both changes, both server-rendering to make sure hostname is correct, and these changes which choose the correct section based on the incoming request.

p-jackson · 2026-02-09T01:23:27Z

client/dashboard/utils/link.ts

+	return [
+		'http://my.localhost:3000',
+		'https://my.wordpress.com',
+		'http://my.woo.localhost:3000',


fwiw I kinda like my-woo.localhost:3000. Just to keep the number of sub-domain components consistent.

Hmm I don't have strong opinion; I think I subconsciously followed the existing jetpack.cloud.localhost hostname. 😄

Oh, that's fair. TIL about jetpack.cloud.localhost

p-jackson · 2026-02-09T01:28:42Z

client/dashboard/app-ciab/index.tsx

 boot( {
 	name: 'CIAB',
-	basePath: '/ciab',
+	basePath: getCiabDashboardBasePath( window.location.hostname ),


Is this just a temporary thing, having the ability to support both /ciab and my.woo.com? Seems like we should just remove the /ciab path, but this is perhaps to help with the transition so we don't immediately break the link between CIAB site dashboards and the MSD?

I think we need this anyway for the Dashboard Live link. Since we only have one live environment, and the domain is random string, there's no way to distinguish it. So currently CIAB is accessible at <Dashboard Live link>/ciab/*, while dotcom's is at the root path.

Oh yes, live links!

p-jackson · 2026-02-09T01:36:34Z

client/server/pages/index.js

-		handleRoute( DASHBOARD_CIAB_SECTION_DEFINITION, '/ciab', 'entry-dashboard-ciab', ( req ) => {
-			// Allow CIAB routes under my.localhost.
-			return req.get( 'host' ).startsWith( 'my.localhost' );
+			handleRoute( DOTCOM_DASHBOARD_SECTION_DEFINITION, route, 'entry-dashboard-dotcom', ( req ) =>


Having a separate handleRoute call for each MSD-variant seems fine to me. Calypso v1 has that giant sections.ts file to do it all declaratively, and if we end up with enough MSD-variants maybe we want to do it declaratively too. But I'm not mad about having a copy-pasted line for each dashboard type.

maybe we want to do it declaratively too.

Hmm, I'm afraid if it's possible at all. We can only get the current request's host when we actually get the request, so that's why we need to "register" all the sections and then filter the correct one based on req.get('host') imperatively here 😬

fushar force-pushed the my-woo-envs-alt branch 2 times, most recently from 60cc72a to 319de54 Compare February 6, 2026 01:12

fushar force-pushed the my-woo-envs-alt branch from 319de54 to 8d7799b Compare February 6, 2026 03:57

fushar changed the title ~~WIP support CIAB on my.woo.com~~ MSD: support CIAB routes at my.woo.localhost and my.woo.com Feb 6, 2026

fushar requested a review from taipeicoder February 6, 2026 04:02

matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Feb 6, 2026

fushar self-assigned this Feb 6, 2026

MSD: support CIAB routes at my.woo.localhost and my.woo.com

a1da870

fushar force-pushed the my-woo-envs-alt branch from 8d7799b to a1da870 Compare February 6, 2026 04:32

fushar marked this pull request as ready for review February 6, 2026 04:46

fushar requested review from a team as code owners February 6, 2026 04:46

p-jackson reviewed Feb 9, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MSD: support CIAB routes at my.woo.localhost and my.woo.com#108550

MSD: support CIAB routes at my.woo.localhost and my.woo.com#108550
fushar wants to merge 1 commit intotrunkfrom
my-woo-envs-alt

fushar commented Feb 6, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Feb 6, 2026 •

edited by matticbot

Loading

Uh oh!

matticbot commented Feb 6, 2026 •

edited

Loading

Uh oh!

p-jackson left a comment

Uh oh!

p-jackson Feb 9, 2026

Uh oh!

fushar Feb 9, 2026

Uh oh!

p-jackson Feb 9, 2026

Uh oh!

p-jackson Feb 9, 2026

Uh oh!

fushar Feb 9, 2026

Uh oh!

p-jackson Feb 9, 2026

Uh oh!

p-jackson Feb 9, 2026

Uh oh!

fushar Feb 9, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

fushar commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed Changes

Why are these changes being made?

Testing Instructions

Pre-merge Checklist

Uh oh!

github-actions bot commented Feb 6, 2026 • edited by matticbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

matticbot commented Feb 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

p-jackson left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

fushar commented Feb 6, 2026 •

edited

Loading

github-actions bot commented Feb 6, 2026 •

edited by matticbot

Loading

matticbot commented Feb 6, 2026 •

edited

Loading