Let us know how we can contact you.
We'll respond shortly.
By Tim Labeeuw • January 08, 2013
There’s really no good reason for them to do this.
Agree, there is no good reason for that.
I believe the argument is associated with packaged gems (vendor/cache) bundled with your application.
The other is incorrect versioning (having a Windows gem like 220.127.116.11 while the non-Windows is 1.2.1)
I’m still pinging them to fix the heroku toolbelt, leave alone the buildpack :(
Heroku uses unix boxes. Windows lockfiles can’t reliably be installed onto unix boxes. That’s a pretty big reason.
Gemfile.lock can support different versions on different platforms. Bundler handles this just fine. Heroku should just use the bundled versions for the platform it is on, and ignore the windows ones.
I’ve been having a lot of problems with the Heroku Toolbelt gaining access. It’s just one problem after another, and no help at all from the support staff. On the other hand, I tried a friend’s macbook and got it working within seconds.
Want a weekly window into what's happening in the software industry? Get stories and news from Pivotal and our customers delivered to your inbox.