summaryrefslogtreecommitdiff
path: root/doc/development/architecture.md
diff options
context:
space:
mode:
authorFabio Papa <fabtheman@gmail.com>2019-07-12 10:37:24 -0700
committerFabio Papa <fabtheman@gmail.com>2019-07-12 10:37:24 -0700
commit6c51aadf35c4e7899da99c85c3fc4c01484819f2 (patch)
treec683e3d7ebcf3e188f1dd85b8701ff972e7f8a3d /doc/development/architecture.md
parent9b176c65159e4186f79eae2107af80e69132ba09 (diff)
parent6457d5edb7d66df5dd3d5ba1f1ea0c56a59287a8 (diff)
downloadgitlab-ce-6c51aadf35c4e7899da99c85c3fc4c01484819f2.tar.gz
Merge branch 'maintainers-can-create-subgroup' of https://gitlab.com/fapapa/gitlab-ce into maintainers-can-create-subgroup
Diffstat (limited to 'doc/development/architecture.md')
-rw-r--r--doc/development/architecture.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/development/architecture.md b/doc/development/architecture.md
index 8319603fea2..b645a72567c 100644
--- a/doc/development/architecture.md
+++ b/doc/development/architecture.md
@@ -484,9 +484,11 @@ When making a request to an HTTP Endpoint (think `/users/sign_in`) the request w
Below we describe the different pathing that HTTP vs. SSH Git requests will take. There is some overlap with the Web Request Cycle but also some differences.
### Web Request (80/443)
+
TODO
### SSH Request (22)
+
TODO
## System Layout
@@ -505,7 +507,9 @@ To summarize here's the [directory structure of the `git` user home directory](.
### Processes
- ps aux | grep '^git'
+```sh
+ps aux | grep '^git'
+```
GitLab has several components to operate. As a system user (i.e. any user that is not the `git` user) it requires a persistent database (MySQL/PostreSQL) and redis database. It also uses Apache httpd or Nginx to proxypass Unicorn. As the `git` user it starts Sidekiq and Unicorn (a simple ruby HTTP server running on port `8080` by default). Under the GitLab user there are normally 4 processes: `unicorn_rails master` (1 process), `unicorn_rails worker` (2 processes), `sidekiq` (1 process).