News for hackers. Stuff that matters.

A comment on Ruby deploys temporarily disabled. Parent comment

Re:Ruby deploys temporarily disabled by sumone4life on Wednesday January 30, 2013 @02:23PM (#5141209)
They still allow you to deploy you just have to explicitly set a variable in the deploy command so they know you are aware whats going on
[ Parent | on HN ]
Re:Ruby deploys temporarily disabled by tlrobinson on Wednesday January 30, 2013 @02:26PM (#5141220)
The point was unless you also previously cached all your gems somewhere you'd have to deploy using potentially compromised gems from rubygems.
[ Parent | on HN ]
Re:Ruby deploys temporarily disabled by splatcollision on Wednesday January 30, 2013 @02:42PM (#5141314)
Is this safe if you haven't changed any gems since the last deploy? I have a bugfix that I would like to deploy...
[ Parent | on HN ]
Re:Ruby deploys temporarily disabled by ikawe on Wednesday January 30, 2013 @02:57PM (#5141411)
Heroku runs bundle install on deploy, so it's not safe until all your gems (and their dependencies in gemfile.lock) are cleared.
[ Parent | on HN ]