Serve landing homepage on the radicle.network deployment

The canonical radicle.network deployment serves the marketing landing
page at `/`, while self-hosted deployments keep the node view. Opt in
at build time without changing the default.

README.md

@@ -120,6 +120,13 @@ The `nodes.homepage` key controls what is rendered at the root URL (`/`):
 The cross-seed Explore page is always available at `/explore`, regardless of
 the `homepage` setting.
 
+#### radicle.network deployment
+
+`default.json` keeps `homepage` set to `"node"`, so self-hosted deployments
+are unaffected. The canonical radicle.network deployment opts into the
+marketing site at **build time** without changing that default. To deploy
+radicle.network, run `npm run deploy`.
+
 #### Node-homepage deployment
 
 If you operate your own seed node and want the explorer to act as a

config/radicle.network.json

@@ -0,0 +1,5 @@
+{
+  "nodes": {
+    "homepage": "landing"
+  }
+}

package.json

@@ -16,7 +16,7 @@
     "test:http-client:unit": "NODE_CONFIG_ENV='test' TZ='UTC' vitest run --config http-client/vite.config.ts --reporter verbose",
     "test:http-client:unit:local": "scripts/compile-local-httpd && USE_LOCAL_HTTPD=true NODE_CONFIG_ENV='test' TZ='UTC' vitest run --config http-client/vite.config.ts --reporter verbose",
     "test:radicle-httpd": "cargo test --all-features",
-    "deploy": "rimraf build && npm clean-install && npm run build && scripts/inject-plausible && npx wrangler deploy",
+    "deploy": "rimraf build && npm clean-install && NODE_CONFIG_ENV='radicle.network' npm run build && scripts/inject-plausible && npx wrangler deploy",
     "deploy:open-graph": "cd workers/open-graph && npx wrangler deploy",
     "start:open-graph": "cd workers/open-graph && npx wrangler dev"
   },