From: James Britt <james_b@...>
Date: 2005-08-16T01:12:46+09:00
Subject: Re: Rails the daemon side of things

BearItAll wrote:
> Hello.
> 
> While learning Ruby rails I just had it on my Linux server and used a
> Linux client to edit/view/debug/debug/debug.. etc. We got along very
> nicely, much better than I have with any other web development
> environment. (HTML and I simply don't like each other).
> 
> 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
> 
> My ISP seems to be running it as background process. Which seems sensible
> because I don't want to have to keep a ssh terminal open just so I can
> keep the site up.

Forgive me if I've so missed your question that I'm casting in the dark, 
but have you read the assorted Rails tutorials at rubyonrails.com, and 
do you know the difference between WEBrick and, say, Apache?

script/server will kick off an instance of WEBrick, running, by default, 
on port 3000.  Almost any ISP will run Apache or some other proper Web 
server, not WEBrick, and will serve Web pages on port 80.  And Rails 
apps will likely be processed as either CGI of FastCGI.

See the Rails tutorials on how to run Rails apps as CGI processes.

James

-- 

http://www.ruby-doc.org - The Ruby Documentation Site
http://www.rubyxml.com  - News, Articles, and Listings for Ruby & XML
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com  - Playing with Better Toys