swanson / stringer

97%

master: 97%

LAST BUILD ON BRANCH update-vulnerable-gems

branch: update-vulnerable-gems

CHANGE BRANCH

x

Reset

• update-vulnerable-gems
• 2.3.0-upgrade
• add-migration-to-fix-unprintables
• backbone
• dependabot/bundler/nokogiri-1.11.4
• dependabot/bundler/rack-2.2.3
• experiment-with-workers
• fever-api
• fix-old-mac-line-endings
• gp-sprockets
• gp-tests
• gp-title-summary
• gp-upgrade
• master
• pr/199
• pr/294
• pr/400
• rf-app_spec
• rf-ar_up
• rf-assets_specs
• rf-bundle_cleanup
• rf-bundle_up
• rf-bundler
• rf-change_password_specs
• rf-coverage
• rf-coveralls_reborn
• rf-feed_repo_specs
• rf-feeds_tests
• rf-fetch_feed_fix
• rf-fix_delayed_job
• rf-fix_flake
• rf-group_repo_spec
• rf-heroku_spec
• rf-more_specs
• rf-no_sqlite
• rf-puma
• rf-query_fix
• rf-ruboall
• rf-rubocop_all
• rf-schema
• rf-story_repo_spec
• rf-story_repo_specs
• rf-story_specs
• rf-unicorn_up
• rf-user_specs
• rspec-3
• rubocop-1
• rubocop-lint
• rubocop-metrics
• rubocop-performance
• rubocop-style
• travis-fix
• vk-activerecord-tasks-databasetasks
• vk-bump-activerecord
• vk-bump-loofah
• vk-bump-nokogiri
• wbr-tags

Build # 664

Build Type

push

travis-ci

Committed by Koronen

Commit Message

Update config/database.yml to use DATABASE_URL in production

The previous configuration would result in the following type of error on
Heroku.

    app[web.1]: /.../connection_adapters/postgresql_adapter.rb:888:in
      `initialize': could not connect to server: No such file or directory (PG::ConnectionBad)
    app[web.1]:    Is the server running locally and accepting
    app[web.1]:    connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

From
<https://github.com/rails/rails/blob/4-1-stable/activerecord/CHANGELOG.md#rails-410-april-8-2014>:

> Currently Active Record can be configured via the environment variable
> `DATABASE_URL` or by manually injecting a hash of values which is what Rails
> does, reading in `database.yml` and setting Active Record appropriately.
> Active Record expects to be able to use `DATABASE_URL` without the use of
> Rails, and we cannot rip out this functionality without deprecating.

The `DATABASE_URL` environment variable should contain all the settings now
removed from `config/database.yml`.

Run Details

2230 of 2292 relevant lines covered (97.29%)

11.29 hits per line