|
List Info
Thread: Need advice on Apache 1.3 Config
|
|
| Need advice on Apache 1.3 Config |
|
2006-09-25 15:49:57 |
|
Instant Rails 1.4 is almost ready for release. It replaces SCGI with Mongrel (when serving via Apache), and Mongrel also replaces WEBrick for serving up your app during development.
This release also updates Rails and to the latest version and the embedded Ruby to
1.8.5, and it will automatically configure RadRails with the correct paths.
The only thing left to do is to set up the Apache configuration to use mod_proxy to forward http requests the Rails apps being served by Mongrel. I'm not an Apache expert. With some research and experimentation I can figure this out, but I thought maybe one of you could save me a lot of time and help get this release out the door more quickly.
What I need is a Virtual Host setup and possibly an Alias setup for Apache 1.3 (*not* Apache 2) that will use mod_proxy to forward requests to a Rails app being served by Mongrel on a given port. Any help/suggestions would be appreciated.
Curt
|
| Need advice on Apache 1.3 Config |
|
2006-09-25 22:19:44 |
I am curious as to why you want to use apache 1.3? I thought
microapache might be a good fit instantrails
(http://microapac
he.amadis.sytes.net/). You can even get the 2.2
version with mod_proxy_balance although it seems that 2.2
doesn't get
along with php. He also has a micro mysql and microphp too
so it seems
like a good fit for what you are trying to do.
Anyway I could try and help you out. We are talking windows
only
right? All my linux servers are running 2.0.
On 9/26/06, Curt Hibbs <curt.hibbs gmail.com> wrote:
> Instant Rails 1.4 is almost ready for release. It
replaces SCGI with Mongrel
> (when serving via Apache), and Mongrel also replaces
WEBrick for serving up
> your app during development.
>
> This release also updates Rails and to the latest
version and the embedded
> Ruby to 1.8.5, and it will automatically configure
RadRails with the correct
> paths.
>
> The only thing left to do is to set up the Apache
configuration to use
> mod_proxy to forward http requests the Rails apps being
served by Mongrel.
> I'm not an Apache expert. With some research and
experimentation I can
> figure this out, but I thought maybe one of you could
save me a lot of time
> and help get this release out the door more quickly.
>
> What I need is a Virtual Host setup and possibly an
Alias setup for Apache
> 1.3 (*not* Apache 2) that will use mod_proxy to forward
requests to a Rails
> app being served by Mongrel on a given port. Any
help/suggestions would be
> appreciated.
>
> Curt
>
> _______________________________________________
> Instantrails-users mailing list
> Instantrails-usersrubyforge.org
> http://rubyforge.org/mailman/listinfo/instantrails-users
>
>
_______________________________________________
Instantrails-users mailing list
Instantrails-usersrubyforge.org
http://rubyforge.org/mailman/listinfo/instantrails-users
|
|
| Need advice on Apache 1.3 Config |
|
2006-09-26 02:10:27 |
|
On 9/25/06, Tim Uckun <gmail.com">timuckungmail.com> wrote:
I am curious as to why you want to use apache 1.3? I thought
microapache might be a good fit instantrails
(http://microapache.amadis.sytes.net/). You can even get the
2.2
version with mod_proxy_balance although it seems that 2.2 doesn't get
along with php. He also has a micro mysql and microphp too so it seems
like a good fit for what you are trying to do.
Anyway I could try and help you out. We are talking windows only
right? All my linux servers are running 2.0.
I don't *want* to use Apache 1.3, its just a historical fact of life since the current, Windows-only version of Instant Rails is a fork of EasyPHP.
I'm not willing to put *any* time into changing that (or the fact that the included MySQL is 4.1) because that would take development time away from Instant Rails 2, which is multi-platform and will use Apache 2 and MySQL 5.
The only reason this extra release of Instant Rails 1.x is happening at all is because SCGI is not no longer supported and I could not, in good conscience, leave an obsolete version of Instant Rails in circulation for the 6-9 months of so that it will take to get Instant Rails 2 out the door.
I was hoping that someone on the list had already done this (mod_proxy with Apache 1.3) and could just send me a sample configuration snippet. But it looks like I'm out of luck on that, so I'm just going to figure it out tonight.
Curt
On 9/26/06, Curt Hibbs <gmail.com">curt.hibbsgmail.com
> wrote:
>; Instant Rails 1.4 is almost ready for release. It replaces SCGI with Mongrel
> (when serving via Apache), and Mongrel also replaces WEBrick for serving up
> your app during development.
>
> This release also updates Rails and to the latest version and the embedded
> Ruby to 1.8.5, and it will automatically configure RadRails with the correct
> paths.
>;
> The only thing left to do is to set up the Apache configuration to use
> mod_proxy to forward http requests the Rails apps being served by Mongrel.
> I'm not an Apache expert. With some research and experimentation I can
> figure this out, but I thought maybe one of you could save me a lot of time
> and help get this release out the door more quickly.
>
> What I need is a Virtual Host setup and possibly an Alias setup for Apache
>; 1.3 (*not* Apache 2) that will use mod_proxy to forward requests to a Rails
>; app being served by Mongrel on a given port. Any help/suggestions would be
> appreciated.
>
>; Curt
>
> _______________________________________________
> Instantrails-users mailing list
> rubyforge.org">Instantrails-usersrubyforge.org
> http://rubyforge.org/mailman/listinfo/instantrails-users
>
>
|
[1-3]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|