The problem was, that I set the path using assets.s3.path instead of assets.path. No wonder it created the whole path, since it defaults to this one: :path => Radiant::Config["assets.path"] ? Radiant::Config["assets.path"] : ":rails_root/ public/:class/:id/:basename:no_original_style.:extension"
Cheers, Phil On 11 Aug., 15:13, Philipp Ringli <[email protected]> wrote: > Hi Keith, > > Thanks for your reply. > I had the settings in place. I tried your setting, restarted apache and the > path looks still like > this:http://s3.amazonaws.com/com-sichtwerk-imuw-ch/Users/cmyk/Sites/imuw-c... > It should look like, > no?:http://s3.amazonaws.com/com-sichtwerk-imuw-ch/public/assets/9/grt.jpg > > The problem is, that it won't find the assets once I push it to heroku. > > Phil > > On 11.08.2010, at 10:26, kbingman wrote: > > > > > You need to set the path in you Radiant::Config. I use the Settings > > extension to make it easier. > > > Here is mine: :class/:id/:basename:no_original_style.:extension > > > Hope that helps > > > keith > > > On Aug 9, 7:18 pm, cmyk <[email protected]> wrote: > >> I've got an issue with the paperclipped extension and s3. > >> I set it to use S3 and it works, but the path it saves the images to > >> (on the s3 server) looks exactly like the path on my system (/Users/ > >> cmyk/Sites/etc...) > >> And when I upload something on heroku, the path looks like disk1/home/ > >> slugs etc.. > >> Any ideas on how to fix that?
