WP-NOW: Open browser with blueprint landingPage instead of absoluteUrl (

#233) * Open blueprint landingPage when defined instead of absoluteUrl.
WordPress · Apr 15, 2024 · bca8656 · bca8656
1 parent 270c1e5
commit bca8656
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/packages/wp-now/src/config.ts b/packages/wp-now/src/config.ts
@@ -46,6 +46,7 @@ export interface WPNowOptions {
 	numberOfPhpInstances?: number;
 	blueprintObject?: Blueprint;
 	reset?: boolean;
+	landingPage?: string;
 }
 
 export const DEFAULT_OPTIONS: WPNowOptions = {
@@ -56,6 +57,7 @@ export const DEFAULT_OPTIONS: WPNowOptions = {
 	mode: WPNowMode.AUTO,
 	numberOfPhpInstances: 1,
 	reset: false,
+	landingPage: '',
 };
 
 export interface WPEnvOptions {
@@ -171,6 +173,10 @@ export default async function getWpNowConfig(
 			options.absoluteUrl = siteUrl;
 			absoluteUrlFromBlueprint = siteUrl;
 		}
+		if (blueprintObject.landingPage) {
+			options.landingPage =
+				(await getAbsoluteURL()) + blueprintObject.landingPage;
+		}
 	}
 	return options;
 }

diff --git a/packages/wp-now/src/start-server.ts b/packages/wp-now/src/start-server.ts
@@ -102,9 +102,9 @@ export async function startServer(
 			output?.trace(e);
 		}
 	});
-	const url = options.absoluteUrl;
+	const url = options.landingPage || options.absoluteUrl;
 	const server = app.listen(port, () => {
-		output?.log(`Server running at ${url}`);
+		output?.log(`Server running at ${options.absoluteUrl}`);
 	});
 
 	return {