GitHub issues is closed, the PivotalTracker project is the place to create new feature requests or bug reports. Please open all new issues in the icebox and use one of the templates when opening a new issue.
The Kudo project originated from the wish to create common goals for people and teams who work on different projects in order to strengthen the team spirit, collectively celebrate successes and ensure transparency within an organization.
The Kudos-o-Matic was created to keep track of these goals and the progress towards it. Users can reward each other for good deeds by giving Kudos to each other and work together to achieve common goals in the form of Kudo-thresholds.
To start using the Kudos-o-Matic, you'll need:
- Ruby (consult .ruby-version or Gemfile for the proper version)
- Ruby on Rails (consult Gemfile for the proper version)
- Redis
- Bundler
- PostgreSQL
- ImageMagick
- Mailhog (development only)
By using a Ruby version manager (such as asdf, you can easily switch between different Ruby versions and avoid conflicts that can occur when different versions use different versions of gems.
docker compose up --buildWhen everything runs:
open http://localhost:3000/graphql/playgroundTo seed the database:
docker exec -it kudo-o-matic_web bash
# in the shell of the docker container:
bundle exec rake db:seedRunning tests:
docker exec -it kudo-o-matic_web bash
# in the shell of the docker container:
RAILS_ENV=test bundle exec rspecFirst, make sure you install bundler:
gem install bundlerThen, install dependencies:
bundle install- For Windows you can download it here
- For MacOS you can use Homebrew:
brew install redis
Copy environment variables. Following the dependency setup instructions below will help you set these variables.
cp env.example .env
Create the databases and initialize it with the seed data.
The corresponding script requires Redis to be up and running, so make sure you start this first.
redis-server
bin/rails db:setupredis-server
bin/sidekiq -q default -q mailers
bin/rails s- Your GraphQL endpoint will be listening on 'http://localhost:3000/graphql'.
- You can view your Kudos-o-Matic playground at 'http://localhost:3000/graphql/playground'.
- You can set up your Kudos-o-Matic front-end by following the instructions on 'https://github.com/kabisa/kudos-frontend'
Congratulations, you did just set up the Kudos-o-Matic!
You can optionally set up the dependencies listed below to get the most out of your Kudos-o-Matic.
Follow these instructions to setup the Amazon AWS S3 cloud storage service for images attached to Kudo posts:
- Create an AWS S3 account.
- Setup a Amazon S3 Bucket.
- Set the
AWS_S3_HOST_NAME,AWS_S3_REGION,AWS_S3_BUCKET,AWS_S3_BUCKETandAWS_SECRET_ACCESS_KEYenvironment variables. - Restart the server.
The Kudos-o-Matic can automatically send mail notifications when the following events occur:
- When a user joins the Kudos-o-Matic platform.
- When a user receives Kudos (only this user will receive the notification).
- When a Kudo goal is reached.
- Weekly summary mail.
- User account related emails (confirmation, password reset, etc.)
To use Mailhog for local usage follow the instructions on their GitHub repository
You can also update the configuration (development.rb) if you don't want to use Mailhog. Set and use the MAIL_USERNAME, MAIL_PASSWORD and MAIL_ADDRESS environment variables for this.
See here.
The project is build using GitHub actions and deployed to Heroku.
Every commit to the develop branch is deployed to staging
Every commit to the master branch is deployed to production
A diagram of the models is available here.
A KudosMeter is the base of the Kudos-o-Matic system. It groups Goals together and connects them to Posts.
A Team is the tenant where you and your colleagues give and collect Kudos
A Goal depends on a KudosMeter. To set and see a Goal on the Kudo Meter you need to associate the Goal with the current KudosMeter. A Goal is a common reward for the organization (for example: paintball) that will be organized if the defined Kudo threshold is exceeded.
A Post depends on a KudosMeter. A User can reward another User for a good deed by creating a Kudo Post.
A Vote depends on a Post (votable) and a User (voter). A User can like and unlike Posts.
A User can create a Kudo Post to reward another User for a good deed. Users work together to achieve common Kudo Goals.
- Fork the repository.
- Create your feature branch (
git checkout -b my-new-feature). - Commit your changes (
git commit -am 'Add some new feature'). - Push to the branch (
git push origin my-new-feature). - Create a new Pull Request.
- Ensure the bug was not already reported.
- If you are unable to find an open issue addressing the problem, open a new one.
- Be sure to include a title and a clear description, as much relevant information as possible, and a code example or an executable test case demonstration of the expected behavior that is not occurring.