Files
computer-playbook/roles/web-app-chess
Kevin Veen-Birkenbach a4a8061998 Refactor: unify Docker build config via build.yml.j2 include
Replaced duplicated inline build definitions in multiple docker-compose.yml.j2
templates with a shared include (roles/docker-container/templates/build.yml.j2).
This ensures consistent use of pull_policy: never and Dockerfile context across
services (Postgres, Bookwyrm, Bridgy Fed, Chess, Confluence, Jira, Moodle,
OpenProject, Pretix, Roulette Wheel, WordPress, XWiki, Simpleicons).

Conversation: https://chatgpt.com/share/68cd8f35-b764-800f-9b00-2c837103d2fb
2025-09-19 19:13:44 +02:00
..
2025-09-03 17:30:31 +02:00
2025-09-03 17:30:31 +02:00

Chess

Description

castling.club is a federated chess server built on the ActivityPub protocol.
It provides an open and decentralized way to play chess online, where games and moves are visible across the Fediverse.

Overview

Instead of relying on closed platforms, castling.club uses an arbiter actor (“the King”) to validate moves and mediate matches.
This ensures fair play, federation with platforms like Mastodon or Friendica, and community visibility of ongoing games.
The service runs as a lightweight Node.js app backed by PostgreSQL.

Features

  • Federated Chess Matches: Challenge and play with others across the Fediverse.
  • Rule Enforcement: The arbiter validates each move for correctness.
  • Open Identities: Use your existing Fediverse account; no new silo account needed.
  • Game Visibility: Matches and moves can appear in social timelines.
  • Lightweight Service: Built with Node.js and PostgreSQL for efficiency.

Further Resources