Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I agree with what JacobM said above in a comment, but perhaps I can sum these up for you.</p> <ol> <li><p>This question is slightly vague. Are you referring to rails environments or are you referring to the <code>Gemfile</code>? I am going to assume you mean the <code>Gemfile</code>. In that case, the </p> <p>group :assets do gem 'sprockets' gem 'assets-ftw' end</p></li> </ol> <p>is a way of telling bundler when to include those gems. You don't need <code>:testing</code> gems in your <code>:development</code> profile, and vice versa, etc. Its good organization. </p> <ol> <li><p>This question doesn't have a hard or fast answer. It really depends on the code you are writing. It is advised to test completely. Make sure your unit tests cover all aspects of your model and using integration testing to ensure user actions are completing successfully up and down the stack.</p></li> <li><p>I would advise against renaming the folders inside the <code>/assets</code> directory, but rails may let you do that. The files found in the assets folder are their to be compressed when the rails app is put into production. The <code>/public/javascripts</code> folder is where <code>.js</code> files used to reside before Rails <code>3.1</code></p></li> <li><p>To compile assets you run the rake command <code>rake assets:precompile</code></p></li> <li><p>I'm not sure.</p></li> </ol> <p>For more complete answers. I would split these up into longer questions, but search SO more completely, as I think most of these have been asked before. </p>
 

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