unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
* Question about shared directory
@ 2019-08-06  8:52 Patryk Kotarski
  2019-08-06 14:00 ` Eric Wong
  0 siblings, 1 reply; 2+ messages in thread
From: Patryk Kotarski @ 2019-08-06  8:52 UTC (permalink / raw)
  To: unicorn-public

Hello, dear unicorn devs,

Quick question which I failed to find in previous issues on your archive and through search engines.

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

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/

Greetings,
Patryk

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Question about shared directory
  2019-08-06  8:52 Question about shared directory Patryk Kotarski
@ 2019-08-06 14:00 ` Eric Wong
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2019-08-06 14:00 UTC (permalink / raw)
  To: Patryk Kotarski; +Cc: unicorn-public

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:
https://public-inbox.org/git/alpine.LFD.1.10.0806161723081.2949@woody.linux-foundation.org/

> 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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-08-06 14:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-06  8:52 Question about shared directory Patryk Kotarski
2019-08-06 14:00 ` Eric Wong

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