Gemfile.lock vs Gemfile


(Steve Wills) #1

Just curious, reading this:

That’s fine, it’s of course your right to support or not support whatever you want.

Was wondering though, since I’ve seen other apps where you could freely delete the Gemfile.lock and it would be re-created using the gems that were installed that satisfied the Gemfile and everything would be fine, why that’s not the case with Discourse? I think other than this issue with sprockets-rails, that should be the case. Would you accept a patch to add gem 'sprockets-rails', '~> 2.0.1' to the Gemfile? Or other patches to update things, such as bumping the fog gem to 1.23?


(Sam Saffron) #2

I usually try to add specific versions in, but missed this one.

We should get it working on latest regardless


Updating some Gems to latest
(Steve Wills) #3

That’d be great. Having Discourse working with the latest version of all the gems it uses (and being explicit about where it doesn’t) will make my eventual goal of having a FreeBSD port of Discourse a lot easier.


(Jeff Atwood) #4

You mean FreeBSD running Docker, right… right?


(Steve Wills) #5

Yeah! Sure! Ok, you got me, it’s really in a jail.