From: "Mike Dalessio" <mike@csa.net>
To: "Florian Weimer" <fweimer@bfk.de>
Cc: "Thomas Adam" <thomas.adam22@gmail.com>,
"Eric Wong" <normalperson@yhbt.net>,
git@vger.kernel.org
Subject: Re: [PATCH] instaweb: support for Ruby's WEBrick server
Date: Mon, 17 Sep 2007 09:55:35 -0400 [thread overview]
Message-ID: <618c07250709170655p649a71fdwcfaaa4d5bfcd06ff@mail.gmail.com> (raw)
In-Reply-To: <823axd32dz.fsf@mid.bfk.de>
I could generate a second /bin/sh script to run
"ruby .../webrick.rb"
This would assume that 'ruby' was in the user's $PATH, but that seems
like a reasonable expectation.
The drawback is that we'd be generating TWO scripts, one ruby script
to invoke the server, and one shell script to run the ruby
script. This seems a little ... circuitous.
Another idea is to hack the $httpd variable to contain a command
string like "ruby .../webrick.rb", with the drawback then being a lack
of obviousness, since the convention is that the variable contains the
same command as the --httpd argument, and is named the same as
the <webserver>_conf() functions.
On 9/17/07, Florian Weimer <fweimer@bfk.de> wrote:
> * Thomas Adam:
>
> > This is what /usr/bin/env is useful for, but it's not that portable.
>
> Yeah, it's /bin/env exclusively on some systems. 8-(
>
> --
> Florian Weimer <fweimer@bfk.de>
> BFK edv-consulting GmbH http://www.bfk.de/
> Kriegsstraße 100 tel: +49-721-96201-1
> D-76133 Karlsruhe fax: +49-721-96201-99
>
--
mike dalessio
mike@csa.net
prev parent reply other threads:[~2007-09-17 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <618c07250709161935g333f0536q31b453bd58f2d75d@mail.gmail.com>
2007-09-17 11:55 ` [PATCH] instaweb: support for Ruby's WEBrick server Eric Wong
2007-09-17 12:02 ` Thomas Adam
2007-09-17 12:25 ` Florian Weimer
2007-09-17 13:55 ` Mike Dalessio [this message]
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=618c07250709170655p649a71fdwcfaaa4d5bfcd06ff@mail.gmail.com \
--to=mike@csa.net \
--cc=fweimer@bfk.de \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=thomas.adam22@gmail.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 NNTP newsgroup(s).