Releases: Terkwood/BUGOUT
Releases Β· Terkwood/BUGOUT
β° Add startup grace period for reaper
β οΈ Cloud Cost Savings, Part One
This release centers around issues raised in #75, and makes it possible to host the system on two different CoreOS VMs in Amazon Web Services.
- Split up docker-compose files to allow running on two different machines
- Configuration for the larger host
- Add reaper service to shut down the kafka host when the system is idle (see #117)
Gateway: support color choice π³
Resolves #107.
Gateway: fix .env loading πΊ
Game Lobby π
Updates and additions
- Gateway: add management of find public game and create private game (#93, #88)
- Gateway: lots of refactoring #93
- Fix timing of wait for opponent event (#93, #94)
- Adds a game lobby feature which supports queuing for a game with members of the public, or creating and sharing a link to a private game (#79, #78, #53, #62)
- Add color chooser application #83
- Cleans up some gross type tag annotations (#82 , #81)
- Cleans up the data model in gateway #80
- Cleans up log messages #91
- Remove useless type tags #82
Sabaki reference
This commit in Sabaki depends on BUGOUT v0.3.0.
History π
- Allow Sabaki to request the history of the game when white connects. This prevents a potential deadlock in the case where black makes a move before white connects. (#64, #76, Terkwood/Sabaki#16)
- Split up docker-compose files in preparation for a slimmed-down deployment. (#74)
- Clean up gateway dependencies. (#73)
Existence π»
Provides a stable system that allows two individuals to play Go over the web.