Feature #13124

Add Gemfile.lock for production-ready deployment

Added by Stefano A. about 7 years ago. Updated about 7 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Gems support
Target version:-


It would be great to add a Gemfile.lock file so that bundler can use the --deployment flag to install Redmine on a production server. At the moment the file is missing and trying to install redmine without admin rights fails if not using the --path option to specify a custom location for gems because it tries to install them system-wide and also asks for the root password to continue.

Related issues

Duplicates Redmine - Defect #10683: Missing Gemfile.lock in latest 1.4 stable branch Closed


#1 Updated by Etienne Massip about 7 years ago

  • Category set to Gems support
  • Target version set to Candidate for next major release

I do agree, Bundler documentation itself stipulates that Gemfile.lock should be released.

#2 Updated by Toshi MARUYAMA about 7 years ago

How do we treat plugins?
Many plugins have own Gemfile.

#3 Updated by Etienne Massip about 7 years ago

  • Target version deleted (Candidate for next major release)

You're right. This and the database adapter and Gemfile.local things, probably too much for a target version.

We could release a Gemfile.lock.mysql file and .postgresql, .mssql (sqlite is not wished in production) for the kind of case described here?

#4 Updated by Jean-Philippe Lang about 7 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Already discussed in #10683.

Also available in: Atom PDF