Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all Rails4 apps <a href="http://blog.remarkablelabs.com/2012/12/dynamic-index-html-rails-4-countdown-to-2013" rel="nofollow noreferrer">no longer serve public/index.html</a>, or <em>app/assets/rails.png</em>, as those files are now handled by the rails gem itself, so you can safely ignore all talk relating to them.</p> <p>Secondly, I would advise you to <strong>ignore</strong> the advice given in the <a href="https://stackoverflow.com/questions/8865712/rails-3-1-3-on-heroku-no-route-matches-get-assets-rails-png">question</a> you linked to as it's not at all relevant for rails4. You will not need to procompile your assets if you're using heroku. They do it for you when you push your app to them. It's probably worth removing the public/assets folder that you created when your ran <code>rake assets:precompile</code> as it will just get in the way</p> <p>Thirdly, remove the code you added to config/application.rb as there is <a href="http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0-gemfile" rel="nofollow noreferrer">no assets group in Rails 4</a></p> <p>Fourthly, heroku used to inject a plugin for serving static assets into your app, but now you need to <a href="https://devcenter.heroku.com/articles/rails4#heroku-gems" rel="nofollow noreferrer">do that yourself</a> by adding the following to your Gemfile:</p> <pre><code>gem 'rails_log_stdout', github: 'heroku/rails_log_stdout' gem 'rails3_serve_static_assets', github: 'heroku/rails3_serve_static_assets' </code></pre> <p>Fifthly, you are using Webrick server. Heroku advise you to <a href="https://devcenter.heroku.com/articles/rails-unicorn" rel="nofollow noreferrer">switch to Unicorn</a>.</p> <p>Lastly, don't worry about the default Rails landing page not being shown on Heroku. It might be a bug in their system, it happened to me, it will happen to the next guy, it would more than likely happen to Matz if he tried it too. It's no big deal. Just move on. Your app is ready for you to start developing your own landing page.</p> <p>Good luck and for what it's worth, here's a very simple example Gemfile optimised for heroku:</p> <pre><code>source 'https://rubygems.org' # you are using Ruby 1.9.3, better to 2.0.0 upgrade for more speed ruby '2.0.0' gem 'rails', '4.0.0.rc1' gem 'sass-rails', '~&gt; 4.0.0.rc1' gem 'uglifier', '&gt;= 1.3.0' gem 'coffee-rails', '~&gt; 4.0.0' gem 'jquery-rails' gem 'turbolinks' gem 'jbuilder', '~&gt; 1.0.1' # The asset_sync gem is WELL worth using # but you should read more about it before deciding # https://github.com/rumblelabs/asset_sync # gem 'asset_sync' # only want sqlite in dev and test envs group :development, :test do gem 'sqlite3' end group :production do gem 'pg' # dont want sqlite in production gem 'unicorn' # make sure you follow installation instructions for this gem gem 'rails_log_stdout', github: 'heroku/rails_log_stdout' gem 'rails3_serve_static_assets', github: 'heroku/rails3_serve_static_assets' end group :doc do gem 'sdoc', require: false end </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload