department-of-veterans-affairs/SCIInterim

Name: SCIInterim

Owner: Department of Veterans Affairs

Description: null

Created: 2015-04-24 22:02:51.0

Updated: 2016-02-02 05:15:25.0

Pushed: 2016-08-03 00:57:59.0

Homepage: null

Size: 3945

Language: Ruby

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

SCI Interim

Data entry and records application for Spinal Care Injuries at Veterans Affairs

How to get started hacking

There are 3 steps:

1. Setting up postgres
2. Setting up rails
3. [options] Add some fake data.

postgres Setup

Install the postgres binary somehow. For Mac, use Homebrew and run brew install postgres. For Linux, use your package manager. You're on your own for windows.

If this is the inital setup of postgres, you must create the database files, create the initial user, etc. Executing

 pg:first_run

will do all of the above including seeding the database. Notice the pg is not db.

If this is not the first run, then you may need to start/stop the database process by doing some combination of

 pg:start
 pg:stop

This rake script runs a postgres instance under your current user. If you have a system postgres daemon, parts of this might not work.

Rails Setup

• bundle install
• rails s
• guard # Use this to auto-run affected specs as you change code.

Rails Setup

If you want to create fake data, there is a rake task. Run

 app:seed_fake

Useful Links

Install PostgreSQL: https://www.codefellows.org/blog/three-battle-tested-ways-to-install-postgresql Install Ruby On Rails on Mac: http://railsapps.github.io/installrubyonrails-mac.html

Issues

We are currently using labels and milestones from tracking requirements and bugs during sprint cycles. Label are for priority; milestone for sprint cycle

• To search Issues by piroirty and milestone, use example: label:p2 milestone:[0]pre-testing
• Priority Definition:
  • P0 - Must Have
  • P1 - Should Have
  • P2 - Could Have
  • P3 - Wish List
• Sprint names: For now, we will use descriptive names like [0]pre-testing, [1]alpha-launch. In the future, we may revert to using m0, m1, m2, etc. Let's see what works better for communicating sprint cycles.
• Status:
  • status:not-started
  • status:in-progress
  • status:help-wanted
  • status:wont-fix
  • status:done
• Task Size:
  • 1: A few Minutes
  • 2: Half a Day
  • 3: One Day
  • 5: We have no idea how long this will take!