Cards / razzia
Razzia, a Kahoot-style quiz game you host for a room of players who join from their phones
No steward yet · MITEdgible cards 53/53
| App | What | Who can reach it | Place |
|---|---|---|---|
razzia | Razzia, the host screen and the players' phones | open to anyone | razzia |
A place is one serving device. Minimum recommended for each:
| Place | Memory | Disk | Architecture | GPU |
|---|---|---|---|---|
razzia | 256 MB | 1 GB | amd64, arm64 | none |
The first start downloads the app's images: about 41 MB, under a minute on a typical home connection. That time is the download from the app's registry, not Edgible, and it happens once: later starts and upgrades reuse the images and fetch only what changed.
| Volume | What it is |
|---|---|
razzia-config | yours alone: backed up, and checked after a restore or a move |
razzia-secrets | yours alone: backed up, and checked after a restore or a move |
After a restore or a move, a quick count shows the data arrived, with nothing read but numbers and dates.
RAZZIA_JWT_SECRET. The card makes them at first start, and only its own apps read them. They stay on the machine, and in its backups.RAZZIA_MANAGER_PASSWORD: the host's sign-in, to create quizzes and start games. Made on your machine too, where the show command in the README prints it.3 of 5 checks passed. Each is a fact about the app, not an opinion: how they are decided (opens in a new tab).
Setting it up by hand? Install Edgible from edgible.com (opens in a new tab), then follow the steps below.
You want to run a quiz for a classroom, a club night, a team event or a family evening, where everyone answers on their own phone and a big screen shows the scores, without a hosted quiz service and its player limits. Razzia (opens in a new tab) is a Kahoot-style quiz platform made for smaller events. The host builds quizzes and starts a game; players type the game code in their phone's browser, with no account and nothing to install.
One Razzia container, with its quizzes, media and results in one volume. It is published on one hostname with auth mode none, because the players are guests with no Edgible account, on phones that cannot get past an Edgible sign-in. The host page is on the same hostname, so Razzia's own host password is what stops a stranger from creating quizzes or starting games; players can only join a game the host has started. A strong host password and a session signing key are made on the machine at first start, and are not in card.env. If only your Edgible organization will ever play, change the hostname to org after Publish with edgible app update.
The quizzes, uploaded media and saved results are in the razzia-config volume; the host password and signing key are in razzia-secrets. Minimum recommended for the place razzia: 256 MB of memory and 1 GB of disk, on an arm64 or amd64 machine, with no GPU.
The Compose file is docker-compose.yml (opens in a new tab), the settings card.env (opens in a new tab), the card card.yml (opens in a new tab).
Five steps. Edit card.env (opens in a new tab) before you start.
mkdir -p razzia
curl -fsSL https://github.com/edgible-org/cards/archive/refs/heads/main.tar.gz \
| tar -xz --strip-components=2 -C razzia cards-main/razzia
Set DEVICE.
nano razzia/card.env
curl -fsSLo check-env.py https://raw.githubusercontent.com/edgible-org/card-kit/main/check-env.py
python3 check-env.py razzia
It moves a taken port, as lines to paste. Run it again until it says no conflicts.
docker compose --env-file razzia/card.env -f razzia/docker-compose.yml pull
docker compose --env-file razzia/card.env -f razzia/docker-compose.yml up -d --wait
docker compose --env-file razzia/card.env -f razzia/docker-compose.yml ps
The first start downloads the app's images from the registries named in the Compose file, which takes longer for a larger app. pull does that download on its own, so you can see it. The time is the download, not Edgible, and it happens once: later starts and upgrades reuse the images on the machine and fetch only what changed. --wait returns when each service is running, and healthy when it has a healthcheck.
set -euo pipefail
set -a
. razzia/card.env
set +a
device_id=$(edgible device list --json | jq -er --arg name "$DEVICE" '
map(select(.name == $name))
| if length == 1 then .[0].id
else error("need exactly one device named " + $name + " (" + (map(.status + " " + .id) | join(", ")) + ")")
end
')
edgible app create existing \
--non-interactive \
--name razzia \
--port "$RAZZIA_PORT" \
--protocol https \
--auth-modes none \
--device-id "$device_id"
edgible app list
Without Edgible: only Publish is Edgible's. The app listens on 127.0.0.1 at the port in card.env, so any reverse proxy or tunnel on the machine, such as Caddy, nginx, Cloudflare Tunnel or Tailscale, can publish it instead, and sign-in is then that tool's to provide. Every other step stays the same.
razzia uses none.
curl -sS -o /dev/null -w '%{http_code}\n' "https://<razzia hostname>"
Answers with the Razzia page, open to the internet. Open it, choose the host side, and sign in with the host password the card made. Show it on the machine with docker compose --env-file razzia/card.env -f razzia/docker-compose.yml run --rm --no-deps razzia-secrets show RAZZIA_MANAGER_PASSWORD. Players open the same address on their phones and enter the game code.
The rest of the setup is in the Razzia docs (opens in a new tab).
Four steps, in this order. Step 1 runs wherever edgible is logged in. Steps 2 to 4 run on the machine that runs the containers. Steps 2 and 3 read card.env, so keep it until step 4.
edgible app delete razzia --yes
docker compose --env-file razzia/card.env -f razzia/docker-compose.yml down
Skip this step to keep the data. The loop copies each volume to a .tgz file in this directory first.
for volume in $(docker volume ls -q --filter label=com.docker.compose.project=razzia); do
docker run --rm -v "$volume:/data:ro" -v "$PWD:/backup" alpine tar -czf "/backup/$volume.tgz" -C /data .
done
docker compose --env-file razzia/card.env -f razzia/docker-compose.yml down --volumes
rm -rf razzia