- It's unneeded and overly verbose - sass-rails recently deprecated this suffix, rails/sass-rails@d355de9
The `NEW_RELIC_AGGRESSIVE_KEEPALIVE` environment variable was was added in #440 to reduce New Relic's memory consumption for idling applications on Heroku. As of version 3.9.8, New Relic defaults this setting to `true`, so it's no longer necessary to set it explicitly. From the New Relic [CHANGELOG]: > Reduced memory usage for idling applications > > Idling applications using the agent could previously appear to leak > memory because of native allocations during creation of new SSL > connections to our servers. These native allocations didn't factor > into triggering Ruby's garbage collector. > > The agent will now re-use a single TCP connection to our servers for > as long as possible, resulting in improved memory usage for > applications that are idling and not having GC triggered for other > reasons. Related commit: newrelic/rpm@e04d5ce [CHANGELOG]: https://github.com/newrelic/rpm/blob/master/CHANGELOG [fixes #535]
https://relishapp.com/rspec/rspec-mocks/v/3-0/docs/verifying-doubles/partial-doubles "When the verify_partial_doubles configuration option is set, the same argument and method existence checks that are performed for object_double are also performed on partial doubles. You should set this unless you have a good reason not to. It defaults to off only for backwards compatibility."
* Include 2015 in the copyright. * Update logo to use new HTTPS version. * Change header from "Credits" to "About thoughtbot". * Move "thank you" to contributors section. * Make "About thoughtbot" the last thing in the README, with the copyrights grouped closer to the LICENSE information. * Link to LICENSE. * Make the community link more obvious that we have other projects. * Finish with a CTA to hire us. * Include `utm_source` codes to improve tracking.
* Configure ActiveJob's queue adapter to DelayedJob * This removes the step to manually configure the `ActiveJob`'s adapter. * Use `:inline` queue adapter in test environment to execute the background jobs immediately * Remove the background jobs template because it's not necessary anymore [fixes #520]
At the moment, in order to use the deploy script, an user must set as executable. This sets the file as executable after creating it, following the logic employed for the `bin/setup` script. It also adds tests for both of the files, in order to prevent regression