unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Patryk Kotarski <patryk.kotarski@iubenda.com>
Cc: unicorn-public@bogomips.org
Subject: Re: Question about shared directory
Date: Tue, 6 Aug 2019 14:00:59 +0000
Message-ID: <20190806140059.GA12924@dcvr> (raw)
In-Reply-To: <A9FCC000-428C-4F55-BB60-C6C8C955F8B9@iubenda.com>

Patryk Kotarski <patryk.kotarski@iubenda.com> wrote:
> Hello, dear unicorn devs,
> Quick question which I failed to find in previous issues on
> your archive and through search engines.

Thanks for checking, first :>

> Is there any specific reason for which many guides online
> suggest saving the “unicorn.sock” file into the
> shared_directory ? We’re running deploys through Capistrano
> and on recent updates we noticed that we had configured
> unicorn.sock to be stored in
> "[environment]/shared/sockets/unicorn.sock" and we do not
> understand the reason for it

I don't know, either, and I'm not sure if anybody here wrote
those guides.  It really doesn't matter a whole lot.

I do prefer shorter pathnames with fewer path components, though;
it lets the kernel do fewer dcache lookups to get to the socket.
Not sure how much for nginx in your case, but relative vs absolute
pathnames certainly mattered for git back in the day:

> Examples:
> - https://www.digitalocean.com/community/tutorials/how-to-deploy-a-rails-app-with-unicorn-and-nginx-on-ubuntu-14-04
> - https://www.linode.com/docs/development/ror/use-unicorn-and-nginx-on-ubuntu-14-04/

      reply	other threads:[~2019-08-06 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  8:52 Patryk Kotarski
2019-08-06 14:00 ` 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:

  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=20190806140059.GA12924@dcvr \
    --to=e@80x24.org \
    --cc=patryk.kotarski@iubenda.com \
    --cc=unicorn-public@bogomips.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://yhbt.net/unicorn-public
	git clone --mirror http://ou63pmih66umazou.onion/unicorn-public

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 unicorn-public unicorn-public/ https://yhbt.net/unicorn-public \
		unicorn-public@yhbt.net unicorn-public@bogomips.org mongrel-unicorn@rubyforge.org mongrel-unicorn-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
	public-inbox-index unicorn-public

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for the project(s) associated with this inbox:


AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git