Bodhi, You asked
> If you are using 2 ports, why dont you just use / as the base-url for > radiant? Or are you doing this already? I'm using / as the base url already. > You could try using different names (change ServerName in httpd.conf) > instead of ports: > > http://example.com:3000/myapp -> http://myapp1.example.com > http://example.com:3001/myapp2 -> http://myapp2.example.com This would be good. But since we haven't pointed our domain to our hosting plan yet, I think it's not possible. > If you have /myapp1 symlinked to rails/app/public then if you access > http://example.com/myapp1/ you will get the right page, but all the > links to other child pages will be rendered as eg. http://example.com/ > child/page instead of http://example.com/myapp1/child/page (this is > how I understood the problem you were having...?) Thats exactly the problem I was having. > If you add a page *in radiant* below (I think I mistakenly said > 'above' in a previous mail) the home-page for your app (and dont > change the rails-base-path or whatever the configuration option is), > going from: > > > / > +-- child/ > +-- page/ > > to: > > / > +-- myapp1/ <-- new page in radiant > +-- child/ > +-- page/ Oooh ok, it didn't work for me before because I was just changing my home slug from / to /subdir/ Now I see what you meant. But I've already created a bunch of pages under one main section of the site and using your method now would mean starting over again and I can't afford it. However, I'll have it in mind : ) > I'm not 100% sure that this will work using apache-fcgi (we are a > lighty+fcgi shop here), I've tried to set up lighthttpd but I get the following error on make mod_webdav.c: In function `webdav_delete_file': mod_webdav.c:536: warning: unused parameter `p' mod_webdav.c: In function `webdav_copy_file': mod_webdav.c:664: warning: unused parameter `p' mod_webdav.c: In function `webdav_has_lock': mod_webdav.c:1155: parse error before `int' mod_webdav.c:1198: `has_lock' undeclared (first use in this function) mod_webdav.c:1198: (Each undeclared identifier is reported only once mod_webdav.c:1198: for each function it appears in.) mod_webdav.c:1153: warning: unused parameter `con' mod_webdav.c:1153: warning: unused parameter `p' mod_webdav.c:1153: warning: unused parameter `uri' mod_webdav.c:1199: warning: control reaches end of non-void function make[2]: *** [mod_webdav_la-mod_webdav.lo] Error 1 make[2]: Leaving directory `/usr/home/src/lighttpd-1.4.13/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/home/src/lighttpd-1.4.13' make: *** [all] Error 2 Thanks for your attention Bodhi I really appreciate it. jose. > Jose, I've replied to both your emails here... > > > On 15/11/2006, at 10:01 AM, [EMAIL PROTECTED] wrote: > >> Bodhi, >> >> What I've finally done is the following. >> >> In my apache httpd.conf >> >> I've set > > <snipped apache config> > >> All my site's images go into their public/images directory to >> maintain the >> relative urls in my pages. >> >> This is the best I can do for now. Both sites run from their own >> directory >> on different ports and I don't have to fiddle with radiant. >> >> Please tell me what you think. > > If you are using 2 ports, why dont you just use / as the base-url for > radiant? Or are you doing this already? > > You could try using different names (change ServerName in httpd.conf) > instead of ports: > > http://example.com:3000/myapp -> http://myapp1.example.com > http://example.com:3001/myapp2 -> http://myapp2.example.com > > What I meant by my previous email was: > > If you have /myapp1 symlinked to rails/app/public then if you access > http://example.com/myapp1/ you will get the right page, but all the > links to other child pages will be rendered as eg. http://example.com/ > child/page instead of http://example.com/myapp1/child/page (this is > how I understood the problem you were having...?) > > If you add a page *in radiant* below (I think I mistakenly said > 'above' in a previous mail) the home-page for your app (and dont > change the rails-base-path or whatever the configuration option is), > going from: > > > / > +-- child/ > +-- page/ > > to: > > / > +-- myapp1/ <-- new page in radiant > +-- child/ > +-- page/ > > (remember, this change is made only in radiant) Then links to child > pages will be rendered as http://example.com/myapp1/child/page > > I'm not 100% sure that this will work using apache-fcgi (we are a > lighty+fcgi shop here), as it might strip off the myapp1/ part of the > url. Also, when using this method, you have to be careful about > linking to static content in the public directory, and its not > completely DRY... > > But if you have it working satisfactorily now, don't worry about > changing it :) > > 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
