summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJacob Vosmaer <contact@jacobvosmaer.nl>2014-02-10 14:01:15 +0100
committerJacob Vosmaer <contact@jacobvosmaer.nl>2014-02-10 14:01:15 +0100
commit464d820bc59ed4bf26884f1be45463c02d79544e (patch)
treebe88e0397407e7baae91cceb5de9aae461c476ca
parente009e0203e78f6d648b3a3d3a230b9c977dc5141 (diff)
downloadgitlab-ce-464d820bc59ed4bf26884f1be45463c02d79544e.tar.gz
Domain sockets are the default, not TCP
-rw-r--r--doc/development/architecture.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/architecture.md b/doc/development/architecture.md
index a61bb13e34f..8a772344b79 100644
--- a/doc/development/architecture.md
+++ b/doc/development/architecture.md
@@ -32,7 +32,7 @@ To serve repositories over SSH there'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.