Project

General

Profile

Actions

Feature #13124

closed

Add Gemfile.lock for production-ready deployment

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

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Gems support
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

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

Is duplicate of Redmine - Defect #10683: Missing Gemfile.lock in latest 1.4 stable branchClosed

Actions
Actions #1

Updated by Etienne Massip about 11 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.

Actions #2

Updated by Toshi MARUYAMA about 11 years ago

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

Actions #3

Updated by Etienne Massip about 11 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?

Actions #4

Updated by Jean-Philippe Lang about 11 years ago

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

Already discussed in #10683.

Actions

Also available in: Atom PDF