Skip to content

Serve the self-hosting landing page at /self-host - #12

Merged
aminghuf merged 1 commit into
mainfrom
landing-split
Oct 8, 2026
Merged

aminghuf merged 1 commit into
mainfrom
landing-split

Conversation

@aminghuf

@aminghuf aminghuf commented Oct 8, 2026

Copy link
Copy Markdown
Owner

On chesspirit.app, / showed the existing static home page, but the new landing page appeared after visiting /try and clicking back to the home page.

Cause. The reverse proxy on the server serves a static page at /. Every other path goes to the app, so the in-app landing page was only reachable by a client-side jump to /.

Fix. Keep both pages:

  • / stays the static page, for players.
  • /self-host is the in-app landing page, for people who want to run their own copy.

Changes:

  • New route /self-host serves the landing page for signed-out and signed-in visitors.
  • Public pages link to it from the header (from /try and shared reviews).
  • When signed out, the logo and the not-found "Go to Chesspirit" button do a full page load to /, so the proxy's page shows. When signed in, the logo still goes to the app's Home.
  • An unknown signed-out path goes to /login again instead of the landing page.
  • Open Graph tags for /self-host; the README links it.

Tests. npm run typecheck, 477 tests and the build pass. Browser check: /self-host renders, the header link works from /try, the logo is href="/", and /nope goes to /login.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BANAeunr22J7BzgopZzgWs


Generated by Claude Code

chesspirit.app's reverse proxy serves its own home page at /, so the in-app
landing page only appeared after a client-side jump back from /try. Serve it
at /self-host, link it from the public header, make the signed-out logo a
full page load to /, and send unknown signed-out paths to /login again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BANAeunr22J7BzgopZzgWs
@aminghuf
aminghuf merged commit b31828f into main Oct 8, 2026
4 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.

2 participants