Common dependencies and helpers for use in CodeCare client applications
Add this line to your application's Gemfile under group :development, :test do
gem "code_care", git: "[email protected]:reinteractive/CodeCareGem.git", branch: "master"And then execute:
$ bundle install
# If using vendored gems then also run:
$ bundle pack --all
run bundle exec rails g code_care:setup at the root of the application
Here is a list of gems that are included as dependencies. If they are already present in your Gemfile you can remove them when adding code_care.
Note: Dependencies all have a >= 0 version, if you need to specify a specific version you can do this in your app's Gemfile
A new bin/cron_monitor script is provided that will email the output of failed cron jobs, generally rake tasks. For example:
bundle exec bin/cron_monitor rake task
Cron monitor requires the following environment variables to be set:
CRON_MONITOR_EMAIL_TOCRON_MONITOR_EMAIL_FROMSMTP_HOSTSMTP_PORTSMTP_USERNAMESMTP_PASSWORD
If a config/schedule.rb file exists, a new bundled_rake_sentinel job type is added which can be used to run rake tasks via cron_monitor
Note: whenever is not included as a dependency and is not required for the codecare gem
If a .travis.yml file exists, it will be updated to run brakeman and bundle-audit on each run.
Warnings will not be counted as a build failure unless they are run as a cron (i.e. scheduled) run.
Basic setup for SimpleCov will be added to spec_helper.rb.
coverage will also be added to the .gitignore
If a Guardfile does not exist then one will be created by running bundle exec guard init rspec.
This creates a default using the guard-rspec gem.