06 — Deploy

Git-FED uploads to GitHub. Muse never writes to GitHub. Check the live site after every upload. This project is prepared as a static GitHub Pages site. It has not been uploaded or published by this package.

1. Create the repository

On GitHub, create a repository named Meta-Sites. Extract this project ZIP and upload the contents of the meta-sites folder so that index.html, README.md, and assets/ are at the repository root. Do not upload the ZIP as the site's only file. Choose a visibility appropriate for the content; published GitHub Pages sites are publicly available on the internet.

The project includes a regular index.html with relative paths, so it is suitable for a project site. The Pages URL normally includes the repository path, for example https://OWNER.github.io/Meta-Sites/. Use the exact URL GitHub displays for this repository.

2. Turn on GitHub Pages

In the repository, open Settings → Pages. Under Build and deployment, choose Deploy from a branch. Select the branch that contains the uploaded files (often main) and choose the root folder (/(root)), then save. The branch and folder must contain index.html at that root. GitHub's current settings labels or layout may change; the official publishing-source guide is the reference for the current screen.

Wait for the Pages deployment to finish. Open the URL GitHub shows in Settings → Pages. The first deployment or a new update may take a short while; GitHub notes that a change can take up to 10 minutes to publish.

3. Add the Pages URL in Google Sites

Put the published GitHub Pages URL in Google Sites as a link or embedded website. Follow Google Sites steps, then publish the Google Site changes.

4. Check every upload

After each upload, Git-FED must:

  1. Open the live Pages URL and confirm the changed text is present.
  2. Refresh that Pages URL and confirm the text remains.
  3. If Google Sites is the visitor entry point, open the published Google Site and verify its link or embed reaches the same Pages URL.

If the old version appears, use Troubleshooting. Do not assume that editing the local file or uploading a commit means the live page has already changed.

Sources

Cloudflare in the delivery path

The ZIP includes a fixed-origin Cloudflare Worker at cloudflare/worker.js and a wrangler.toml template. Replace the placeholder GitHub account in GITHUB_PAGES_ORIGIN before deploying. The requested proxy path is GitHub Pages as origin, then Cloudflare Worker, then the visitor. The exact Cloudflare route requires a Cloudflare-managed zone and hostname, neither of which was supplied or configured here. Follow Cloudflare routing.

Alternatively, connect the same GitHub repository directly to a Cloudflare Pages project. That option deploys from GitHub automatically but Cloudflare Pages becomes the host; GitHub Pages is no longer between the source repository and visitor. Do not configure both as competing production hosts.