The much anticipated release of Radiant 0.6 is now a reality. In a few
moments you should be able use RubyGems to install Radiant from
Rubyforge.
For the complete list of what’s new see Sean C. excellent blog post:
What's New in Radiant 0.6 - Sean Cribbs
I plan to write up an official announcement on the blog in a few hours,
but for now, I’m off to bed. 
A huge thank you to all the contributors.
Enjoy!
–
John L.
http://wiseheartdesign.com
On 4/24/07, John W. Long [email protected] wrote:
The much anticipated release of Radiant 0.6 is now a reality. In a few
moments you should be able use RubyGems to install Radiant from Rubyforge.
It seems the svn repo has changed and the mental branch has been deleted
Trying to switch to http://dev.radiantcms.org/svn/radiant/trunk/
failed with this:
I do not want to switch to the gem so what should I use now please?
Ollivier,
You should switch to trunk/radiant, not plain trunk.
Sean
John W. Long wrote:
I plan to write up an official announcement on the blog in a few hours,
but for now, I’m off to bed.
Here we go:
http://radiantcms.org/blog/2007/04/24/radiant-0-6-lapidary-release/
And now, does anyone have time to help me update the wiki? We need to go
through and update all of the pages that only apply to 0.5.x.
–
John L.
http://wiseheartdesign.com
I had the same problem on my environment(apache2/fast-cgi, localhost
and DreamHost) before. I don’t know the reason of this(why rails need
to know HOME?), but I could stop the error. Try to add the following
line to the head of config/environment.rb:
ENV[‘HOME’] = ‘/home/username’ # change username to yours
Keita Y.
2007/4/25, Andrea F. [email protected]:
Hi all… i’ve just tried to install radiant on site5 but I got this
error:
…/config/…/vendor/rails/railties/lib/rails_generator/lookup.rb:
33:in expand_path': couldn't find HOME environment -- expanding~’ (ArgumentError)
from …/config/…/vendor/rails/railties/lib/rails_generator/
lookup.rb:33:in user_home' from ../config/../vendor/rails/railties/lib/rails_generator/ lookup.rb:105:inuse_component_sources!’
from …/config/…/vendor/rails/railties/lib/rails_generator/
lookup.rb:53:in included' from ../config/../vendor/rails/railties/lib/ rails_generator.rb:38 from /usr/lib/site_ruby/1.8/rubygems/custom_require.rb:27:inrequire’
from …/config/…/vendor/rails/activerecord/lib/…/…/
activesupport/lib/active_support/dependencies.rb:495:in require' from ../config/../vendor/rails/activerecord/lib/../../ activesupport/lib/active_support/dependencies.rb:342:innew_constants_in’
from …/config/…/vendor/rails/activerecord/lib/…/…/
activesupport/lib/active_support/dependencies.rb:495:in require' ... 12 levels... from ../config/../vendor/rails/railties/lib/initializer.rb: 43:inrun’
from …/config/…/lib/radiant/initializer.rb:32:in `run’
from ./…/config/environment.rb:11
from dispatch.fcgi:21
Does anybody know what I can do?
Thank you very much!
Il giorno 25/apr/07, alle ore 13:40, keita ha scritto:
I had the same problem on my environment(apache2/fast-cgi, localhost
and DreamHost) before. I don’t know the reason of this(why rails need
to know HOME?), but I could stop the error. Try to add the following
line to the head of config/environment.rb:ENV[‘HOME’] = ‘/home/username’ # change username to yours
Keita Y.
Hey it now works!!! Thank you very much!!!
-Andrea
What is the command to unpack the gem?
According to the wiki “radiant --database mysql target” should unpack
the gem into target directory, but it’s not working.
Have I got something wrong?
-Adam
Il giorno 27/apr/07, alle ore 07:37, Adam S. ha scritto:
What is the command to unpack the gem?
According to the wiki “radiant --database mysql target” should
unpack the gem into target directory, but it’s not working.
Maybe you need “radiant --database mysql target” to use radiant in
instance mode…if you want to unpack radiant you can use “gem unpack
radiant”
Andrea F.
The preferred way is to use the instance generator, as you did with
radiant --database mysql target and then use the rake radiant:freeze:gems or rake radiant:freeze:edge to put the source in
vendor/radiant. We’re not encouraging straight source checkouts anymore
because instances are far easier to keep up to date.
Sean
It’s in John’s post about the 0.6 release on the weblog. Anyone who has
time to copy it to the wiki, please do.
Sean
Can someone please explain to me if there is any reason not to freeze
your install to a particular version of rails?
Does rails run faster if it’s run from gem? or local vendor directory?
I also notice it has it’s own rails install… Wouldn’t it be better
to just run from the latest rails gem on hand? or make the gem
dependant on rails gem vx.x.x?
If it’s faster to use locally installed gems how do I force Radiant
not to use it’s bundled version of Rails?
When you catch a breath, could you please add a page to the Wiki about
this? You may recall that I wrote a number of times about my problems
with the release candidates and adding extensions, and how I found that
the easiest path for me was to svn mental, because otherwise none of
the other examples on the net (which assumed a full source in place)
were directly accessible within a gem install. In short, it was a
failure on my part to understand how to interact with a gem instance
Radiant from a development standpoint. As much as I want to use Gems
for ease of updates, I also want to learn how to hack in the same type
of environment.
Thanks again,
Walter
Adam S. wrote:
Can someone please explain to me if there is any reason not to freeze
your install to a particular version of rails?
It’s a matter of personal choice and disk space only. I assume you
meant to freeze Radiant because it includes Rails in its package.
Does rails run faster if it’s run from gem? or local vendor directory?
They’re both directories, so the speed is the same, essentially.
I also notice it has it’s own rails install… Wouldn’t it be better
to just run from the latest rails gem on hand? or make the gem
dependant on rails gem vx.x.x?
No. We tossed this one around and decided that to reduce
incompatibilities and issues with people lacking root access, etc, we
would package Rails along with Radiant. It saves a lot of headaches,
even though the gem size is larger.
If it’s faster to use locally installed gems how do I force Radiant
not to use it’s bundled version of Rails?
See above. However, if a newer bug-fix release of Rails comes out (i.e.
1.2.4, 1.2.5, etc) the trunk version will probably be updated to it soon
after.
Sean
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs