Skip to content

Resolve GitHub Pages 404 by aligning deploy root and entrypoint paths - #1

Merged
VloStudios merged 1 commit into
mainfrom
copilot/fix-it
Sep 15, 2026
Merged

VloStudios merged 1 commit into
mainfrom
copilot/fix-it

Conversation

Copilot AI commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

The site was returning 404 on GitHub Pages because deployment published the repository root while the actual entrypoint lived under static/. In addition, index.html contained Flask template asset paths that do not resolve in static hosting.

  • Deployment target correction

    • Updated Pages publish directory to ./static so the deployed artifact contains the actual index.html.
  • Static hosting compatibility

    • Replaced Jinja/Flask url_for(...) asset references in static/index.html with relative static paths (css/..., js/...) so assets resolve when served directly by Pages.
  • Local/server entrypoint parity

    • Changed Flask / route to serve static/index.html directly, keeping local runtime behavior consistent with the Pages artifact.
# .github/workflows/deploy.yml
with:
  github_token: ${{ secrets.GITHUB_TOKEN }}
  publish_dir: ./static

Co-authored-by: VloStudios <198949883+VloStudios@users.noreply.github.com>
@VloStudios
VloStudios marked this pull request as ready for review September 15, 2026 07:52
@VloStudios
VloStudios merged commit 4f650f4 into main Sep 15, 2026
1 check 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.

2 participants