Fellow Radiant-nites,
I'm trying to set a Radiant powered website on eApps and I'm running
into the same problem Jose was running into (see post below). Mainly
that my Radiant site is under a virtualhost for which I don't seem to
have much control and my RoR apps are in subdirectories.
This is how my website is configured in eApps (from the web control
panel):
Website: integrallis.virtual.vps-host.net
Type: Name-based
Document Root: /home/webadmin/integrallis.virtual.vps-host.net/html
Scripts: /home/webadmin/integrallis.virtual.vps-host.net/cgi-bin/
As you can see the Document Root is the /html directory under my virtual
host
I have a few Rails apps under the /html directory, one of them being
Radiant.
/html
+--+
+ integrallis <== radiant install
+ timetracker
+ courses
My site structure looks like:
Root <- Language Redirect
+-- en (english home - js redirect to home below)
+-- home
+-- about
+-- es (spanish home - js redirect to home below)
+-- home
+-- about
On my machine running under Locomotive things work like a charm.
I have no problem running Radiant at the root but I just don't seem to
be able to configure things to work that way. Just like Jose mentioned
in his post my Radiant Admin interface works just fine, the problem is
with all of the links inside of my Radiant website. They're all absolute
with respect to the ServerRoot e.g.
http://integrallis.virtual.vps-host.net
For example my home page under en is at:
http://integrallis.virtual.vps-host.net/integrallis/public/en/home
yet all the links in those pages are relative to the DocRoot (and hence
don't work)
The first *stupid* thing that I tried was to create a snippet called
baseurl and set it to /integrallis/public/ so that I could prepend that
to my urls. By adding that <r:snippet name="baseurl" /> I naively
thought, hey I can just do that in my layout and possibly in some of my
other snippets and I should be good to go. Well, that at least worked to
get the CSS and JS files loaded correctly in the main layout but things
quickly got ugly when I realized that I couldn't pass that value to
other radius tags. So I quickly abandoned that route.
Before I venture any further I was wondering what the definitive answer
is as to how to run Radiant is a subdirectory. I wouldn't mind making my
DocRoot point to
/home/webadmin/integrallis.virtual.vps-host.net/html/integrallis/public
As long as I can still run the other apps in a subdir (which they seem
to have no problem). But I can even find where to do that in this
webadmin console. I see the value for the DocRoot but it doesn't look
like you can change it. But I really need the ability to run multiple
Rails apps (which I'm already doing successfully). I have a few apps for
timetracking, course catalogue, etc.
Thanks,
Brian
Jose Jose wrote:
> 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.
>
>> 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.
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
