Почему не разворачивается приложение на heroku?

Question

[eliastro]

Здравствуйте!
Пытаюсь развернуть приложение Ruby on Rails4 на heroku.
После того, как отправил изменения в локальный репозиторий git, делаю отправку на heroku:

git push heroku master

Результаты команды:

c:\RailsProject\thinkblog>git push heroku master
Counting objects: 11, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 536 bytes, done.
Total 6 (delta 4), reused 0 (delta 0)

-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.0.0
-----> Installing dependencies using Bundler version 1.3.2
Running: bundle install --without development:test --path vendor/bundle -
-binstubs vendor/bundle/bin
Fetching gem metadata from https://rubygems.org/.........
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Using rake (10.1.0)
Using i18n (0.6.9)
Using minitest (4.7.5)
Using multi_json (1.8.2)
Using atomic (1.1.14)
Using thread_safe (0.1.3)
Using tzinfo (0.3.38)
Using activesupport (4.0.1)
Using builder (3.1.4)
Using erubis (2.7.0)
Using rack (1.5.2)
Using rack-test (0.6.2)
Using actionpack (4.0.1)
Using mime-types (1.25.1)
Using polyglot (0.3.3)
Using treetop (1.4.15)
Using mail (2.5.4)
Using actionmailer (4.0.1)
Using activemodel (4.0.1)
Using activerecord-deprecated_finders (1.0.3)
Using arel (4.0.1)
Using activerecord (4.0.1)
Using bootstrap-sass (2.1.0.0)
Using bundler (1.3.2)
Using coffee-script-source (1.6.3)
Using execjs (2.0.2)
Using coffee-script (2.2.0)
Using thor (0.18.1)
Using railties (4.0.1)
Using coffee-rails (4.0.1)
Using hike (1.2.3)
Using jbuilder (1.5.3)
Using jquery-rails (3.0.4)
Using json (1.8.1)
Using pg (0.17.0)
Using tilt (1.4.1)
Using sprockets (2.10.1)
Using sprockets-rails (2.0.1)
Using rails (4.0.1)
Using rdoc (3.12.2)
Using sass (3.2.12)
Using sass-rails (4.0.1)
Using sdoc (0.3.20)
Using turbolinks (2.0.0)
Using uglifier (2.3.2)
Your bundle is complete! It was installed into ./vendor/bundle
Bundle completed (8.46s)
Cleaning up the bundler cache.
-----> Writing config/database.yml to read from DATABASE_URL
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Asset precompilation completed (2.10s)
Cleaning assets
-----> WARNINGS:
Include 'rails_12factor' gem to enable all platform features
See https://devcenter.heroku.com/articles/rails-integr... for more
information.

You have not declared a Ruby version in your Gemfile.
To set your Ruby version add this line to your Gemfile:
ruby '2.0.0'
# See https://devcenter.heroku.com/articles/ruby-versions for more inform
ation.

Removing `Gemfile.lock` because it was generated on Windows.
Bundler will do a full resolve so native gems are handled properly.
This may result in unexpected gem versions being used in your app.
-----> Discovering process types
Procfile declares types -> (none)
Default types for Ruby -> console, rake, web, worker

-----> Compiled slug size: 21.7MB
-----> Launching... done, v8
afternoon-beach-6553.herokuapp.com deployed to Heroku

To [e-mail]:afternoon-beach-6553.git
1cbcc54..e7ab1ca master -> master

Вроде бы ошибок нет. Открываю сайт:

heroku open

Но открывается стандартная заглушка "Heroku | Welcome to your new app!", т.е. проект не выгрузился на heroku.
Вот результаты команды heroku logs:

