# gbandit

> gbandit hosts web games and web apps. You write the Dockerfile(s) and a
> gbandit.jsonc, run `gbandit deploy --create`, and the platform builds and
> hosts the app with a managed database, auth, and dev/prod environments.

## Docs

- [Deploy contract](https://docs.gbandit.com/deploy.md): Everything needed to go from an arbitrary repo to a deployed app: gbandit.jsonc, Dockerfile contracts, routing, runtime hardening, databases, git behaviour, CLI.
- [Authentication](https://docs.gbandit.com/auth.md): The shared auth flow: getting a game token (a per-project JWT) from the auth.gbandit.com cookie, and verifying it in your backend.
- [The gbandit runtime](https://docs.gbandit.com/runtime.md): The script every game loads from /__gbandit/runtime.js: the player's token, player counting, frontend logs, and serving it under a local dev server.
- [Player activity (heartbeat)](https://docs.gbandit.com/heartbeat.md): How the runtime counts a game's players for the games.gbandit.com ranking.
- [Frontend logs](https://docs.gbandit.com/frontend-logs.md): What the runtime reports from your players' browsers to `gbandit logs frontend`.
- [Errors](https://docs.gbandit.com/errors.md): The RFC 9457 Problem Details body every gbandit API answers a failure with, and every problem `type` it can carry.
- [Getting started: use the template](https://docs.gbandit.com/getting-started-template.md): Guide: scaffold a complete working game with `gbandit scaffold` and deploy it.
- [Getting started: deploy an existing app](https://docs.gbandit.com/getting-started-existing.md): Guide: bring an existing repo to gbandit — gbandit.jsonc, Dockerfile, the porting pitfalls.

## Optional

- [Full documentation in one file](https://docs.gbandit.com/llms-full.txt)