Hi Mohit,

About rake/gempackagetask; you should pin rake to <= 10.0.2
I don't know if it's preferred (not much of a sysadmin guy), but I run my 
instances on nginx + passenger.

Also beware about this bug in 
edge: https://github.com/radiant/radiant-snippets-extension/issues/2
You can get around that by using radiant-snippets-extension 1.0.2

I've been meaning to fix both of these but still haven't got around to it.
Also, we are indeed still not on Rails 3.. we really need a new surge of 
activity here :/


Happy holidays!
B

Op vrijdag 21 december 2012 11:28:04 UTC+1 schreef Mohit Sindhwani het 
volgende:
>
>  Hi Guys, 
>
> It's the end of the year and so I thought I would update my sites that are 
> using older versions of Radiant to the latest.  I noticed that there was 
> mention that 1.0 onwards would work with Rails 3 but I couldn't find a 
> simple way to make that work since I noticed that radiant seems to vendor 
> rails 2.3.14. 
>
> I'm on Windows and have Ruby 1.8.7, 1.9.2 and 1.9.3 installed.  When in 
> 1.9.3, I tried to install the gem (that worked) and then I tried to run 
> bundle exec bootstrap.  I got an error and then I tried the same after 
> installing the gem in 1.8.7 (switched using pik).  In both cases, I got an 
> error similar to the below 
>
> E:\projects\radiant\test_v10>bundle exec rake production db:bootstrap 
> NOTE: Gem.source_index is deprecated, use Specification. It will be 
> removed on or after 2011-11-01. 
> Gem.source_index called from 
> C:/Ruby187/lib/ruby/gems/1.8/gems/rails-2.3.14/lib/rails/gem_dependency.rb:21.
> rake aborted! 
> ERROR: 'rake/gempackagetask' is obsolete and no longer supported. Use 
> 'rubygems/package_task' instead. 
>
>
> Any ideas what I may be doing wrong? 
>
>
> Finally, a couple of other small things: 
> * thanks "saalon" for sharing your experience on migrating to 1.0. 
> * what's the preferred deployment server now?  I'm still deployed on 
> Mongrels for the longest time since I'm on an older version 
>
> Best Regards, 
> Mohit. 
>
>
>
>  

Reply via email to