Hi,
I'm not a spree person, but I have ported frameworks to heroku. (e.g.: loved by
less)
not sure if this was already answered
Why not copy the default theme to the target spot on your own?
Seems the startup code would not copy if it it already existed.
And if it did copy it, just add the File.exist code and submit a patch.
see who calls
spree-0.10.2/lib/plugins/extension_patches/lib/asset_copy.rb
and see if you can get around it
--Keenan
On Jun 2, 2010, at 10:03 AM, Olivier R wrote:
Heroku apps don't have write privileges which causes this exception on
startup. Is there a way to go around this?
Check this out: http://paddock.heroku.com
/home/slugs/196124_7d3212a_92f9/mnt/.gems/gems/spree-0.10.2/lib/spree/
file_utilz.rb:61:in `mirror_files': Could not copy /home/slugs/
196124_7d3212a_92f9/mnt/.gems/gems/spree-0.10.2/vendor/extensions/
theme_default/public/images/wrapper-back-2.png to /disk1/home/slugs/
196124_7d3212a_92f9/mnt/public/images/wrapper-back-2.png:
(RuntimeError)
Read-only file system - /disk1/home/slugs/196124_7d3212a_92f9/mnt/
public/images/wrapper-back-2.png
Best regards,
Olivier
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
