Did you get a chance to look at this again? The upgrade to 1.9 is scheduled but won't happen for at least two more weeks :(
On Wed, Jan 16, 2013 at 4:41 PM, Tim Uckun <[email protected]> wrote: > OK I did as instructed, upgraded the gem and tried an export. It > didn't throw an error message but it also didn't work. The export > looked like this > > #<Proc:0x0000000006b2fe70@/home/bingatron/chrysler/staging/shared/bundle/ruby/1.8/bundler/gems/active_scaffold_export-94213b2eda02/lib/active_scaffold/actions/export.rb:59> > > > > On Wed, Jan 16, 2013 at 9:38 AM, Hernan Astudillo <[email protected]> wrote: >> Tim, >> >> I created a branch for REE, since the streaming way isn't good with REE ( >> http://www.ruby-doc.org/core-1.8.7/Enumerable/Enumerator.html) >> >> can you try it now? Put this in your Gemfile >> >> gem 'active_scaffold_export', :git => >> 'git://github.com/naaano/active_scaffold_export.git', :branch => 'ree' >> >> and bundle update active_scaffold_export >> >> >> >> >> On Tue, Jan 15, 2013 at 3:21 PM, Hernan Astudillo <[email protected]> wrote: >>> >>> I see, well the weird combination that i thought is for newer apps. >>> For older apps, you can use that passenger with REE. For newer ones, it's >>> way better to use unicorn. People can isolate each app with RVM with it's >>> own ruby and gem stack. >>> I know that passenger its easier than installing a web browser, maybe >>> there's too many people using it? >>> >>> I have never used passenger standalone. I think is never needed, since in >>> each app you can have an .htaccess to point another ruby environment. >>> That htaccess must have this: >>> >>> SetEnv GEM_HOME /home/xxxxx/.rvm/gems/ree-1.8.7-2011.03@313 ## point >>> this to your own REE or whatever ruby you're using >>> PassengerEnabled On >>> PassengerAppRoot /home/xxxxx/myapp >>> RailsEnv production >>> >>> >>> For those who don't depend on passenger, the best combination (very well >>> explained by github guys) is: >>> >>> nginx on front (apache2 works too, but nginx is a lot faster since can use >>> unix sockets) >>> unicorn running the app. >>> >>> The config is not hard: install nginx as normal, unicorn as gem, config >>> unicorn and nginx (there are a lot of gists with this for a copy/paste). The >>> only thing you have to worry and check is to add an init script to restart >>> the unicorns in case of server reboot. I have gist with this also. >>> There are lots of howto on internet for this. >>> >>> >>> >>> >>> >>> On Tue, Jan 15, 2013 at 2:14 AM, Sergio Cambra <[email protected]> wrote: >>>> >>>> I don't think is so weird combination, if you have some old apps running >>>> REE in the same server is easier to run REE than setup passenger-standalone >>>> to run 1.9, also I think you don't have dynamic processes with >>>> passenger-standalone. But upcoming passenger 4 will allow to setup ruby >>>> version per virtualhost. >>>> >>>> >>>> >>>> On Lunes, 14 de enero de 2013 13:36:36 Hernan Astudillo escribió: >>>> >>>> Besides, the upcoming rails 4 (which is the following to 3.2, there won't >>>> be a 3.3) will only support ruby 1.9.3+ >>>> >>>> >>>> >>>> >>>> >>>> On Fri, Jan 11, 2013 at 5:45 PM, Tim Uckun <[email protected]> wrote: >>>> >>>> Yea time to upgrade for sure :) >>>> >>>> >>>> >>>> On Sat, Jan 12, 2013 at 9:19 AM, Hernan Astudillo <[email protected]> >>>> wrote: >>>> > I can do that, but i don't have any REE 1.8.7 app which i can test it >>>> > against, so if you could test it, i'll branch it. >>>> > >>>> > IMHO Rails 3.2 and REE it's a weird combination... if you're in REE >>>> > because >>>> > of passenger, you can still use ruby1.9 with passenger. >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > On Thu, Jan 10, 2013 at 10:09 PM, Tim Uckun <[email protected]> wrote: >>>> >> >>>> >> Mmmmm. >>>> >> >>>> >> I guess I'll do that in a fork or something. >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> On Fri, Jan 11, 2013 at 11:43 AM, Hernan Astudillo <[email protected]> >>>> >> wrote: >>>> >> > Ok, the problem is that Enumerator is a ruby 1.9 class. In REE >>>> >> > there's a >>>> >> > Enumerable:Enumerator. >>>> >> > In 1.9 there's also binded as a module, so it could work by changing >>>> >> > Enumerator.each to Enumerable::Enumerator.each >>>> >> > >>>> >> > >>>> >> > On Thu, Jan 10, 2013 at 6:35 PM, Tim Uckun <[email protected]> >>>> >> > wrote: >>>> >> >> >>>> >> >> The error message is >>>> >> >> >>>> >> >> uninitialized constant ActiveScaffold::Actions::Export::Enumerator >>>> >> >> >>>> >> >> Gist for the stack trace https://gist.github.com/4505964 >>>> >> >> >>>> >> >> REE 1.8.7 Rails 3.2.11 >>>> >> >> >>>> >> >> -- >>>> >> >> You received this message because you are subscribed to the Google >>>> >> >> Groups >>>> >> >> "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. >>>> >> >> >>>> >> > >>>> >> > -- >>>> >> > You received this message because you are subscribed to the Google >>>> >> > Groups >>>> >> > "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. >>>> >> >>>> >> -- >>>> >> You received this message because you are subscribed to the Google >>>> >> Groups >>>> >> "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. >>>> >> >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups >>>> > "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. >>>> >>>> >>>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ActiveScaffold : Ruby on Rails plugin" 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/activescaffold?hl=en. -- You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails plugin" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/activescaffold?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
