From 5fdcda8b220af7042d4b5111fa16090ebaf16926 Mon Sep 17 00:00:00 2001 From: adman65 Date: Thu, 22 Mar 2012 12:05:28 +0100 Subject: [engines] [ci-skip] Add example of precompiling engine assets --- guides/source/engines.textile | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/guides/source/engines.textile b/guides/source/engines.textile index 6ae9504c23..501d48eab8 100644 --- a/guides/source/engines.textile +++ b/guides/source/engines.textile @@ -723,6 +723,21 @@ You can also specify these assets as dependencies of other assets using the Asse */ +h4. Separate Assets & Precompiling + +There are some situations where your engine's assets not required by the host application. For example, say that you've created +an admin functionality that only exists for your engine. In this case, the host application doesn't need to require +admin.css+ +or +admin.js+. Only the gem's admin layout needs these assets. It doesn't make sense for the host app to include +"blorg/admin.css"+ in it's stylesheets. In this situation, you should explicitly define these assets for precompilation. +This tells sprockets to add you engine assets when +rake assets:precompile+ is ran. + +You can define assets for precompilation in +engine.rb+ + + +initializer do |app| + app.config.assets.precompile += %w(admin.css admin.js) +end +