Domain sockets are the default, not TCP

Jacob Vosmaer
1 parent e009e020
Showing 1 changed file with 1 additions and 1 deletions Show diff stats
doc/development/architecture.md
@@ -32,7 +32,7 @@ To serve repositories over SSH there&#39;s an add-on application called gitlab-shell
 A typical install of GitLab will be on Ubuntu Linux or RHEL/CentOS.
 It uses Nginx or Apache as a web front end to proxypass the Unicorn web server.
-Communication between Unicorn and the front end is usually HTTP but access via socket is also supported.
+By default, communication between Unicorn and the front end is via a Unix domain socket but forwarding requests via TCP is also supported.
 The web front end accesses `/home/git/gitlab/public` bypassing the Unicorn server to serve static pages, uploads (e.g. avatar images or attachments), and precompiled assets.
 GitLab serves web pages and a [GitLab API](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/api) using the Unicorn web server.
 It uses Sidekiq as a job queue which, in turn, uses redis as a non-persistent database backend for job information, meta data, and incomming jobs.
	@@ -32,7 +32,7 @@ To serve repositories over SSH there's an add-on application called gitlab-shell		@@ -32,7 +32,7 @@ To serve repositories over SSH there's an add-on application called gitlab-shell
32		32
33	A typical install of GitLab will be on Ubuntu Linux or RHEL/CentOS.	33	A typical install of GitLab will be on Ubuntu Linux or RHEL/CentOS.
34	It uses Nginx or Apache as a web front end to proxypass the Unicorn web server.	34	It uses Nginx or Apache as a web front end to proxypass the Unicorn web server.
35	-Communication between Unicorn and the front end is usually HTTP but access via socket is also supported.	35	+By default, communication between Unicorn and the front end is via a Unix domain socket but forwarding requests via TCP is also supported.
36	The web front end accesses `/home/git/gitlab/public` bypassing the Unicorn server to serve static pages, uploads (e.g. avatar images or attachments), and precompiled assets.	36	The web front end accesses `/home/git/gitlab/public` bypassing the Unicorn server to serve static pages, uploads (e.g. avatar images or attachments), and precompiled assets.
37	GitLab serves web pages and a [GitLab API](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/api) using the Unicorn web server.	37	GitLab serves web pages and a [GitLab API](https://gitlab.com/gitlab-org/gitlab-ce/tree/master/doc/api) using the Unicorn web server.
38	It uses Sidekiq as a job queue which, in turn, uses redis as a non-persistent database backend for job information, meta data, and incomming jobs.	38	It uses Sidekiq as a job queue which, in turn, uses redis as a non-persistent database backend for job information, meta data, and incomming jobs.