Bodhi, Thanks for your reply. I'm a bit confused with what you suggest. I've already changed the root url to myapp1 but that doesn't correct the links.
Consider I have a symbolic link from /home/myapp1/public to /public_html/myapp1. That way, when I go to www.mydomain.org/myapp1 I'm going into the public/dispatch.fcgi of my app, which works, but doesn't correct the links, because they are still rendered as /link not /myapp1/link. So, if I do what you suggest, it simply moves www.domain.org/myapp1 to www.domain.org/myapp1/myapp1. And still, it doesn't correct the links. My question is, if I use myaap1 as the slug for the root page as you suggest, what else do I need to do? Do I have to set that up in the apache config? I'll paste here what Dave Thomas suggests so you can have a clearer idea of what I have. "If you don't like dedicating an entire virtual host, perhaps because you want the Rails application to be part of a larger site, that's possible too. All you need to do is make a symbolic link to your public directory from wherever you want the application to live. Imagine that you have community site that needs a forum and you fancy the URL http://www.example.com/community/forum, which is just a symbolic link to the application directory /var/application/railsforum/public. Voila! The symbolic link approach will automatically be picked up by Rails and all the links created by the view helpers, such as image_tar og link_to, will be rewritten to fit under the proper path." But it really doesn't correct anything! Jose > > On 14/11/2006, at 8:13 AM, [EMAIL PROTECTED] wrote: > >> Hi, >> >> I found this by John Long on the ruby archive >> http://www.ruby-forum.com/topic/82446 >> >> He wrote: >> "I wouldn't recommend running Radiant in a sub-directory. It isn't >> designed with this in mind.If you'd like to just have Radiant serve >> files >> from a specific directory, the simplest thing would be to change the >> rewrite rules inthe .htaccess file (or equivalent for your Web >> server). >> What exactly are you trying to do? and why?" >> >> What I'm trying to do is to set two different websites like this: >> >> mydomain.org/app1 >> mydomain.org/app2 > > For a really simple (but not the best) solution, you could make a > root-page for each app with the same slug as the subdirectory. eg. > for app1: > > app1/ > +-- home/ > +-- about/ > +-- contact/ > > etc... One problem that you might have is if you use <r:find>, then > it would start to get a little bit messy. But after thinking for a > bit, it might make more sense for the people that manage the site > arent really technical... keep us posted on what you come up with :) > > bodhi > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
