Skip to content

k-schneider/scrummy-dapr

Folders and files

NameName
Last commit message
Last commit date

Latest commit

df64c81 · Aug 18, 2022
Jan 6, 2022
Feb 20, 2022
Jan 17, 2022
Feb 16, 2022
Aug 18, 2022
Feb 23, 2022
Aug 17, 2022
Jan 6, 2022
Feb 17, 2022
Jan 6, 2022
Jan 6, 2022
Feb 20, 2022
Feb 11, 2022
Aug 18, 2022
Feb 24, 2022
Jan 6, 2022
Feb 11, 2022
Aug 18, 2022
Jan 12, 2022
Feb 20, 2022

Repository files navigation

Scrummy

An Agile Poker online multiplayer game built using .NET, powered by Dapr and SignalR.

Scrummy

Getting Started

To get a local copy up and running follow these simple steps.

Prerequisites

Installation

Clone the repo:

https://github.com/k-schneider/scrummy-dapr.git

Usage

To start Scrummy from the CLI, run the following command from the root folder:

docker-compose up

Once all services are running you can access the following services:

Scrummy reference architecture

Deployment

To deploy a standalone instance of Scrummy follow these steps.

Azure Container Apps

Use the bicep templates in the /deploy/containerapps directory. Choose between minimal and scaleout deployments. Included are sample parameter files.

To deploy using the Azure CLI execute the following command:

az group create --location canadacentral --name scrummy-rg az deployment group create --resource-group scrummy-rg --template-file main.bicep --parameters main.parameters.json

You can replace canadacentral with any other region that supports Azure Container Apps.

Minimal Deployment

Scale-out Deployment

Roadmap

  • Common agile poker decks
  • Nudge players
  • Promote other player to host
  • Spectator mode
  • Custom decks

Contributing

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.

If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE.txt for more information.

Acknowledgements

Special thanks to the people supporting the following initiatives: