In my application.css.scss I reference an image like this: body { background: #7d9ec4 url(asset-path(\'background.png\', image)) no-repeat fixed bottom center;
In order to keep controller specific JavaScript logic out of the standard application.js and only have it included by the relevant controller, I\'m putting it in its own .js file and including it base
I\'ve got html5-rails and compass-html5 working in devlopment on rails 3.1 but when I run my app in production mode and try to visit my homepage, I get the following:
Ok, I\'ve read a lot of information about the new Asset Pipe开发者_如何学运维line for Rails 3.1 and I couldn\'t find a proper answer to my doubt.
we have a rather extensive acceptance test suite, running on our CI server triggered by a Github push hook. i\'d like to add a feature or spec to basically test wether rake assets:precompile runs smoo
I have the following setup: app/assets/stylesheets/application.css.scss /* *= require_self *= require fancybox
When I run \"bund开发者_JS百科le exec rake -T\" in development, the assets:clear and assets:precompile tasks show up, but if I prefix that command with RAILS_ENV=production, or run it on a server wher
I have a rails 3.1 application that allows users to upload pictures. Should these pictures be stored as assets(in app/assets) and therefore be subject to Sprocket overhead(caching, fingerprinting, etc
How do I access assets on my maintenance page in rails 3.1 with the asset pipeline enabled? With the asset pipeline enalbed all assets have a hash in their filename.However, maintenance pages are van
Everything works great in Development. And app deploys as normal with Capistrano. Assets (javascript & css) appear to be fully pre-compiled and each, along with images, are given a \"fingerprint\"