On http://docs.heroku.com/s3 it shows what to do to use s3 with attachment-fu. Specifically it indicates that you need to add has_attachment :storage => :s3 to the definition of User I think this should be going in to vendor/plugins/community_engine/app/ models/user.rb but this is not stated specifically on the heroku page. Can someone confirm this for me. ( As you can tell from this question, my future install procedure will be real newbie material ) / Colm
On Aug 31, 2:51 pm, Carl Fyffe <[email protected]> wrote: > Colm, > > I will gladly update the page. Someone said they were going to post > better instructions back to the list and I either missed them or they > never arrived. > > If you send better instructions I will post them! > > Carl > > On 8/31/09, Colm <[email protected]> wrote: > > > > > Reply to self : > > > The S3 service is defined as perhttp://docs.heroku.com/s3and it > > requires the use of either the Attachment-Fu or Paperclip plugins. > > > To Carl Fyffe, I see that you are one of the editors of the > >http://sites.google.com/a/curbly.com/communityengine/deploying-to-heroku > > page so any chance you could update those instructions. I'l try to get > > a clean install procedure done myslef, if I ever get it installed !! > > > / Colm > > > On Aug 29, 11:31 pm, Colm <[email protected]> wrote: > >> Firstly, I'd like to add to the request for an updated install > >> procedure, please...... > > >> About the S3 service, where are you supposed to tellherokuto use > >> this and where do you provide your user information ? > > >> SimianLogic : In your hint of Aug 12 are you in effect copying the > >> contents of vendor/plugins/community_engine/public/ to public/ > >> manually ? > > >> Thanks / Colm > > >> On Aug 12, 4:47 pm, SimianLogic <[email protected]> wrote: > > >> > I think (maybe) the EnginesHelper is a holdover from when the Engines > >> > plugin was being used, whereas now it seems baked into rails. My app > >> > only has one theme, so I just copied everything to where the Engines > >> > plugin would copy them if it had write access. > > >> > /themes/(my theme)/images/(content) to /public/images/theme/(content) > >> > /themes/(my theme)/stylesheets/(content) to /public/stylesheets/theme/ > >> > (content) > > >> > Going forward, you'll have to make sure you're editing the right > >> > version, as it won't autocopy your new changes into the public folder. > >> > After that, you just add the new files to your git repo, push toHeroku, > >> > and the errors should go away (also--remove the EnginesHelper > >> > line). > > >> > On Aug 12, 8:11 am, "James.d" <[email protected]> wrote: > > >> > > Hi Will, > > >> > > I'm sort of in the same boat as Levi. Using the edge build, i'm able > >> > > to get the .gem file errors (you were correct), but now i'm seeing a > >> > > bunch ofHerokuis read only errors. > > >> > > Can anyone validate that per the instructions, setting > >> > > EnginesHelper.autoload_assets = false actually works with the edge > >> > > build andHeroku. > > >> > > You mention manually copying things intoHeroku, can you share what > >> > > commands made that worked? I'm not a git pro yet... > > >> > > Thanks, > >> > > James > > >> > > On Aug 8, 5:22 pm, SimianLogic <[email protected]> wrote: > > >> > > > Did you add the .gems file? I didn't keep notes while moving over to > >> > > >Heroku, so I don't remember everything I've changed. My install is a > >> > > > bit hacked right now, but I haven't had time to go back and smooth > >> > > > things over. For example, I could never get the > >> > > > EngineHelper.autoload_assets flag to work properly (just manually > >> > > > copied everything into the public directory). Next time I update > >> > > > CE's > >> > > > sources, I'll see if I can do a better job taking notes on the > >> > > > process > >> > > > to get it running onHeroku. > > >> > > > -Will > > >> > > > On Aug 4, 8:49 am, Levi Rosol <[email protected]> wrote: > > >> > > > > did you have any issues with desert? We're seeing this error even > >> > > > > though it > >> > > > > seems we have the desert gem setup correctly: > > >> > > > > $herokurake db:migrate > >> > > > > rake aborted! > >> > > > > no such file to load -- desert > >> > > > > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > >> > > > > `gem_original_require' > >> > > > > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > >> > > > > `require' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/de > >> > > > > pendencies.rb:156:in > >> > > > > `require' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/de > >> > > > > pendencies.rb:521:in > >> > > > > `new_constants_in' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/de > >> > > > > pendencies.rb:156:in > >> > > > > `require' > >> > > > > /disk1/home/slugs/37573_3715c86_5842/mnt/config/environment.rb:8 > >> > > > > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > >> > > > > `gem_original_require' > >> > > > > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in > >> > > > > `require' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/de > >> > > > > pendencies.rb:156:in > >> > > > > `require' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/de > >> > > > > pendencies.rb:521:in > >> > > > > `new_constants_in' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/de > >> > > > > pendencies.rb:156:in > >> > > > > `require' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/tasks/misc.rake:4 > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in > >> > > > > `call' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:617:in > >> > > > > `execute' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in > >> > > > > `each' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:612:in > >> > > > > `execute' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:578:in > >> > > > > `invoke_with_call_chain' > >> > > > > /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:571:in > >> > > > > `invoke_with_call_chain' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:588:in > >> > > > > `invoke_prerequisites' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:585:in > >> > > > > `each' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:585:in > >> > > > > `invoke_prerequisites' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:577:in > >> > > > > `invoke_with_call_chain' > >> > > > > /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:571:in > >> > > > > `invoke_with_call_chain' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:564:in > >> > > > > `invoke' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2027:in > >> > > > > `invoke_task' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in > >> > > > > `top_level' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in > >> > > > > `each' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2005:in > >> > > > > `top_level' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in > >> > > > > `standard_exception_handling' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1999:in > >> > > > > `top_level' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1977:in > >> > > > > `run' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:2044:in > >> > > > > `standard_exception_handling' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/lib/rake.rb:1974:in > >> > > > > `run' > >> > > > > /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.4/bin/rake:31 > >> > > > > /usr/local/bin/rake:19:in `load' > >> > > > > /usr/local/bin/rake:19 > >> > > > > (in /disk1/home/slugs/37573_3715c86_5842/mnt) > >> > > > > ** Invoke db:migrate (first_time) > >> > > > > ** Invoke environment (first_time) > >> > > > > ** Execute environment > >> > > > > ============================== > > >> > > > > -- > >> > > > > Levi Rosol > >> > > > > Twitter: @LeviRosol > > >> > > > > On Tue, Aug 4, 2009 at 10:44 AM, SimianLogic > >> > > > > <[email protected]>wrote: > > >> > > > > > I've got my site (www.worththepoints.com) running onHerokunow. I > >> > > > > > just migrated from EC2 about a week ago, and for the most part > >> > > > > > the > >> > > > > > transition has gone pretty smoothly. Make sure you're offloading > >> > > > > > images to S3 before you start (no permanent storage onHeroku), > >> > > > > > and > >> > > > > > check the little note I posted a couple of days ago on > >> > > > > > attachment_fu. > >> > > > > > I couldn't get attachment_fu working, but after filing a support > >> > > > > > ticket their guys helped track down a solution within a couple > >> > > > > > of > >> > > > > > days. > > >> > > > > > On Aug 3, 9:09 am, Levi Rosol <[email protected]> wrote: > >> > > > > > > We're having issues and are thinking of moving to something > >> > > > > > > else, but > >> > > > > > before > >> > > > > > > we do that, I wanted to see if anyone has been able to > >> > > > > > > successfully > >> > > > > > launch a > >> > > > > > > CE site onHeroku. > > >> > > > > > > -- > >> > > > > > > Levi Rosol > >> > > > > > > Twitter: @LeviRosol --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CommunityEngine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/communityengine?hl=en -~----------~----~----~----~------~----~------~--~---
