Can i delete gemfile.lock

If you remove the lock file it will either use the local gem if present else download the latest version of the gems. Python Javascript Linux Cheat sheet Contact. It is recommended to keep the Gemfile. My Gemfile and Gemfile. Sign in to your account. If you were attempting to accomplish a task, what was it you were attempting to do?

What did you expect to happen? What was the actual behavior? Our bundle-generated Gemfile. Our Gemfile. When using an identical except for the xmingw32 line Gemfile. In other words, to reproduce:. We believe our original, cross-platform Gemfile.

One possible fix would be to replace the logic that detects presence of windows in Gemfile. Lines to in 84e9b6e. Is it okay to delete Gemfile. We're on Rails 3. Improve this question. Crashalot Crashalot Consider using bundle update rails instead to update only the gems you need to change. Add a comment. Active Oldest Votes. If you're using entries like: gem "rails" Then you'll get the latest rails gem, whatever that might be.

If you're using entries like: gem "rails", "3. Improve this answer. It's ok to delete Gemfile. Tom Hert 2 2 gold badges 10 10 silver badges 31 31 bronze badges. AnthonyAlmighty AnthonyAlmighty 7 7 bronze badges. Keep in mind that while your Gemfile lists only three gems with varying degrees of version strictness , your application depends on dozens of gems, once you take into consideration all of the implicit requirements of the gems you depend on.

This is important: the Gemfile. Specifying exact versions of the third-party code you depend on in your Gemfile would not provide the same guarantee, because gems usually declare a range of versions for their dependencies. The next time you run bundle install on the same machine, bundler will see that it already has all of the dependencies you need and skip the installation process. Do not check in the. Those files are specific to each particular machine and are used to persist installation options between runs of the bundle install command.

Bundler can run without connecting to the internet or the RubyGems server if all the gems you need are present in that folder and checked in to your source control. This is an optional step and not recommended due to the increase in size of your source control repository. When your co-developers or you on another machine check out your code, it will come with the exact versions of all the third-party code your application used on the machine that you last developed on in the Gemfile.

Instead, it will install all of the same gems that you used on the original machine. In other words, you don't have to guess which versions of the dependencies you should install. Even if the Rack team releases rack 1. This relieves a large maintenance burden from application developers because all machines always run the exact same third-party code.

Of course, at some point, you might want to update the version of a particular dependency your application relies on. For instance, you might want to update rails to 4. Importantly, just because you're updating one dependency, it doesn't mean you want to re-resolve all of your dependencies and use the latest version of everything.

In our example, you only have three dependencies, but even in this case, updating everything can cause complications. To illustrate, the rails 4. Let's assume that the rails 4. However, we didn't specifically ask to update rack-cache , which may not be compatible with rack 1.