I'm trying to upload a Rails 5.2 Application in Heroku however, I'm unable to deploy it. I am using Rails 5.2 and Ruby ruby '2.5.1'
Below are the logs request your kind assistance.
Thanks!
Peeyushs-MacBook-Air: peeyushverma$ git push heroku master
Counting objects: 1642, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (1588/1588), done.
Writing objects: 100% (1642/1642), 8.01 MiB | 257.00 KiB/s, done.
Total 1642 (delta 684), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.5.1
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from http://rubygems.org/...........
remote: Fetching gem metadata from https://rubygems.org/...........
remote: Fetching version metadata from http://rubygems.org/..
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from http://rubygems.org/.
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Could not find rails-assets-jquery-3.3.1 in any of the sources
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from http://rubygems.org/...........
remote: Fetching gem metadata from https://rubygems.org/...........
remote: Fetching version metadata from http://rubygems.org/..
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from http://rubygems.org/.
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Could not find rails-assets-jquery-3.3.1 in any of the sources
remote:
remote: !
remote: ! Failed to install gems via Bundler.
remote: !
remote: ! Push rejected, failed to compile Ruby app.
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to.
remote:
To https://git.heroku.com/.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/.git'
In your assets/javascripts/application.js, try to replace //=require jquery with //=require jquery3
I think you should remove //=require jquery or //=require jquery3 from assets/javascripts/application.js and use rails default //= require rails-ujs and try to deploy again.
Related
I have my project ruby on rails in windows.
source 'http://rubygems.org'
ruby '2.5.7'
gem 'rails', '~> 5.0.0'
When I do git push heroku master, heroku throws the following errors
Compressing objects: 100% (140/140), done.
Writing objects: 100% (145/145), 843.56 KiB | 5.27 MiB/s, done.
Total 145 (delta 88), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Building on the Heroku-18 stack
remote: -----> Determining which buildpack to use for this app
remote: -----> Ruby app detected
remote: -----> Installing bundler 2.2.33
remote: -----> Removing BUNDLED WITH version in the Gemfile.lock
remote: -----> Compiling Ruby/Rails
remote:
remote: ###### WARNING:
remote:
remote: Your app was upgraded to bundler 2.2.33.
remote: Previously you had a successful deploy with bundler 2.2.21.
remote:
remote: If you see problems related to the bundler version please refer to:
remote: https://devcenter.heroku.com/articles/bundler-version#known-upgrade-issues
remote:
remote:
remote: -----> Using Ruby version: ruby-2.5.7
remote:
remote: ###### WARNING:
remote:
remote: Removing `Gemfile.lock` because it was generated on Windows.
remote: Bundler will do a full resolve so native gems are handled properly.
remote: This may result in unexpected gem versions being used in your app.
remote: In rare occasions Bundler may not be able to resolve your dependencies at all.
.....
remote: Using uglifier 4.2.0
remote: Using aws-sigv4 1.4.0
remote: Using daru 0.1.6
remote: Fetching bootsnap 1.10.1
remote: --- ERROR REPORT TEMPLATE -------------------------------------------------------
remote:
remote: ```
remote: ArgumentError: wrong number of arguments (given 4, expected 1)
remote: /tmp/build_e0d3fad0/vendor/bundle/ruby/2.5.0/gems/psych-4.0.3/lib/psych.rb:323:in `safe_load'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/safe_yaml.rb:31:in `safe_load'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:496:in `block (2 levels) in read_checksums'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:495:in `wrap'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:495:in `block in read_checksums'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package/tar_reader.rb:116:in `seek'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:494:in `read_checksums'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:547:in `block (2 levels) in verify'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package/tar_reader.rb:29:in `new'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:546:in `block in verify'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package/file_source.rb:30:in `open'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package/file_source.rb:30:in `with_read_io'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:545:in `verify'
remote: /tmp/build_e0d3fad0/vendor/ruby-2.5.7/lib/ruby/2.5.0/rubygems/package.rb:526:in `spec'
remote: /tmp/build_e0d3fad0/vendor/bundle/ruby/2.5.0/gems/bundler-2.2.33/lib/bundler/rubygems_integration.rb:250:in `spec_from_gem'
...
remote: <No /tmp/build_e0d3fad0/Gemfile.lock found>
remote: ```
remote:
remote: --- TEMPLATE END ----------------------------------------------------------------
remote:
remote: Unfortunately, an unexpected error occurred, and Bundler cannot continue.
remote:
remote: First, try this link to see if there are any existing issue reports for this error:
remote: https://github.com/rubygems/rubygems/search?q=wrong+number+of+arguments+%28given+4%2C+expected+1%29&type=Issues
remote:
remote: If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.
remote:
remote: !
remote: ! Failed to install gems via Bundler.
remote: !
remote: ! Push rejected, failed to compile Ruby app.
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to tksoft.
remote:
To https://git.heroku.com/tksoft.git
! [remote rejected] fran -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/tksoft.git'
I already did a lot of things, but everything not working, For example:
Created a new branch and push from this
Modify Gemfile to put de same version bundler the heroku, and PLATFORMS
ruby
x64-mingw32
x86_64-linux
Set buildpacks in heroku to the last version of deploy
Thanks for your help
Looks like there is a problem in psych gem, specifically in the safe_load method that got some breaking changes. Windows is not the problem here.
It was discussed in these questions: here and there and in the issue.
Until issue is not fixed I'd suggest to manually set the version of psych to older 3.3.2 in Gemfile.
I try to push my project on heroku and error message pop outs
git push heroku master
remote: -----> Building on the Heroku-18 stack
remote: -----> Using buildpack: heroku/ruby
remote: -----> Ruby app detected
remote: -----> Installing bundler 2.2.11
remote: -----> Removing BUNDLED WITH version in the Gemfile.lock
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.6.3
remote: -----> Installing dependencies using bundler 2.2.11
remote: Running: BUNDLE_WITHOUT='development:test' BUNDLE_PATH=vendor/bundle BUNDLE_BIN=vendor/bundle/bin BUNDLE_DEPLOYMENT=1 bundle install -j4
remote: Fetching gem metadata from https://rubygems.org/............
remote: **Your bundle is locked to mimemagic (0.3.5), but that version could not be found**
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of mimemagic (0.3.5) has removed it. You'll need to update
remote: your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
remote: in order to install.
remote: Bundler Output: Fetching gem metadata from https://rubygems.org/............
remote: Your bundle is locked to mimemagic (0.3.5), but that version could not be found
remote: in any of the sources listed in your Gemfile. If you haven't changed sources,
remote: that means the author of mimemagic (0.3.5) has removed it. You'll need to update
remote: your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
remote: in order to install.
remote:
remote: !
remote: ! Failed to install gems via Bundler.
remote: !
remote: ! Push rejected, failed to compile Ruby app.
remote:
remote: ! Push failed
remote: !
I guess the problem is caused by rails gem mimemagic's version is out of date so I try to update to the latest version, it still doesn't work.
Here's my ruby, Rails, mimemagic version
ruby -v
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
rails -v
Rails 6.1.3.1
bundle info mimemagic
* mimemagic (0.4.3)
information in Gemfile
gem 'rails', '~> 6.1', '>= 6.1.0'
gem 'bundler', '~> 2.2', '>= 2.2.1.1'
gem 'mimemagic', '~> 0.4.3'
in Gemfile.lock
mimemagic (~> 0.4.3)
run bundle update mimemagic worked for me
Change version of mimemagic to 0.3.10 in your Gemfile
Mimemagic seems to be experiencing updates? hopefully will be fixed soon. Try changing mimemagic to previous version for now..
Gemfile:
gem 'mimemagic', '~> 0.3.10'
Running bundle update will automatically update every dependency on your app to the latest version
I finished setting up OAuth in my app, but I can't seem to push to Heroku. There is a gem dependency that was installed (and everything works locally), but Heroku rejects the push.
I have tried deleted my .lock file, .bundle, and have tried bundle update as well. Heroku will not accept the push
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.5.3
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Could not find multipart-post-2.0.0 in any of the sources
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.17.1). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Could not find multipart-post-2.0.0 in any of the sources
remote:
remote: !
remote: ! Failed to install gems via Bundler.
remote: !
remote: ! Push rejected, failed to compile Ruby app.
remote:
remote: ! Push failed
The gem is supposed to be multipart-post (version 2.0.0), but for some reason it is including the version as part of the gem file. Any thoughts?
You can see the RubyGems site & use proper version format such as
gem 'multipart-post', '~> 2.0'
and again commit lifecycle & see what happens
I am totally new to Git and Ruby on Rails and I'm doing the "The Odin Project", but I've got stucked.
I am trying to deploy the application I've created, using Git to push the master branch up to Heroku.
When I run the command "git push heroku master" I get this log with the follwing mistakes, what it may be?
matteo#matteo-VirtualBox:~/railsbridge/hello_app$ git push heroku master
Counting objects: 90, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (76/76), done.
Writing objects: 100% (90/90), 22.03 KiB | 0 bytes/s, done.
Total 90 (delta 6), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: ! Warning: Multiple default buildpacks reported the ability to handle this app. The first buildpack in the list below will be used.
remote: Detected buildpacks: Ruby,Node.js
remote: See https://devcenter.heroku.com/articles/buildpacks#buildpack-detect-order
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.3.4
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.15.4). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/.........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Fetching rake 12.1.0
remote: Installing concurrent-ruby 1.0.5
remote: Fetching minitest 5.10.3
....
remote: Installing turbolinks 5.0.1
remote: Fetching activesupport 5.1.4
remote: The latest bundler is 1.16.0.pre.3, but you are currently running 1.15.2.
remote: To update, run `gem install bundler --pre`
remote: Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
remote: current directory:
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/gems/sqlite3-1.3.13/ext/sqlite3
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/ruby-2.3.4/bin/ruby -r
remote: ./siteconf20171015-278-1swne7x.rb extconf.rb
remote: checking for sqlite3.h... no
remote: sqlite3.h is missing. Try 'brew install sqlite3',
remote: 'yum install sqlite-devel' or 'apt-get install libsqlite3-dev'
remote: and check your shared library search path (the
remote: location where your sqlite3 shared library is located).
remote: *** extconf.rb failed ***
remote: Could not create Makefile due to some reason, probably lack of necessary
remote: libraries and/or headers. Check the mkmf.log file for more details. You may
remote: need configuration options.
remote: Provided configuration options:
remote: --with-opt-dir
remote: --srcdir=.
remote: --curdir
remote: --ruby=/tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/ruby-2.3.4/bin/$(RUBY_BASE_NAME)
remote: --with-sqlite3-config
remote: --without-sqlite3-config
remote: --without-sqlite3-lib=${sqlite3-dir}/lib
remote: To see why this extension failed to compile, please check the mkmf.log which can
remote: be found here:
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/sqlite3-1.3.13/mkmf.log
remote: extconf failed, exit code 1
remote: Gem files will remain installed in
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/gems/sqlite3-1.3.13
remote: for inspection.
remote: Results logged to
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/sqlite3-1.3.13/gem_make.out
remote: An error occurred while installing sqlite3 (1.3.13), and Bundler cannot
remote: continue.
remote: Make sure that `gem install sqlite3 -v '1.3.13'` succeeds before bundling.
remote: In Gemfile:
remote: sqlite3
remote: Bundler Output: Warning: the running version of Bundler (1.15.2) is older than the version that created the lockfile (1.15.4). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/.........
remote: Fetching version metadata from https://rubygems.org/..
remote: Fetching dependency metadata from https://rubygems.org/.
remote: Fetching rake 12.1.0
remote: Fetching concurrent-ruby 1.0.5
1.4
remote: Fetching rb-inotify 0.9.10
remote: Installing rb-inotify 0.9.10
remote: The latest bundler is 1.16.0.pre.3, but you are currently running 1.15.2.
remote: To update, run `gem install bundler --pre`
remote: Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
remote:
remote: current directory:
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/gems/sqlite3-1.3.13/ext/sqlite3
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/ruby-2.3.4/bin/ruby -r
remote: ./siteconf20171015-278-1swne7x.rb extconf.rb
remote: checking for sqlite3.h... no
remote: sqlite3.h is missing. Try 'brew install sqlite3',
remote: 'yum install sqlite-devel' or 'apt-get install libsqlite3-dev'
remote: and check your shared library search path (the
remote: location where your sqlite3 shared library is located).
remote: *** extconf.rb failed ***
remote: Could not create Makefile due to some reason, probably lack of necessary
remote: libraries and/or headers. Check the mkmf.log file for more details. You may
remote: need configuration options.
remote:
remote: Provided configuration options:
remote: --with-opt-dir
remote: --without-opt-dir
remote: --ruby=/tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/ruby-2.3.4/bin/$(RUBY_BASE_NAME)
remote: --with-sqlite3-config
remote: --without-sqlite3-lib=${sqlite3-dir}/lib
remote:
remote: To see why this extension failed to compile, please check the mkmf.log which can
remote: be found here:
remote:
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/sqlite3-1.3.13/mkmf.log
remote:
remote: extconf failed, exit code 1
remote:
remote: Gem files will remain installed in
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/gems/sqlite3-1.3.13
remote: for inspection.
remote: Results logged to
remote: /tmp/build_c400101f4282a4c7d4222ce20d2d35b2/vendor/bundle/ruby/2.3.0/extensions/x86_64-linux/2.3.0/sqlite3-1.3.13/gem_make.out
remote:
remote: An error occurred while installing sqlite3 (1.3.13), and Bundler cannot
remote: continue.
remote: Make sure that `gem install sqlite3 -v '1.3.13'` succeeds before bundling.
remote:
remote: In Gemfile:
remote: sqlite3
remote: !
remote: ! Failed to install gems via Bundler.
remote: ! Detected sqlite3 gem which is not supported on Heroku:
remote: ! https://devcenter.heroku.com/articles/sqlite3
remote: !
remote: ! Push rejected, failed to compile Ruby app.
remote:
remote: ! Push failed
remote: Verifying deploy...
remote:
remote: ! Push rejected to murmuring-river-60914.
remote:
To https://git.heroku.com/murmuring-river-60914.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/murmuring-river-60914.git'
I have followed the tutorial instruction by setting the Gemfile with this inside:
group :development, :test do
gem 'sqlite3', '1.3.13'
gem 'byebug', '9.0.0', platform: :mri
end
group :production do
gem 'pg', '0.20.0'
end
For multiple buildpacks, remove all of them and then set the Ruby one:
$ heroku buildpacks:clear
$ heroku buildpacks:set heroku/ruby
About SQLite on Heroku:
SQLite runs in memory, and backs up its data store in files on disk.
While this strategy works well for development, Heroku’s Cedar stack
has an ephemeral filesystem. You can write to it, and you can read
from it, but the contents will be cleared periodically. If you were to
use SQLite on Heroku, you would lose your entire database at least
once every 24 hours.
So, for the message
sqlite3.h is missing. Try 'brew install sqlite3'`
replace the sqlite3 gem for pg in your Gemfile, then edit the database.yml file:
# Gemfile
gem 'pg'
# config/database.yml
default: &default
adapter: postgresql
pool: <%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
timeout: 5000
development:
<<: *default
database: your_project_name_dev
test:
<<: *default
database: your_project_name_test
production:
<<: *default
database: your_project_name_prod
Probably you'll need to clean the tmp/ folder, so you can delete the Gemfile.lock file and run the rails commands for that:
$ rm -rf Gemfile.lock
$ rails tmp:clear
$ rails tmp:create
I just pushed an update (which works perfectly on localhost) to Heroku and I'm getting a status=500 error in my logs, a We're sorry, but something went wrong. page for my index page, and no further information.
Here is the information from git push heroku master:
Counting objects: 3733, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3205/3205), done.
Writing objects: 100% (3733/3733), 7.43 MiB | 1.01 MiB/s, done.
Total 3733 (delta 943), reused 2943 (delta 463)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.2.4
remote: ###### WARNING:
remote: You have the `.bundle/config` file checked into your repository
remote: It contains local state like the location of the installed bundle
remote: as well as configured git local gems, and other settings that should
remote: not be shared between multiple checkouts of a single repo. Please
remote: remove the `.bundle/` folder from your repo and add it to your `.gitignore` file.
remote: https://devcenter.heroku.com/articles/bundler-configuration
remote:
remote: -----> Installing dependencies using bundler 1.11.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Your Gemfile lists the gem pg (>= 0) more than once.
remote: You should probably keep only one of them.
remote: While it's not a problem now, it could cause errors if you change the version of just one of them later.
remote: Warning: the running version of Bundler is older than the version that created the lockfile. We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Fetching gem metadata from https://rubygems.org/...........
remote: Fetching version metadata from https://rubygems.org/...
remote: Fetching dependency metadata from https://rubygems.org/..
remote: Using rake 11.1.2
remote: Using json 1.8.3
remote: Using i18n 0.7.0
remote: Using minitest 5.8.4
remote: Using thread_safe 0.3.5
remote: Using builder 3.2.2
remote: Using erubis 2.7.0
remote: Using mini_portile2 2.0.0
remote: Using rack 1.6.4
remote: Using mime-types-data 3.2016.0221
remote: Using arel 6.0.3
remote: Using execjs 2.6.0
remote: Using bcrypt 3.1.11
remote: Using sass 3.4.22
remote: Using coffee-script-source 1.10.0
remote: Using thor 0.19.1
remote: Using concurrent-ruby 1.0.1
remote: Using google-analytics-rails 1.1.0
remote: Using pg 0.18.4
remote: Using bundler 1.11.2
remote: Using tilt 2.0.2
remote: Using tzinfo 1.2.2
remote: Using nokogiri 1.6.7.2
remote: Using rack-test 0.6.3
remote: Using mime-types 3.0
remote: Using autoprefixer-rails 6.3.6
remote: Using uglifier 3.0.0
remote: Using figaro 1.0.0
remote: Using coffee-script 2.4.1
remote: Using sprockets 3.6.0
remote: Using activesupport 4.2.6
remote: Using loofah 2.0.3
remote: Using mail 2.6.4
remote: Using bootstrap-sass 3.3.6
remote: Using rails-deprecated_sanitizer 1.0.3
remote: Using globalid 0.3.6
remote: Using activemodel 4.2.6
remote: Using rails-html-sanitizer 1.0.3
remote: Using rails-dom-testing 1.0.7
remote: Using activejob 4.2.6
remote: Using activerecord 4.2.6
remote: Using actionview 4.2.6
remote: Using actionpack 4.2.6
remote: Using actionmailer 4.2.6
remote: Using railties 4.2.6
remote: Using sprockets-rails 3.0.4
remote: Using simple_form 3.2.1
remote: Using mail_form 1.5.1
remote: Using coffee-rails 4.1.1
remote: Installing orm_adapter 0.5.0
remote: Installing warden 1.2.6
remote: Installing responders 2.2.0
remote: Using jquery-rails 4.1.1
remote: Using rails 4.2.6
remote: Using sass-rails 5.0.4
remote: Using turbolinks 2.5.3
remote: Installing jquery-turbolinks 2.1.0
remote: Installing devise 4.2.0
remote: Bundle complete! 20 Gemfile dependencies, 58 gems now installed.
remote: Gems in the groups development, test and production were not installed.
remote: Bundled gems are installed into ./vendor/bundle.
remote: Bundle completed (4.42s)
remote: Cleaning up the bundler cache.
remote: Your Gemfile lists the gem pg (>= 0) more than once.
remote: You should probably keep only one of them.
remote: While it's not a problem now, it could cause errors if you change the version of just one of them later.
remote: Warning: the running version of Bundler is older than the version that created the lockfile. We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
remote: Detected manifest file, assuming assets were compiled locally
remote:
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:
remote: ###### WARNING:
remote: You have the `.bundle/config` file checked into your repository
remote: It contains local state like the location of the installed bundle
remote: as well as configured git local gems, and other settings that should
remote: not be shared between multiple checkouts of a single repo. Please
remote: remove the `.bundle/` folder from your repo and add it to your `.gitignore` file.
remote: https://devcenter.heroku.com/articles/bundler-configuration
remote:
remote: ###### WARNING:
remote: No Procfile detected, using the default web server.
remote: We recommend explicitly declaring how to boot your server process via a Procfile.
remote: https://devcenter.heroku.com/articles/ruby-default-web-server
remote:
remote: -----> Discovering process types
remote: Procfile declares types -> (none)
remote: Default types for buildpack -> console, rake, web, worker
remote:
remote: -----> Compressing...
remote: Done: 182.8M
remote: -----> Launching...
remote: Released v20
remote: https://frozen-lowlands-30190.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy... done.
To https://git.heroku.com/frozen-lowlands-30190.git
5f16820..3583a96 master -> master
And here's the status=500 line I get, which doesn't have further explanation:
2016-09-07T21:43:17.513968+00:00 heroku[router]: at=info method=GET path="/" host=www.geneticgolf.com request_id=e52af315-b9c6-4029-af51-69deada5b2f3 fwd="70.181.88.50" dyno=web.1 connect=1ms service=33ms status=500 bytes=1754
I have run heroku run rake db:migrate and heroku restart, but to no avail. I also have the rails_12factor gem installed in my production group gemfile already.
Can anyone point out where the error might be or how to fix it? The site is live so an erroring index page is bad...
NEW INFORMATION
The staging link for my site is apparently not exhibiting this problem, only the domain name that points to the staging link.
I messaged Heroku support and they said that I should remove .bundle/config from my Git files because it was preventing my production gems from being installed, which prohibited rails_12factor from giving me information about the error. Once this change was made the heroku logs actually began yielding useful information and I was able to debug.