Databases
StackOverflow2013
Postsdbo
PORails assets aren't compiled properly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails assets aren't compiled properly
    primarykey
    data
    text
    <p>I'm having an unsettling issue with Ruby on Rails today. My assets aren't compiled: and by that, I mean that even when using asset:precompiled, they are simply not compiled.</p> <p>I believe this will illustrate the problem better. After pre-compiling the assets, this is what /public/assets/application.js looks like:</p> <pre><code>// This is a manifest file that'll be compiled into including all the files listed below. // Add new JavaScript/Coffee code in separate files in this directory and they'll automatically // be included in the compiled file accessible from http://example.com/assets/application.js // It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the // the compiled file. // //= require jquery //= require jquery-ui //= require jquery_ujs //= require twitter/bootstrap //= require_tree . ; </code></pre> <p>Same goes for the css. The project works fine on other computers, so I suspect my configuration is at fault here. But what could possibly cause this kind of problem ? It's not like Rails doesn't try to precompile, but when he get to the files he just copy them to the asset folder without precompiling them.</p> <p>Any clue on how to fix that ?</p> <p>EDIT: Added output of asset:precompile</p> <pre><code>** Invoke assets:precompile (first_time) ** Execute assets:precompile /home/plaristote/.rvm/rubies/ruby-2.0.0-p0/bin/ruby /home/plaristote/.rvm/gems/ruby-2.0.0-p0@visibleo_commApp/bin/rake assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets --trace ** Invoke assets:precompile:all (first_time) ** Execute assets:precompile:all ** Invoke assets:precompile:primary (first_time) ** Invoke assets:environment (first_time) ** Execute assets:environment ** Invoke environment (first_time) ** Execute environment ** Invoke tmp:cache:clear (first_time) ** Execute tmp:cache:clear ** Execute assets:precompile:primary /home/plaristote/.rvm/rubies/ruby-2.0.0-p0/bin/ruby /home/plaristote/.rvm/gems/ruby-2.0.0-p0@visibleo_commApp/bin/rake assets:precompile:nondigest RAILS_ENV=production RAILS_GROUPS=assets --trace ** Invoke assets:precompile:nondigest (first_time) ** Invoke assets:environment (first_time) ** Execute assets:environment ** Invoke environment (first_time) ** Execute environment ** Invoke tmp:cache:clear (first_time) ** Execute tmp:cache:clear ** Execute assets:precompile:nondigest </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMichael
    1. USMichael
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORails assets aren't compiled properly
      1. USMatthew Clark
      1. VTFavorite
    1. COWhere you're trying to precompile? production enviromennt or development?
      singulars
      1. PORails assets aren't compiled properly
      1. UStbem
    2. COBoth development and production. Note that on development, when I do not pre-compile the assets, they should be compiled on the fly by Rails: however from what I can see in the browser the received js and css files weren't compiled at all (as shown above).
      singulars
      1. PORails assets aren't compiled properly
      1. USMichael
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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