docs(build): developer guides for game servers, routing, and runtime capabilities#40
Open
hbrombeer wants to merge 1 commit into
Open
docs(build): developer guides for game servers, routing, and runtime capabilities#40hbrombeer wants to merge 1 commit into
hbrombeer wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Fold the genuinely developer-useful platform concepts into the Build tab, reframed as "what you do and get" (not platform internals) and grounded in current capability maturity rather than the roadmap: - concepts/game-servers — what a gamemode push becomes under Agones - concepts/connecting-players — how a player reaches your server - runtime/environment-and-secrets — per-app env vars + encrypted secrets - runtime/databases — what persists across a push (honest: no managed DB) - runtime/messaging — declaring + publishing NATS events (cross-app is roadmap) - runtime/backend-services — the service type and its real current maturity Adds a Runtime group and two Concepts pages to the Build nav. Also corrects build/observability: Grafana is reachable but not project- isolated, so the supported per-developer surfaces (portal Logs tab, `grounds logs`, portal metrics) lead instead of Grafana. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
hbrombeer
force-pushed
the
docs/platform-architecture
branch
from
df95a24 to
384587b
Compare
hbrombeer
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Folds the genuinely developer-useful platform concepts into the Build tab as helpful, honest developer docs — reframed as "what you do and get" rather than platform internals, and grounded in current capability maturity (verified against the code) instead of the roadmap.
New pages
Concepts
game-servers— what a gamemode push becomes under Agones (Fleet/GameServer, Ready/Allocated, replicas) without touching Kubernetesconnecting-players— how a player actually reaches your server (<mode>-<handle>.mc.grnds.io→ edge → Velocity → your allocated server)Runtime (new group — what your app gets at runtime)
environment-and-secrets— per-app env vars (shipped) + encrypted secrets (rolling out; writes 503 until the key is provisioned + the carrying release deploys)databases— what survives a push; honest that there's no managed per-app database today (persist in an external DB via a secret; managed Postgres is roadmap)messaging— declaring + publishing NATS events from yourgrounds.yaml; honest that reliable cross-app pub/sub is not yet provenbackend-services— theservicetype (push an HTTP service, get a URL) vs the in-progress first-class gRPC domain-service storyCleanup
build/observability:grafana.platform.grnds.iois reachable but not project-isolated, so the supported per-developer surfaces (portal Logs tab,grounds logs, portal metrics) now lead; Grafana is framed as an operator/ad-hoc tool.How it was produced
Capability maturity was verified against the real code first (env vars, secrets, Postgres, NATS-from-app, services, Grafana access), then each page was written from that ground-truth and reviewed on two axes: developer usefulness and accuracy/honesty (no roadmap-as-shipped). Pages mark early/unavailable capabilities plainly.
Validation
All internal links resolve, frontmatter + MDX-safety checks pass,
docs.jsonnav fully covers the new pages. Relying on the Mintlify preview build on this PR for the authoritative check.🤖 Generated with Claude Code