# Basic InstantRails CGI implementation

**URL:** <https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720>\
**Category:** Rails\
**Created:** [October 26, 2006, 5:26pm UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720 "2006-10-26T17:26:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![RSVince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/f475e1/32.png) [@RSVince](https://www.ruby-forum.com/u/RSVince)\
**Post date:** [October 26, 2006, 5:26pm UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720/1 "2006-10-26T17:26:11Z")

</div>

I have installed Instantrails 1.4 and am interested in simply deploying  
such  
that someone can hit my site on port 80, via Apache, and be into my  
rails  
site. I’m not yet interested in setting up FastCGI, etc. I cannot change  
the  
web hosts file.

It seems that I can, from within InstantRails, go to “Congifugre Rails  
Apps,” check off my app, then “Start with Mongrel”. This works fine as  
long  
as I come into [http://mysite:3000](http://mysite:3000) but not when I come into  
[http://mysite](http://mysite).

What am I missing about Instant Rails that is making it seem  
not-so-instant  
in the case of deployment here? Thanks, R. Vince

---

<div class="post-metadata">

**Author:** ![RSVince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/f475e1/32.png) [@RSVince](https://www.ruby-forum.com/u/RSVince)\
**Post date:** [October 26, 2006, 6:18pm UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720/2 "2006-10-26T18:18:19Z")

</div>

On 10/26/06, R. Vince [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> What am I missing about Instant Rails that is making it seem not-so-instant  
> in the case of deployment here? Thanks, R. Vince

You have to set up you Apache configuration for proxy port 80 requests  
for your app’s domain to Mongrel running on whatever port you have  
chosen.

Edit the apache config file through the Instant Rails menus and look  
at the end of the file where you’ll see working configurations for the  
cookbook and typo apps.

Curt

---

<div class="post-metadata">

**Author:** ![RSVince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/f475e1/32.png) [@RSVince](https://www.ruby-forum.com/u/RSVince)\
**Post date:** [October 26, 2006, 9:16pm UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720/3 "2006-10-26T21:16:40Z")

</div>

Curt H. wrote:

> Edit the apache config file through the Instant Rails menus and look  
> at the end of the file where you’ll see working configurations for the  
> cookbook and typo apps.
> 
> Curt

Thanks Curt,

But this requires editing the Windows.hosts file, doesn’t it? -Ralph

---

<div class="post-metadata">

**Author:** ![RSVince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/f475e1/32.png) [@RSVince](https://www.ruby-forum.com/u/RSVince)\
**Post date:** [October 27, 2006, 12:37am UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720/4 "2006-10-27T00:37:06Z")

</div>

On 10/26/06, Ike [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Thanks Curt,
> 
> But this requires editing the Windows.hosts file, doesn’t it? -Ralph

It does if you don’t have a real domain name mapped to the machine’s  
IP address, then you’d need to edit the HOSTS file to fake the domain  
name (this is only good for development).

What you do really depends on what it is that you are trying to  
accomplish. If all you want to do is to do some light production  
serving on port 80, then you could just forego Apache completely  
(don’t let it start up), and configure Mongrel to serve up the rails  
app on port 80.

Curt

---

<div class="post-metadata">

**Author:** ![RSVince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/f475e1/32.png) [@RSVince](https://www.ruby-forum.com/u/RSVince)\
**Post date:** [October 27, 2006, 3:45am UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720/5 "2006-10-27T03:45:24Z")

</div>

I have Tomcat running with Apache, coming in on port 80, to a dedicated  
IP address. It seems to me I am best to let mongrel run, on port 3000  
under this configuration, and do NOTHING in httpd.conf. Rather, to have  
the URL used to hit the Rails apps com in with the :3000 appended onto  
the IP address. This may be the most efficient way for me since that  
would bypass Apache altogher, and in so doing, Rails is marginally  
quicker, as might be my Apache/Tomcat stuff runniing on port 80. Does  
that sound correct to you? Thanks, Ralph

---

<div class="post-metadata">

**Author:** ![RSVince](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/f475e1/32.png) [@RSVince](https://www.ruby-forum.com/u/RSVince)\
**Post date:** [October 27, 2006, 5:40am UTC](https://www.ruby-forum.com/t/basic-instantrails-cgi-implementation/73720/6 "2006-10-27T05:40:57Z")

</div>

On 10/26/06, Ike [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> I have Tomcat running with Apache, coming in on port 80, to a dedicated  
> IP address. It seems to me I am best to let mongrel run, on port 3000  
> under this configuration, and do NOTHING in httpd.conf. Rather, to have  
> the URL used to hit the Rails apps com in with the :3000 appended onto  
> the IP address. This may be the most efficient way for me since that  
> would bypass Apache altogher, and in so doing, Rails is marginally  
> quicker, as might be my Apache/Tomcat stuff runniing on port 80. Does  
> that sound correct to you? Thanks, Ralph

Sure, nothing wrong with that.

Curt
