Go to file
Mark Moser e516cceb1b fixing model test 2018-12-07 13:10:49 -06:00
app Blogs 2018-11-11 18:38:16 -06:00
bin init 2018-11-09 20:52:04 -06:00
config Blogs 2018-11-11 18:38:16 -06:00
db Blogs 2018-11-11 18:38:16 -06:00
lib/tasks setup and rubocop corrections 2018-11-10 11:32:05 -06:00
public init 2018-11-09 20:52:04 -06:00
test fixing model test 2018-12-07 13:10:49 -06:00
vendor init 2018-11-09 20:52:04 -06:00
.editorconfig setup and rubocop corrections 2018-11-10 11:32:05 -06:00
.gitignore Blogs 2018-11-11 18:38:16 -06:00
.rubocop.yml setup and rubocop corrections 2018-11-10 11:32:05 -06:00
.ruby-version init 2018-11-09 20:52:04 -06:00
Gemfile Users & Auth 2018-11-10 20:34:11 -06:00
Gemfile.lock Users & Auth 2018-11-10 20:34:11 -06:00
Guardfile setup and rubocop corrections 2018-11-10 11:32:05 -06:00
README.md setup and rubocop corrections 2018-11-10 11:32:05 -06:00
Rakefile setup and rubocop corrections 2018-11-10 11:32:05 -06:00
config.ru setup and rubocop corrections 2018-11-10 11:32:05 -06:00
rebuild-dev-db.sh setup and rubocop corrections 2018-11-10 11:32:05 -06:00
user_stories.md Blogs 2018-11-11 18:38:16 -06:00

README.md

MicroBlogger

This is a Rails 5.2.n API stack.

Local dev setup

Be sure to have ruby (2.5.n) installed. RVM is recommended to manage ruby. This dev stack uses guard for rapid style and test feedback. It is strongly recommended to have it running for every dev change/session.

Initial setup

  • rvm install ruby-2.5.1
  • bundle install
  • set up application.yml
    • copy config/application.yml.sample to config/application.yml
    • edit values as needed
  • rake db:create
  • rake db:migrate
  • rake db:fixtures:load

There is a shell script in the root that will rebuild both the local dev and test databases which executes the last three setup steps: ./rebuild-dev-db.sh

Currently fixture files are used to seed local and test dev instead of the rake db:seed pattern.

dev session

  • bundle exec guard
  • do work until tests pass.
  • quit to exit guard

The guard config file is /Guardfile.

With (almost) every file save, associated tests to that file are ran, if successful the whole suite is then executed.

After the test suite rubocop kicks off with auto-correction flags.

Finally simple cover reports are updated.

other notes