You shouldn't need to turn off caching for this.
I'm working now to bake this into the next release of radiant, but
here's a start:
Inside config/initializers/compass.rb place this code
-----
require 'fileutils'
FileUtils.mkdir_p(Rails.root.join("tmp", "stylesheets"))
Sass::Plugin.options[:template_location] = (Rails.root + 'public' +
'stylesheets' + 'sass').to_s
require 'compass'
require 'compass/app_integration/rails'
Compass::AppIntegration::Rails.initialize!
-----
That should tell sass where to look for the templates and ensure that
the tmp/stylesheets directory has been created.
For JS, you can run "rake radiant:update:cached_assets" before
deploying which should compile the JS. You can the check that in and
deploy.
On Tue, May 31, 2011 at 5:25 PM, Wes Gamble <[email protected]> wrote:
> Thanks William.
>
> Also, you need to turn off Sass compilation for Heroku, so production.rb
> looks like this for those two options:
>
> # Caching is off for Heroku
> config.action_controller.perform_caching = false
>
> # Turn off Sass compilation in production
> Sass::Plugin.options[:never_update] = true
>
> Wes
>
> On 5/31/11 3:11 PM, William Ross wrote:
>
> On 31 May 2011, at 20:15, Wes Gamble wrote:
>
> How do I override the default admin. layout for Radiant?
>
> I'm playing with the Radiant 1.0.0 prerelease and it's caching the
> Javascript into an "all" file and I want to take that behavior out, since
> I'm deploying on Heroku and can't write to the filesystem.
>
> In this case it should be enough to set
>
> config.action_controller.perform_caching = false
>
> in config/environments/production.rb.
>
> If you really want to override the layout you can do that by including an
> app/layouts/application.html.haml in any extension.
>
> best,
>
> will
>
>
>
--
Jim Gay
Saturn Flyer LLC
http://www.saturnflyer.com
571-403-0338
