Skip to content

Add GitHub Pages public web distribution - #7

Merged
na399 merged 2 commits into
mainfrom
feat/github-pages-public-web
Aug 30, 2026
Merged

Add GitHub Pages public web distribution#7
na399 merged 2 commits into
mainfrom
feat/github-pages-public-web

Conversation

@na399

@na399 na399 commented Aug 30, 2026

Copy link
Copy Markdown
Member

Summary

  • add a GitHub Pages workflow that validates the existing Rust/Tauri safety boundary, builds the Leptos/WASM application with the /DGX_Lab/ project path, validates generated references, and deploys only tested main artifacts
  • add public independence, local-execution, and browser-storage notices while preserving Tauri as the desktop distribution over the same simulator
  • document the architectural decision, repository setup, trust and persistence limits, custom-domain migration, and rollback
  • refresh Cargo metadata, Make targets, changelog, README, and the checksum manifest

Validation

  • workflow YAML parsed successfully
  • Cargo manifest parsed successfully
  • Pages artifact validator passes a valid /DGX_Lab/ fixture
  • Pages artifact validator rejects a root-hosted asset leak
  • all created Git blobs match the locally tested Git object hashes
  • release manifest contains 207 sorted, unique entries with matching hashes

Deployment behavior

Pull requests build and validate the static distribution but do not publish it. Pushes to main upload and deploy the tested artifact.

After merge

A repository administrator must select GitHub Actions under Settings → Pages once. The next successful main workflow run will then publish the public web edition.

Build and validate the Leptos/WASM application at the repository project path, deploy tested main-branch artifacts through GitHub Pages, and document the public-release, persistence, and certification boundaries.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 30, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-30T03:19:03.015796Z f2e1823 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f1b3467c0f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

run: |
make check
python3 scripts/static_rust_sanity.py
python3 scripts/verify_manifest.py

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Generate the content pack before verifying the manifest

In a clean GitHub Actions checkout, this command always fails because MANIFEST.sha256 requires dist/DGX_Lab_SLURM_Fundamentals_v1.0.0.dgxlabpack, while /dist/ is ignored and the file is not tracked; neither make check nor static_rust_sanity.py generates it. Consequently every Pages run exits here before the static build, upload, or deployment. Generate the pack first or exclude generated artifacts from manifest verification.

Useful? React with 👍 / 👎.

@na399
na399 merged commit fcb4057 into main Aug 30, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant