Skip to content
Snippets Groups Projects
Commit bb5a6e3c authored by Chris Wilson's avatar Chris Wilson
Browse files

Update GitLab architecture diagram, include Google draw link

[ci skip]
parent fd9eb403
No related branches found
No related tags found
No related merge requests found
Loading
@@ -53,6 +53,8 @@ To serve repositories over SSH there's an add-on application called gitlab-shell
Loading
@@ -53,6 +53,8 @@ To serve repositories over SSH there's an add-on application called gitlab-shell
### Components ### Components
   
![GitLab Diagram Overview](gitlab_architecture_diagram.png) ![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 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.
   
Loading
Loading
doc/development/gitlab_architecture_diagram.png

274 KiB | W: | H:

doc/development/gitlab_architecture_diagram.png

45.8 KiB | W: | H:

doc/development/gitlab_architecture_diagram.png
doc/development/gitlab_architecture_diagram.png
doc/development/gitlab_architecture_diagram.png
doc/development/gitlab_architecture_diagram.png
  • 2-up
  • Swipe
  • Onion skin
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment