dirdori.cloud, the playground of Dir and Dori
What it is
Free browser games on the seabed, where Dir and Dori live. You play without an account. A score that competes for a leaderboard is replayed by the server, so a forged score never gets on it.
All twenty-one games play today: Dir's games of timing and counting, Dori's games of sorting and memory, and ten classics in their own jacket. Tournaments and a door for agents come later.
How it runs
- An App bundle: a container with one warm replica and its own Postgres database.
- Deployed from GitHub with the Dorelli deploy Action, on every push to main, with the id-token of GitHub Actions as proof instead of a deploy token.
- Checked every five minutes, backed up every night.
A house site
The site is a customer in everything: the same account, the same bundle, the same monitor, the same invoice. The house settles that invoice at € 0. We say so here, because you may want to know which of our examples we pay for ourselves.
What it taught us
The first days found four things in the platform that a customer with an app would have hit too. All four are fixed.
- The deploy Action did not send the image along on a first publication.
- After the first publication, the keys a second deploy needs were nowhere to be found: the summary pointed to a mail that does not carry them.
- The database role could not create a table in its own database.
- The house site flag withdrew the deploy token, and a new one needed a click in the portal. Now a site can deploy with the id-token of GitHub Actions, bound to its repository, without any token to keep.
That is what a house site is for: it keeps the platform sharp before a customer notices anything.
The source code becomes public as soon as the site runs on its own domain.