What appears to be happening is Heroku only has version 1.9.7 of bundler, but Pakyow requires a version greater than 1.10. However, when I deploy a brand new app it looks like Heroku is bundling with 1.9.7 and doesn't try to install the version that Pakyow requires.
git push heroku master
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 378 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote: -----> Using set buildpack heroku/ruby
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rack
remote: -----> Using Ruby version: ruby-2.2.4
remote: -----> Installing dependencies using bundler 1.9.7
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Using rake 10.5.0
remote: Using addressable 2.4.0
remote: Using concurrent-ruby 1.0.0
remote: Using htmlentities 4.3.4
remote: Using mime-types 2.99.1
remote: Using mini_portile2 2.0.0
remote: Using bundler 1.9.7
remote: Using pakyow-support 0.10.2
remote: Using rack 1.6.4
remote: Using redis 3.2.2
remote: Using websocket_parser 1.0.0
remote: Using puma 3.0.1
remote: Using css_parser 1.3.7
remote: Using mail 2.6.3
remote: Using nokogiri 126.96.36.199
remote: Using pakyow-core 0.10.2
remote: Using premailer 1.8.6
remote: Using pakyow-presenter 0.10.2
remote: Using pakyow-realtime 0.10.2
remote: Using pakyow-rake 0.10.2
remote: Using pakyow-mailer 0.10.2
remote: Using pakyow-ui 0.10.2
remote: Using pakyow-test 0.10.2
remote: Using pakyow 0.10.2
remote: Bundle complete! 4 Gemfile dependencies, 24 gems now installed.
remote: Gems in the groups development and test were not installed.
remote: Bundled gems are installed into ./vendor/bundle.
remote: Bundle completed (0.28s)
remote: Cleaning up the bundler cache.
remote: ###### WARNING:
remote: You have not declared a Ruby version in your Gemfile.
remote: To set your Ruby version add this line to your Gemfile:
remote: ruby '2.2.4'
remote: # See https://devcenter.heroku.com/articles/ruby-versions for more information.
remote: ###### WARNING:
remote: No Procfile detected, using the default web server (webrick)
remote: -----> Discovering process types
remote: Procfile declares types -> (none)
remote: Default types for buildpack -> console, rake, web
remote: -----> Compressing...
remote: Done: 19.5M
remote: -----> Launching...
remote: Released v5
remote: https://guarded-castle-87151.herokuapp.com/ deployed to Heroku
remote: Verifying deploy... done.
fb51be0..dc9b1e2 master -> master
Scratching my head right now. I suppose it could be a difference in how Heroku handles Windows vs non-Windows, but I don't have a Windows machine to test that out. I do know of a few people who have successfully deployed a Pakyow app to Heroku from Windows in the recent past. I might reach out to them to see if they can help here.
Another clue is that the
Procfile is optional -- a Pakyow app will run on Heroku without it. Just to make sure you're using the right stack, what's the result of
heroku info? Here's mine:
Dynos: web: 1
Git URL: https://git.heroku.com/guarded-castle-87151.git
Repo Size: 60 KB
Slug Size: 19 MB
Web URL: https://guarded-castle-87151.herokuapp.com/