General purpose backend for multiplayer board/card games
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Hamcha 932ed7b204 Don't update room after removing it! 3 years ago
client/bot Let's make everything a single big package 3 years ago
lobby Let's make everything a single big package 3 years ago
room Don't update room after removing it! 3 years ago
.drone.yml Make gopath a shared volume bind 3 years ago
.gitignore Update ubuntu box, use docker "caching" thingie 3 years ago
.vagrantplugins Add JoinRoom implementation 3 years ago
Caddyfile caddy: Fix websocket proxying 3 years ago
Dockerfile.builder Does this work? WHO KNOWS 3 years ago
Dockerfile.publish Can't use /app there 3 years ago
Dockerfile.service-run Not-as-terrible docker config 3 years ago
LICENSE Add license 3 years ago Add .drone.yml 3 years ago
Vagrantfile Does this work? WHO KNOWS 3 years ago
cardgage.go REFACTOR EVERYTHING (wip) 3 years ago
docker-compose.yml Aliases should not be needed 3 years ago
go.mod Update moa 3 years ago
go.sum Update moa 3 years ago


Build Status

Cardgage is a (very unfinished) set of microservices built on top of moa aimed at creating a fully featured back-end for multiplayer board/card games.


Cardgage aims to:

  • Provide a lobby system to let players create and join rooms, either as players or spectators
  • Provide a communication system for low volume real-time interaction, with all interactions stored allowing games to be replayed
  • Allow for pluggable rule engines to transform the backend into an authoritative server for one or more games


Option 1. Set up a development environment

docker-compose up --force-recreate --build

Option 2. Build with Vagrant

A Vagrantfile is provided to easily build and deploy a dev environment on platforms without docker, like Windows.

First, the ugly: you need a plugin.

vagrant plugin install vagrant-docker-compose

After that, setup/run the VM with vagrant up and build the project with vagrant build.

Other things

Go 1.12 or newer required

The API gateway uses httputil.ReverseProxy, which doesn't support websockets before Go 1.12. This is technically a non-issue since golang:alpine takes the newest golang out there (which is 1.12 at the time of writing) but if you are rolling your own infrastructure you should keep this in mind.

Build custom caddy container (optional)

For the official server we keep metrics via Prometheus amongst other things, so we need a custom docker build:

docker build --build-arg plugins=prometheus,cors,git -t mcg-caddy

Re-building the builder

If go.mod changes you need to re-build the builder, there is a command for that:

vagrant make-builder

Re-building api gateway

If your docker build of apigateway is outdated, you can rebuild it by just calling

vagrant ssh -c "cd /vagrant; docker-compose build"

This will take a while.

Re-compiling protobuf files

You will need:

  • protoc

cd into the appropriate folder (<servicename>/proto) and run

protoc --go_out=plugins=grpc:. <service>.proto