From: Scytrin dai Kinthra <scytrin@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: Rack-compatible server issues
Date: Sat, 5 Dec 2009 14:55:12 -0800 [thread overview]
Message-ID: <5a9d52bd0912051455u3411ed02n770f60244cb89d4f@mail.gmail.com> (raw)
In-Reply-To: <200912052149.36041.ibc@aliax.net>
Starting the script directly, rackup is only one way to do things.
On Sat, Dec 5, 2009 at 12:49, Iñaki Baz Castillo <ibc@aliax.net> wrote:
> El Sábado, 5 de Diciembre de 2009, Kevin Williams escribió:
>> That makes sense. I can't say I'm a big fan of Builder either
>
> Perhaps I miss something but, which is the other way to create a Rack app
> without using Builder?
>
>
> --
> Iñaki Baz Castillo <ibc@aliax.net>
>
--
stadik.net
next prev parent reply other threads:[~2009-12-05 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 2:04 Rack-compatible server issues Kevin Williams
2009-12-05 6:42 ` Matt Todd
2009-12-05 15:51 ` Kevin Williams
2009-12-05 20:49 ` Iñaki Baz Castillo
2009-12-05 22:55 ` Scytrin dai Kinthra [this message]
2009-12-05 6:43 ` Michael Fellinger
2009-12-05 16:00 ` Kevin Williams
2009-12-05 17:05 ` Kevin Williams
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=5a9d52bd0912051455u3411ed02n770f60244cb89d4f@mail.gmail.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).