On Monday 15 August 2005 12:01, BearItAll wrote:
> Anyway I got web space on an ISP that supports ruby rails, the big
> difference is that on my local server I ran rails from the script
> 
> script/server
> 
> Then access with the likes of http://web:3000

This is the "development mode" for rails, using the Ruby "Webrick" web 
server.
 
> But ISP's being ISP's they don't actually tell you what changes you have
> to make to the way you access your site or add to the available
> applications.

Hmm, odd.  Most of the time they do.  If they "support rails", then they 
probably have a certain setup for it.  Most likely, they're probably 
either setting it up so you can run it with Apache/cgi or Apache/fcgi, 
maybe lighthttpd/fcgi.
 
> I know that 'script/server' does not expose the site on port :3000. But I
> have a feeling that it shouldn't.

No, if they're an ISP there are probably hundreds of other people using the 
same server, most likely the same IP, and only one port 3000.  It's 
vaguely possible they'd let you run Webrick on another port so that you 
could do development-mode work, but most likely they just want you to run 
cgi/fcgi processes.  (Lower server load and memory requirements)
 
> So, what is normal practise for ruby rails out on your ISP's servers, for
> adding projects to the 'server' and accessing the results?

I don't know what the normal ISP thing is, but the first step is trying to 
figure out what pages they're serving for your site.  Say your site is 
http://my.isp.com/~bearitall/ your files might be served from your home 
directory (say /home/bearitall) in the subdirectory public_html.  The next 
trick is to get your rails "public" directory seen by the web server, and 
to get it to pay attention to the .htaccess file in that directory.

Once you do that, you might simply be able to access the site as 
http://my.isp.com/~bearitall/controller/method

Ben