Hello,

I was wondering what you ment by create it locally...
Should i install the radiant as a plugin, so i can tweak it in my /
vendor dir?

Sorry that i'm not getting what you mean, but if you could explain it
a little more, you would really help me.
Thanx in advance!

On Sep 8, 4:44 pm, john muhl <johnm...@gmail.com> wrote:
> create it locally (by running in production) and commit it to your repo.
>
> On Wed, Sep 8, 2010 at 9:38 AM, Jeff Casimir <j...@casimircreative.com> wrote:
> > Hey all,
>
> > I have what is hopefully a quick issue.  My public facing site is
> > running great, but the admin side doesn't work in production on
> > Heroku.  Here's the trace:
>
> > ActionView::TemplateError (Read-only file system -
> > /disk1/home/slugs/261976_f884c4e_6faa/mnt/public/javascripts/admin/all.js
> > - Heroku has a read-only filesystem.  See
> >http://docs.heroku.com/constraints#read-only-filesystem) on line #9 of
> > /home/slugs/261976_f884c4e_6faa/mnt/.bundle/gems/ruby/1.8/gems/radiant-0.9.1/app/views/layouts/application.html.haml:
> > 6:     - @stylesheets.uniq.each do |stylesheet|
> > 7:       = stylesheet_link_tag stylesheet
> > 8:     %script{:type=>"text/javascript"}="var relative_url_root =
> > '#{ActionController::Base.relative_url_root}';"
> > 9:     = javascript_include_tag %w(admin/prototype admin/effects
> > admin/lowpro admin/dateinput admin/pagestatus admin/cookie admin/popup
> > admin/status admin/utility admin/codearea admin/tabcontrol
> > admin/ruledtable admin/sitemap admin/shortcuts admin/toggle
> > admin/validationerror admin/application), :cache => 'admin/all'
> > 10:     - @javascripts.uniq.each do |javascript|
> > 11:       = javascript_include_tagjavascript
> > 12:     - if @content_for_page_scripts
>
> > This is Radiant 0.9.1.  It looks like the javascript_include_tag is
> > trying to cache into 'admin/all' but failing because of the read-only
> > file system.
>
> > Tips?
>
> > Thanks,
> > Jeff
>
> > ---
> > Jeff Casimir
> > Jumpstart Lab by Casimir Creative, LLC
> >http://jumpstartlab.com
> > @jumpstartlab on twitter
>
>

Reply via email to