# Radiant on eApps

**URL:** <https://www.ruby-forum.com/t/radiant-on-eapps/76392>\
**Category:** Radiant CMS\
**Created:** [November 18, 2006, 7:36am UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392 "2006-11-18T07:36:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Sam-Bodden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/4da419/32.png) [@Brian\_Sam-Bodden](https://www.ruby-forum.com/u/Brian_Sam-Bodden)\
**Post date:** [November 18, 2006, 7:36am UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392/1 "2006-11-18T07:36:13Z")

</div>

Hi,  
Has anybody succesfully configured Radiant on an [eapps.com](http://eapps.com) VPS? I have a  
horrible time following the instructions at  
[http://support.eapps.com/index.php?\_m=knowledgebase&\_a=viewarticle&kbarticleid=108](http://support.eapps.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=108)  
I just can’t get the routes.rb modifications they are talking about to  
work. I’m a RoR newbie so the part that is really confusing is that they  
have a directory structure like:

virtual\_domain/  
html/  
app/  
components/  
config/  
…

and they tell me that to add my app (in this case Radiant) under /html  
and then modify the routes.rb (I’m assuming the one at html/config (not  
the one under html/app/config). Any ideas?

Thanks,  
Brian

---

<div class="post-metadata">

**Author:** ![Brian\_Sam-Bodden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/4da419/32.png) [@Brian\_Sam-Bodden](https://www.ruby-forum.com/u/Brian_Sam-Bodden)\
**Post date:** [November 18, 2006, 7:42am UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392/2 "2006-11-18T07:42:14Z")

</div>

I’m not sure why you have a RAILS\_ROOT/app/config directory?

You want to edit RAILS\_ROOT/config/routes.rb

Here is more info on routes:  
[http://manuals.rubyonrails.com/read/chapter/65#page164](http://manuals.rubyonrails.com/read/chapter/65#page164)

---

<div class="post-metadata">

**Author:** ![Brian\_Sam-Bodden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/4da419/32.png) [@Brian\_Sam-Bodden](https://www.ruby-forum.com/u/Brian_Sam-Bodden)\
**Post date:** [November 18, 2006, 1:58pm UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392/3 "2006-11-18T13:58:32Z")

</div>

Hey Brian,

You’re right, Eapps instructions are not really helpful. I spent a  
whole day trying to get a RoR site working with Eapps. All kinds of  
issues. I understand your frustration.

You shouldn’t have an app/config directory. That’s odd. It should be  
virtual\_domain-\>html-\>config. Maybe you should delete the site and  
start over - or delete everything under html and run ‘rails newapp’?

Do you see anything interesting in /var/log/httpd/error\_log? or  
/var/log/httpd/suexec.log?

-Todd  
Send direct to me if you want to take this off list and we can report  
back the solution to the list or dev wiki with Eapps instructions.

---

<div class="post-metadata">

**Author:** ![Brian\_Sam-Bodden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/4da419/32.png) [@Brian\_Sam-Bodden](https://www.ruby-forum.com/u/Brian_Sam-Bodden)\
**Post date:** [November 19, 2006, 9:13pm UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392/4 "2006-11-19T21:13:19Z")

</div>

> Maybe you should delete the site and  
> start over - or delete everything under html and run ‘rails newapp’?

Brian I think this suggestion Todd has is the best. “delete  
everything” and then create a new rails app right there on your host.  
Once you can get that working then you can move your code in place.

---

<div class="post-metadata">

**Author:** ![Brian\_Sam-Bodden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/4da419/32.png) [@Brian\_Sam-Bodden](https://www.ruby-forum.com/u/Brian_Sam-Bodden)\
**Post date:** [December 31, 2006, 8:42pm UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392/5 "2006-12-31T20:42:48Z")

</div>

Michael et all,  
You guys were right it was simply a matter of starting from scratch.  
The  
instructions at:

[http://support.eapps.com/index.php?\_m=knowledgebase&\_a=viewarticle&kbarticleid=108&nav=0,1](http://support.eapps.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=108&nav=0,1)

Although poorly written are mostly correct. What they don’t explain  
quite right is that in eApps the DocRoot is the …/html directory. The  
setup comes with the plain vanilla RoR app installed there. So you can  
see the welcome page if you got to:

[http://yoursite/public](http://yoursite/public)

They recommend installing other Rails apps under /html so you’ll end up  
with something like:

html/  
±-+ror\_app1  
+ror\_app2

- …

The database.yml for MySQL as shown in the document is wrong:

development:  
adapter: mysql  
database: \_development  
username:   
password:   
socket: localhost

To get it to work I used this:

development:  
adapter: mysql  
database: radiant\_dev  
username: radiant  
password: \*\*\*\*\*\*\*  
socket: /var/lib/mysql/mysql.sock

Also for Radiant you should grab the dispatch.\* files from a fresh app.  
It somehow does like that ones distributed with Radiant. After that  
things should work (except for the whole Radiant in a subdirectory  
problem for which I’m still trying to figure out a good solution)

I’ll put a How To on the Wiki once I get that last glitch worked out.

Thanks,  
Brian

Michael J. wrote:

> > Maybe you should delete the site and  
> > start over - or delete everything under html and run ‘rails newapp’?
> 
> Brian I think this suggestion Todd has is the best. “delete  
> everything” and then create a new rails app right there on your host.  
> Once you can get that working then you can move your code in place.

---

<div class="post-metadata">

**Author:** ![Brian\_Sam-Bodden](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/4da419/32.png) [@Brian\_Sam-Bodden](https://www.ruby-forum.com/u/Brian_Sam-Bodden)\
**Post date:** [March 13, 2009, 2:25pm UTC](https://www.ruby-forum.com/t/radiant-on-eapps/76392/6 "2009-03-13T14:25:04Z")

</div>

cheap hosting for students [http://javaprovider.net](http://javaprovider.net) no one can beat them
