Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

This project is archived and is in readonly mode.

Ignoring Gemfile.lock

#4150

Really simple think. In autogenerated .gitignore file there is line with ".bundle". If we ignore "bundle noise" out of box I think we can also add Gemfile.lock to ignores.

Reported by Łukasz Strzałkowski · March 10th, 2010 @ 07:49 PM

State: invalid
Milestone: 3.0.2
Assigned to: nobody
Importance: Low

Activity

  1. Yehuda Katz (wycats)
    Yehuda Katz (wycats)
    • Milestone cleared.
    • State changed from new to invalid

    As per the bundler README, Gemfile.lock should be included in version control.

    March 27th, 2010 @ 09:30 AM

  2. ronin-45124 (at lighthouseapp)
    ronin-45124 (at lighthouseapp)
    • Importance changed from to Low

    hm sure? from my point of view i thought the lock file represent also the current environment. i use diffrent database gems in development (sqlite) and production (pg). the "problem" is that bundler does ignore the current environment and i have to use 'bundle install --without=production' on my development environment and get a lock file. but on production i will have a diffrent lock file (without sqlite, but with pg)

    either i havent understand bundler or check in the lock file is a bad idea...

    July 28th, 2010 @ 11:07 AM

  3. Jeremy Kemper