Skip to content

Merge pull request #17 from JARVIS-discordbot/Production #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BenCos17 merged 3 commits into from
Jun 6, 2026
Merged

Merge pull request #17 from JARVIS-discordbot/Production #18

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
31c79f9
Merge pull request #17 from JARVIS-discordbot/Production
BenCos17 Jun 6, 2026
0f39633
a lot of things
BenCos17 Jun 6, 2026
ed25181
Merge branch 'main' of https://github.com/JARVIS-discordbot/landing
BenCos17 Jun 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,14 @@ this is using github pages and shows up here
https://jarvis-discordbot.github.io/landing/
the code will auto deploy to production when commited to the production branch (anyone doing dev please push to main and I'll pr to production when it's tested and checked)

## Pages in this repo

| File | Purpose | Staging (GitHub Pages) | Production |
|------|---------|------------------------|------------|
| `index.html` | Main landing page | Yes | Deployed as `landing.html` via CI |
| `clusters.html` | Live cluster telemetry dashboard | No* | Served from the bot API host (e.g. `clusters.jarvisdiscordbot.net`) |

\* `clusters.html` fetches `/clusters` on the same origin as the page, so it must be deployed alongside the bot API—not via GitHub Pages. Keep it in this repo for version control; deploy it to the cluster status server separately.

credits:
1. @bencos17
Expand Down
Loading
Loading