rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: James Tucker <jftucker@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Allow network access to Sinatra server running on Rack?
Date: Mon, 07 Sep 2015 15:50:21 +0000	[thread overview]
Message-ID: <CABGa_T_bysx9M_ge5oBz8c0292gMUzJ93b0uoqXcfBdAY8oqbw@mail.gmail.com> (raw)
In-Reply-To: <f73abc6b-a578-4ff0-84d5-13e3e23cadb7@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 3010 bytes --]

Those are really server options. Rackup isn't really a framework. People
often want to extend it for this purpose, but isnt designed in that way
really.

What you could do would be to write your own binary, using rack::server and
then grab options from there, but in that case you'd really be better off
implementing options yourself so that you have more control and aren't
reliant on APIs that no one really uses (and thus may be subject to change).

Racks server infrastructure has always been designed to be used
programmatically for this reason.

On Thu, Sep 3, 2015, 1:15 PM  <jtindall@soasta.com> wrote:

> Aha - it was just a matter of setting the host to 0.0.0.0 in the command
> options like so :$ rackup --server thin --host 0.0.0.0 --port 4567
>
> Still no idea how to access the options though :(
>
>
> On Thursday, September 3, 2015 at 5:11:42 PM UTC+1, jtin...@soasta.com
> wrote:
>>
>> Hi Steve,
>>
>> Thanks. I am passing in the port setting when starting rack from the
>> command line like so :$ rackup --server thin --host localhost --port 4567
>>
>> I also pass in options via the --options flag but can't seem to find any
>> documentation on how to access these options anywhere!
>>
>> James
>>
>> On Thursday, September 3, 2015 at 2:09:35 PM UTC+1, Steve Fazekas wrote:
>>>
>>> James,
>>>
>>> I think I have that config set up for my  own use and when I get into
>>> work later I'll send you what I have this afternoon.  If you think
>>> everything is set correctly try setting a different port.
>>>
>>> Steve Fazekas
>>> sfaz...@act1.net act...@hotmail.com
>>> 614.989.9764
>>>
>>> On Sep 2, 2015, at 1:07 PM, jtin...@soasta.com wrote:
>>>
>>> Hi all,
>>>
>>> Sinatra supports access over the network by setting the bind setting to
>>> '0.0.0.0' - I can't seem to find any docs on how this is achieved when
>>> running Sinatra via Rack::Cascade. Anyone have any Ideas??
>>>
>>> Also, finding it hard to find docs on how to pass Rackup --options into
>>> the Sinatra app running in Rack::Cascade.
>>>
>>> Thanks - any help much appreciated!
>>>
>>> James
>>>
>>>
>>> --
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Rack Development" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to rack-devel+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Rack Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rack-devel+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 4498 bytes --]

      reply	other threads:[~2015-09-07 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 17:07 Allow network access to Sinatra server running on Rack? jtindall
2015-09-03 12:40 ` Steve Fazekas
2015-09-03 16:11   ` jtindall
2015-09-03 16:15     ` jtindall
2015-09-07 15:50       ` James Tucker [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-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=CABGa_T_bysx9M_ge5oBz8c0292gMUzJ93b0uoqXcfBdAY8oqbw@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).