Update rails & ruby

[bsp3ars]

Resolves #157

Here is the current status of the branch:

• Ruby and Rails have been updated to 3.0.4p208 and 6.0.6 respectively
• The code works in development mode
• One feature test is kinda wonky, specifically I couldn't get it to wait long enough to find an id after a page change (spec/features/create_admin_spec.rb lines 36-38)
• The capistrano deploy to QA is failing due to ArgumentError: Missing secret_key_base for 'production' environment, set this string with rails credentials:edit

Recent Troubleshooting Steps:

1. I added the secret_key_base to the .env.production.local on QA but it didn't resolve the issue
2. Started to look into the Rails 6 changes regarding how secret_key_base is stored and referenced

Other things of note:

• You can unset the bundle installation location (vendor/bundle) if you accidentally set it via: bundle config unset path
• I used the following sites for reference when upgrading Ruby and Rails (https://guides.rubyonrails.org/upgrading_ruby_on_rails.html) (https://selleo.com/blog/how-to-upgrade-to-rails-6)
• You can use the d option to show the difference when using the bundle update rails command

[crowesn]

• Corrected .env filename in Capistrano config
• add rbenv config to :production deploy config
• Created new secret key

[crowesn]

@lisa3711 @scherztc
this should be ready to go.

[scherztc]

Coveralls : Coverage report generated for RSpec to /Users/scherztc/Workspaces/aaec/coverage. 641 / 697 LOC (91.97%) covered.

[scherztc]

The main thing that wasn't well documented and therefore unable to test:

1. How do I login as the admin user to see all of the publications?
2. Why Webpacker?

[scherztc]

We ran the test suite locally, read through the code and made comments, and spun up the application, reviewed circleci, and clicked through the available features.

We still need to do a test deploy with Capistrano.

[scherztc]

We ran the test suite locally, read through the code and made comments, and spun up the application, reviewed circleci, and clicked through the available features.

We still need to do a test deploy with Capistrano.