c:\RailsProject\thinkblog>heroku logs
2013-11-30T15:58:31.157367+00:00 app[web.1]: [2013-11-30 15:58:31] INFO WEBrick
::HTTPServer#start: pid=2 port=29179
2013-11-30T15:58:31.514138+00:00 heroku[web.1]: State changed from starting to u
p
2013-11-30T17:07:30.739453+00:00 heroku[web.1]: Idling
2013-11-30T17:07:30.740562+00:00 heroku[web.1]: State changed from up to down
2013-11-30T17:07:34.001400+00:00 heroku[web.1]: Stopping all processes with SIGT
ERM
2013-11-30T17:07:34.595847+00:00 app[web.1]: [2013-11-30 17:07:34] FATAL SignalE
xception: SIGTERM
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2.0.0/webrick/server.rb:170:in `select'
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2.0.0/webrick/server.rb:32:in `start'
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/rack-1.5.2/lib/rack/handler/webrick.rb:14:in `run'
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2.0.0/webrick/server.rb:170:in `block in start'
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2.0.0/webrick/server.rb:160:in `start'
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/railties-4.0.1/lib/rails/commands/server.rb:84:in `start'
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/railties-4.0.1/lib/rails/commands.rb:71:in `tap'
2013-11-30T17:07:34.596047+00:00 app[web.1]: [2013-11-30 17:07:34] INFO going t
o shutdown ...
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/railties-4.0.1/lib/rails/commands.rb:76:in `block in '
2013-11-30T17:07:34.596047+00:00 app[web.1]: bin/rails:4:in `'
2013-11-30T17:07:34.596047+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/railties-4.0.1/lib/rails/commands.rb:71:in `'
2013-11-30T17:07:34.596047+00:00 app[web.1]: bin/rails:4:in `require'
2013-11-30T17:07:34.596047+00:00 app[web.1]: [2013-11-30 17:07:34] INFO WEBrick
::HTTPServer#start done.
2013-11-30T17:07:34.595847+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/rack-1.5.2/lib/rack/server.rb:264:in `start'
2013-11-30T17:07:34.644169+00:00 app[web.1]: => Booting WEBrick
2013-11-30T17:07:34.644169+00:00 app[web.1]: => Ctrl-C to shutdown server
2013-11-30T17:07:34.644169+00:00 app[web.1]: Exiting
2013-11-30T17:07:34.644169+00:00 app[web.1]: => Rails 4.0.1 application starting
in production on 0.0.0.0:29179
2013-11-30T17:07:34.644169+00:00 app[web.1]: => Run `rails server -h` for more s
tartup options
2013-11-30T17:07:35.974709+00:00 heroku[web.1]: Process exited with status 143
2013-12-01T10:21:26+00:00 heroku[slug-compiler]: Slug compilation started
2013-12-01T10:21:53.341656+00:00 heroku[api]: Deploy 955d598 by ******@gmail.
com
2013-12-01T10:21:53.364924+00:00 heroku[api]: Release v6 created by ******@gm
ail.com
2013-12-01T10:21:53+00:00 heroku[slug-compiler]: Slug compilation finished
2013-12-01T10:21:53.723026+00:00 heroku[web.1]: State changed from down to start
ing
2013-12-01T10:21:57.550054+00:00 heroku[web.1]: Starting process with command `b
in/rails server -p 34518 -e $RAILS_ENV`
2013-12-01T10:22:01.673536+00:00 app[web.1]: [2013-12-01 10:22:01] INFO WEBrick
1.3.1
2013-12-01T10:22:01.674227+00:00 app[web.1]: [2013-12-01 10:22:01] INFO WEBrick
::HTTPServer#start: pid=2 port=34518
2013-12-01T10:22:01.673752+00:00 app[web.1]: [2013-12-01 10:22:01] INFO ruby 2.
0.0 (2013-11-22) [x86_64-linux]
2013-12-01T11:25:09.430635+00:00 heroku[web.1]: Idling
2013-12-01T11:25:09.431176+00:00 heroku[web.1]: State changed from up to down
2013-12-01T11:25:12.665757+00:00 heroku[web.1]: Stopping all processes with SIGT
ERM
2013-12-01T11:25:13.395941+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/ge
ms/railties-4.0.1/lib/rails/commands/server.rb:84:in `start'
2013-12-01T11:25:13.395941+00:00 app[web.1]: [2013-12-01 11:25:13] FATAL SignalE
xception: SIGTERM
2013-12-01T11:25:13.395941+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2.0.0/webrick/server.rb:170:in `select'
2013-12-01T11:25:13.395941+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2.0.0/webrick/server.rb:170:in `block in start'
2013-12-01T11:25:13.395941+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/
2013-12-07T07:29:56.489300+00:00 heroku[web.1]: State changed from starting to u
P
….
2013-12-07T08:07:20+00:00 heroku[slug-compiler]: Slug compilation started
2013-12-07T08:07:49.681788+00:00 heroku[api]: Deploy e7ab1ca by ******@gmail.
com
2013-12-07T08:07:49.958439+00:00 heroku[api]: Release v8 created by ******@gm
ail.com
2013-12-07T08:07:50+00:00 heroku[slug-compiler]: Slug compilation finished
2013-12-07T08:07:50.537055+00:00 heroku[web.1]: State changed from up to startin
g
2013-12-07T08:07:53.138953+00:00 heroku[web.1]: Stopping all processes with SIGT
ERM
2013-12-07T08:07:53.675334+00:00 app[web.1]: [2013-12-07 08:07:53] FATAL SignalE
xception: SIGTERM
2013-12-07T08:07:59.894998+00:00 app[web.1]: [2013-12-07 08:07:59] INFO WEBrick
::HTTPServer#start: pid=2 port=43135
2013-12-07T08:08:00.362503+00:00 heroku[web.1]: State changed from starting to u
p

Rails, '4.0.1', ruby 2.0.0p247, Win7.

Answer 1

[jFox]

Проверь - запущен ли у тебя Dyno.

Comments

[eliastro]

А как проверить? Не нашел такого где запускается.

[jFox]

heroku ps

Если видите нечто вроде:

=== web (1X): `bin/rails server -p $PORT -e $RAILS_ENV`
web.1: crashed 2013/12/07 04:49:08 (~ 1m ago)

, то, вероятно, проблема заключается в комментариях в коде касающихся IE9 (Heroku их не переваривает) подобного рода:

<!--[if lt IE 9]><script src="../../docs-assets/js/ie8-responsive-file-warning.js"></script><![endif]-->
<!--[if lt IE 9]>
      <script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
      <script src="https://oss.maxcdn.com/libs/respond.js/1.3.0/respond.min.js"></script>
    <![endif]-->

Удали подобные комментарии и вновь смотри логи.

[eliastro]

подобные комменты для IE были - удалил. Логи (heroku ps) не поменялись:
c:\RailsProject\thinkblog>heroku ps
=== web (1X): `bin/rails server -p $PORT -e $RAILS_ENV`
web.1: up 2013/12/07 22:06:37 (~ 1m ago)

[jFox]

Раз Дино запущен, значит дело не в комментариях.

Покажи что тебе говорит git remote -v в папке с приложением.

[eliastro]

c:\RailsProject\thinkblog>git remote -v
heroku [e-mail]:afternoon-beach-6553.git (fetch)
heroku [e-mail]:afternoon-beach-6553.git (push)
origin [e-mail]:vk26/thinkblog.git (fetch)
origin [e-mail]:vk26/thinkblog.git (push)

[jFox]

Больше никаких идей пока что нет.
Гем 'rails_12factor' тут точно не при чём, поскольку он вовсе не обязателен к установке для запуска проекта. По крайней мере я всегда запускал проекты а Heroku без него.

В обход твоей проблемы могу пореккомендовать перенести свой код на вот эту заготовку.

Она постится на Heroku со стопроцентным шансом ;)

[eliastro]

Все получилось, спасибо! Также помогло удаление и вновь пересоздание приложения на хероку, т.е. команды:
heroku destroy
heroku create
git push heroku master

Answer 2

[FanKiLL]

Добавте gem 'rails_12factor'
Почему, читайте тут

Comments

[FanKiLL]

И в начало Gemfile пропишите ruby '2.0.0'

[eliastro]

добавил gem 'rails_12factor'. Также прописывал в гемфайл ruby '2.0.0'. Не помогло.

[Даниил Лаптев]

Судя по ошибкам, проблемы все же с rails_12factor