Release of how to set up on DreamHost the proper way coming

This is my first post here, so bear with me. :slight_smile:

I felt, as since there has been previous interest and current interest,
and that current ‘methods’ of this are not working AT ALL. shiver I
spent a few days fighting to get Radiant running; it is exactly what I
need; I hate PHP CMS setups (mostly cause they are unwieldy at best,)
and other CMSs (Ruby and otherwise) do not fit my needs well. Granted
Radiant doesn’t fit it perfectly, it does pretty good.

Anyways, off topic; as since all the other sites (not JUST Radiant’s)
for setup on Dreamhost are incorrect (Some of them are so far off it’s
pathetic,) I am assembling a set of instructions on proper setup (And
moreso especially FastCGI support – Evil to work with, to say the
least) and will be releasing them within the week.

As well, I may assemble a tarball for an unpacked site as since I’m not
overly graceful with the setup of this package yet that people can just
tar -xvf it and follow a much shorter set of instructions. For this, it
would be nice to see if someone else is on a different Dreamhost server
to test this idea (IE:- ruby/etc in same location on each server)

Anyways, cheers all!
BladedThoth

Andrew,

I’ll be interested in giving that a read. I have an account with them
and am surprised so many people have had problems installing Radiant
there. Maybe my experience is an anomaly, but I was up and running
with Radiant in about 5-7 minutes.

Well, if you insist in intalling from gem, then I suggest you first
set Radiant in development mode, and kill all FGCI/Rails/Ruby
pocesses associated with Radiant. a good way is to run the command
“top” in the shell and see which FCGI/Rails/Ruby are owned by Radiant.
Then very ungracefully kill them (kill -9 pid). Once you’ve killed all
related pid’s, then fix whatever you need to fix and then point your
browser to our Radiant install.

I cannot emphasize enough how easy it was to install from source though.

May have a fix for this: Waiting for my backup site to come online on
DreamHost. DreamHost’s DNS servers seem to be having issues ATM again.

BladedThoth

Okay, got source to work with minor modifications. Looks like
essentially like radiant --unpack. It seems that the instanced version
is not liking the detection of bluecloth on --some-- hosts, and also
looks like it might be a gem issue moreso than anything else.

I am going to write on how to use the source on installing, because for
all I know, gem installations which are instanced are bugged on
DreamHost and elsewhere, and I do not want to encourage this, even if
theoretically easier to upgrade.

Thanks again!
Andy

This could sound stupid: tried RAILS_ROOT/lib ?

They are added at the beginning of environment loading…

Tried that too. No avail.

Maybe adjusting your .htaccess file instead?
SetEnv GEM_HOME /usr/lib/ruby/gems/1.8
SetEnv GEM_PATH /usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems

Maybe this wiki page could help you on your quest:

http://wiki.rubyonrails.com/rails/pages/HowToUseMultipleGemRepositories

Tried this too
. Reading more online; It seems that Dreamhost isn’t the only site
plagued with the bluecloth bug, and not the only sourcecode bugged by
this glitch either (Search bluecloth on Google; More specifically that
error) – I am about to try from the source itself; I have a suspicion
it’s gonna be about the same, if not the same…

Thanks all for helping. I was going to be content posting how to do this
with --unpack, but seeing there is a really good chance --unpack is
going away, I need to figure this out for myself and others (With your
help) :slight_smile:

Andy

Okay. Got the fix started. Here’s the problem (Again) – It nags that
bluecloth does not exist. I’ve dropped bluecloth.rb in RAILS_ROOT, no
avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again.
Can’t access GEM_HOME. I’ve ran out of ideas. radiant and radius is
seen, as is everything else. Just not seeing bluecloth. My previous fix
by tossing bluecloth into RAILS_ROOT isn’t working now. Ideas?

Just as an FYI, I’ve tossed the following two lines into my dispatch.cgi
and dispatch.fcgi. No luck:

ENV[‘GEM_HOME’]=’/usr/lib/ruby/gems/1.8’
ENV[‘GEM_PATH’]=’/usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems’

It made it so that ruby would see my gem folder.

Ideas on how to make radiant see bluecloth?

I am guessing it may be server-related then.

Yeah, I know what you mean. Windows; seconds (Under Instant Rails) - my
home Fedora server. All goes fine. Get onto DreamHost, try to do it
‘vanilla’, no luck. Try to follow all the sites out there; no luck. Part
of the problem is that the shebang of all the dispatches point to
something totally different, for one. Part two, is that the gems
(locally installed) are not seen by the global ruby app for processing,
even when made fully visible. (chmod)

Anyways, got to go to work. TTFN
BladedThoth

Yes I am. Had to check myself to make sure. :slight_smile:

This DreamHost thing is whoppin’ my butt. I got radiant --unpack working
fine with a buncha small changes, but without --unpack, it refuses to
run. The error is as such:

/usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:18:in
`require__’: no such file to load – bluecloth (MissingSourceFile)

It picks up Radiant and everything now, but when I try the bluecloth mod
as desribed on the Wiki, no luck. Doesn’t seem to make a lick of
difference, no matter where I put that. I don’t know what would make the
unpack and the instance version is any different really (Looking through
it all. Tons of sifting)

Thanks again!

Andrew,

I HIGHLY suggest you install from source. Will make your life much
easier.

Andrew,

Are you running on production mode?

On 1/16/07, Andrew K. [email protected] wrote:

Okay. Got the fix started. Here’s the problem (Again) – It nags that
bluecloth does not exist. I’ve dropped bluecloth.rb in RAILS_ROOT, no
avail. vendor/, nope. vendor/plugins/, nope again. GEM_PATH, nope again.
Can’t access GEM_HOME. I’ve ran out of ideas. radiant and radius is
seen, as is everything else. Just not seeing bluecloth. My previous fix
by tossing bluecloth into RAILS_ROOT isn’t working now. Ideas?

This could sound stupid: tried RAILS_ROOT/lib ?

They are added at the beginning of environment loading…

Just as an FYI, I’ve tossed the following two lines into my dispatch.cgi
and dispatch.fcgi. No luck:

ENV[‘GEM_HOME’]=’/usr/lib/ruby/gems/1.8’
ENV[‘GEM_PATH’]=’/usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems’

Maybe adjusting your .htaccess file instead?

SetEnv GEM_HOME /usr/lib/ruby/gems/1.8
SetEnv GEM_PATH /usr/lib/ruby/gems/1.8:/home/bladedthoth/.gems

Maybe this wiki page could help you on your quest:

http://wiki.rubyonrails.com/rails/pages/HowToUseMultipleGemRepositories


Luis L.
Multimedia systems

Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs