unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Best way to deploy an internal Rack app?
Date: Thu, 21 Nov 2013 17:22:44 +0000	[thread overview]
Message-ID: <20131121172244.GA20007@dcvr.yhbt.net> (raw)
In-Reply-To: <D604FB44-E1D1-4BEB-B732-249D105621BC@airbladesoftware.com>

Andrew Stewart <boss@airbladesoftware.com> wrote:
> Hello!
> 
> I have a Rails monolith and have identified a few parts which can be
> chipped off and deployed as self-contained services, called by the
> monolith.
> 
> Each service will be a rack app presenting an API over HTTP.  For now
> everything will run on the same box.  The services shouldn't be
> exposed to the outside world.

> I have almost built the first service and am now wondering how best to serve it.  For example:
> 
> - Does Unicorn alone suffice or should I front it with Nginx?

This depends on how you want clients to connect.  Either the unicorns
need to listen on different addresses/ports, or you can set up nginx to
handle routing so clients only connect to nginx.

> - To keep the services internal do I just listen to a port on the
> loopback interface?

Any address:port (127.0.0.1:1234, 127.0.0.2:1234, ...), or unix socket.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

      reply	other threads:[~2013-11-21 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 10:58 Best way to deploy an internal Rack app? Andrew Stewart
2013-11-21 17:22 ` Eric Wong [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

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131121172244.GA20007@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

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).