2016-06-23 02:15:51 +00:00 · 2016-06-23 02:15:51 +00:00 · bb5a6e3c51
parent fd9eb4036c
commit bb5a6e3c51
2 changed files with 2 additions and 0 deletions
--- a/doc/development/architecture.md
+++ b/doc/development/architecture.md
@ -53,6 +53,8 @@ To serve repositories over SSH there's an add-on application called gitlab-shell
 ### Components

 ![GitLab Diagram Overview](gitlab_architecture_diagram.png)
+ 
+_[edit diagram](https://docs.google.com/drawings/d/1fBzAyklyveF-i-2q-OHUIqDkYfjjxC4mq5shwKSZHLs/edit)_

 A typical install of GitLab will be on GNU/Linux. It uses Nginx or Apache as a web front end to proxypass the Unicorn web server. 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 incoming jobs.

--- a/doc/development/gitlab_architecture_diagram.png
+++ b/doc/development/gitlab_architecture_diagram.png