fourfingerz / dontblazy Goto Github PK

The app is using SQLite on development and test environment, and Postgres in production. It is a good practice to keep the environments as similar as possible in order to avoid "works on my machine (tm)" cases.

SQLite is very easy to setup but you can use the best features from Postgres or rely that both databases may have the same dataset with this configuration.

Here is one topic with some reasons to change everything to Postgres http://stackoverflow.com/questions/10859186/sqlite-in-development-postgresql-in-production-why-not

Hey @Fourfingerz, whats up?

I'm setting this project on my machine and I have 4 failing tests:

rspec ./spec/features/typical_usage_spec.rb:67 # User lands on landing page for the first time ever adds a new micropost with two associated recipients and began delayed job
rspec ./spec/models/micropost_spec.rb:78 # Micropost micropost#check_in will properly check in a micropost depending on whether or not a user checked in
rspec ./spec/models/user_spec.rb:14 # User will not allow users to make another account with the same phone number
rspec ./spec/models/user_spec.rb:71 # User user#create_status_sms creates the proper tasks map for persistance and proper sms message

Are they failing on you machine?

Hey @Fourfingerz, can you add the code climate badge on readme ?