Thanks Oren, it's useful to know how it works and what the best thing
to do is.
cheers,
DAZ
On Oct 26, 7:58 pm, Oren Teich o...@heroku.com wrote:
Both are correct. Just add a blank line and we'll pull the latest
version if you havn't specified.
Best practice is to pin all versions to
Hi,
Sinatra upgraded to version 1.1 yesterday. Is this version available
on Heroku and how do I update current apps that are using Sinatra to
the new version?
cheers,
DAZ
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send
Simply put it in your .gems or Gemfile and you'll be all set.
Oren
On Tue, Oct 26, 2010 at 5:58 AM, DAZ daz4...@gmail.com wrote:
Hi,
Sinatra upgraded to version 1.1 yesterday. Is this version available
on Heroku and how do I update current apps that are using Sinatra to
the new version?
Thanks Oren,
I changed my .gems file to say
sinatra --version 1.1
instead of just
sinatra
Is there any way of forcing Heroku to always go and look for the
latest gems without having to specify a version number?
cheers,
DAZ
On Oct 26, 4:30 pm, Oren Teich o...@heroku.com wrote:
Simply put it
By not specifiying a gem version we will always pull the latest
version when you change your .gems/gemfile. This is a bad idea
however, as your app could randomly break if for example sinatra 2.0
comes out and changes an API you depend on.
Oren
On Tue, Oct 26, 2010 at 11:35 AM, DAZ
thanks Oren,
I've tested it locally, so was happy to update. So would I have to
just change the .gems file with something trivial to 'force' an
update?
Or are you saying that best practice is to always specify version
numbers?
cheers,
DAZ
On Oct 26, 7:40 pm, Oren Teich o...@heroku.com wrote:
Both are correct. Just add a blank line and we'll pull the latest
version if you havn't specified.
Best practice is to pin all versions to prevent nasty surprises.
Oren
On Tue, Oct 26, 2010 at 11:53 AM, DAZ daz4...@gmail.com wrote:
thanks Oren,
I've tested it locally, so was happy to update.
