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 -
Bodhi,
What I've finally done is the following.
In my apache httpd.conf
I've set
Listen 3000
Listen 3001
And I've created virtual hosts for each of my radiant sites using those
ports.
VirtualHost *:3000
ServerName myserver
DocumentRoot /pathtomyapp/myapp1/public/
Directory
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
The easiest way is to set your DNS to point to your radiant sub dir. Else you could fiddle with the routes.rb file to fit your needs.On 11/13/06,
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,I've managed to set two radiant sites using apache 1.3 and fcgi. Now I canaccess them site at
Thanks for the reply.
Do you know where exactly do I have to make the changes?
Perhaps # Site URLs ?
Jose.
The easiest way is to set your DNS to point to your radiant sub dir. Else
you could fiddle with the routes.rb file to fit your needs.
On 11/13/06, [EMAIL PROTECTED] [EMAIL
I think what you describe should be fairly easy to solve with routes.rb hacks. Else your COULD create an url filter in the front controller to add /myApp/ in front of all incoming URLS. Sorry I can't be more specific at the moment...I'm at work and am supposed to be debugging some 2K lines of .Net
Jose,I'd fiddle with the lines below (which correspond to lines 56 in routes.rb):
# Site URLs map.with_options(:controller = 'site') do |site| site.homepage '', :action ="" 'show_page', :url ="" '/' site.not_found 'error/404', :action ="" 'not_found'
site.error 'error/500', :action ="" 'error' #
Jose,That Rails ticket is exactly what I was talking about. I tried and it worked very well. The only problem I see if the URL requests collide with some controller/setting of Radiantif you have a development environment tried there first before deploying.
On 11/13/06, [EMAIL PROTECTED] [EMAIL
Ruben,
I also found this http://www.hostingrails.com/forums/rails_coding_thread/37
I think this is what I need. It says that
ActionController::AbstractRequest.relative_url_root Essentially tells
Rails to tack on an extra '/subdir' to every URL it writes.
I've already used
Jose,It is a common task. The disconnect happens between Radiant and the generated page. Radiant will know to add the URL prefix, but any manual links won't be automatically updated/parsed on the way out.
If you are using Apache, make sure to put this line in your .htaccess: RewriteBase
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
11 matches
Mail list logo
