Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

542 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Online Risk Manager

EO principles respected here DevOps By Rultor.com We recommend RubyMine

rake PDD status Test Coverage Maintainability Hits-of-Code Availability at SixNines

This is an online risk manager, where you register all know risks in your project, assign probabilities and impacts, and then create mitigation and avoidance plans for them. Using this information the system generates an agenda of the most critical tasks for you.

Read this blog post, it explains it all in details: 0rsk.com: Cause + Risk + Effect.

Here you can find some inspiration: yegor256/awesome-risks.

It's free for everybody.

How to contribute

Read these guidelines. Make sure your build is green before you contribute your pull request.

Prerequisites

You will need:

Database setup

The build auto-starts a local PostgreSQL instance and applies Liquibase migrations. No manual setup is required for development.

For a custom database, set the DATABASE_URL environment variable:

export DATABASE_URL=postgres://user:pass@localhost:5432/0rsk

Alternatively, create target/pgsql-config.yml (auto-generated by bundle exec rake when using the default local setup).

Configuration

Running the app directly with ruby 0rsk.rb (outside of tests, where RACK_ENV=test skips this) reads GitHub OAuth, Sentry, and Telegram settings from config.yml at the repository root, if that file exists. Copy config.sample.yml to config.yml and fill in real values to enable GitHub login and Telegram notifications:

cp config.sample.yml config.yml

Without config.yml, the app still starts, using placeholder GitHub credentials.

Quick start

bundle install
bundle exec rake

This will: start PostgreSQL → apply Liquibase migrations → run tests → lint (RuboCop, ESLint, xcop).

If it's clean and you don't see any error messages, submit your pull request.

To run a single unit test, first start the server:

bundle exec rake run

Then, in another terminal:

ruby test/test_risks.rb -n test_adds_and_fetches

To test in your browser, open http://localhost:9292. Use http://localhost:9292?glogin=test for a test login.

Should work.

About

Online Risk Manager

Topics

Resources

Stars

24 stars

Watchers

2 watching

Forks

Releases

Used by

Contributors

Languages