From: Ross Fairbanks <ross.fairbanks@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Rack-Legacy: A rack handler for serving legacy CGI and PHP scripts
Date: Mon, 29 Mar 2010 15:17:53 -0700 (PDT) [thread overview]
Message-ID: <f38c2085-e3e9-4b2e-a449-8df993da88e7@y14g2000yqm.googlegroups.com> (raw)
In-Reply-To: <545fed2e-9c3a-42ca-8598-5113ba8a3f02@z4g2000yqa.googlegroups.com>
Thanks Eric, this is really useful just giving it a try now. The only
minor install issue I found is on Ubuntu you need to make sure you
install PHP from the php5-cgi package rather than the php5 package (as
it doesn't include the CGI handler).
Ross
On Mar 26, 1:30 am, Eric Anderson <e...@pixelwareinc.com> wrote:
> Wanted to post a note about bit of code I have written which assists
> the development of apps that have some PHP/CGI code running alongside
> Ruby code. It help avoid having to setup and configure Apache (or
> whatever your preferred production stack is) just to do development on
> a mixed code app. It basically a simple handler that execs the CGI and
> puts the results back through rack. In the case of PHP it uses the php-
> cgi to do the dirty work.
>
> I have put some basic info and usage up athttp://wiki.github.com/eric1234/rack-legacy/.
> I welcome others to give a try. It should work under any Rack-
> compatible environment although I had to do some adjustments to get it
> to work under Rails 2.3.5 (Rails 3.x beta is untested).
>
> This is my first rack module so I welcome feedback. Hope it is as
> useful for others as it has been for me.
>
> Eric
To unsubscribe from this group, send email to rack-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
next prev parent reply other threads:[~2010-03-29 22:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 0:30 Rack-Legacy: A rack handler for serving legacy CGI and PHP scripts Eric Anderson
2010-03-29 22:17 ` Ross Fairbanks [this message]
2010-03-31 2:41 ` Mat Schaffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f38c2085-e3e9-4b2e-a449-8df993da88e7@y14g2000yqm.googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).