MUSEtiny tech desk
Deployment · Static files only

One folder.
Three ways to ship.

The actual website lives in site/. There is no build step, server database, account system or Manus-hosted URL in this package.

GitHub Pages

  1. Push this repository to GitHub and use the included Actions workflow at .github/workflows/static.yml.
  2. In the repository, open Settings → Pages and select GitHub Actions as the publishing source.
  3. Push to main. The workflow publishes the site/ directory.

The site uses ordinary relative links to named HTML files, so it works from a repository subpath without a custom rewrite engine.

Cloudflare Pages

For a Git-connected Cloudflare Pages project, select “None” as the framework, leave the build command blank, and set the build output directory to site. For a one-time or scripted direct upload, create the project and deploy the static directory:

npx wrangler pages project create muse-ai-glasses
npx wrangler pages deploy site --project-name muse-ai-glasses

Cloudflare Pages direct-upload projects have their own project setup choices; follow the dashboard prompts when creating your project.

Cloudflare Workers with static assets

The root includes wrangler.jsonc and worker.js. Install or run Wrangler, authenticate, then deploy:

npx wrangler login
npx wrangler deploy

Wrangler uploads site/ as static assets and the small Worker entry sends requests to those files. Unknown paths use the custom 404.html.

Choose one publishing target.

The included GitHub Actions workflow publishes to GitHub Pages. Cloudflare Pages and Workers need their own project setup and deployment command. No Cloudflare account tokens, GitHub credentials, deployment domains or private secrets are included. The Support page contains the public/live checkout identifiers supplied for PayPal and Stripe.

Official deployment docs

Back to the siteAbout and sources