Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-workhorse
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-workhorse
Commits
ee087818
Commit
ee087818
authored
Nov 02, 2016
by
Jacob Vosmaer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add "quick facts" section
parent
377df647
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
21 additions
and
0 deletions
+21
-0
README.md
README.md
+21
-0
No files found.
README.md
View file @
ee087818
...
...
@@ -4,6 +4,27 @@ Gitlab-workhorse is a smart reverse proxy for GitLab. It handles
"large" HTTP requests such as file downloads, file uploads, Git
push/pull and Git archive downloads.
## Quick facts (how does Workhorse work)
-
Workhorse can handle some requests without involving Rails at all:
for example, Javascript files and CSS files are served straight
from disk.
-
Workhorse can modify responses sent by Rails: for example if you use
`send_file`
in Rails then gitlab-workhorse will open the file on
disk and send its contents as the response body to the client.
-
Workhorse can take over requests after asking permission from Rails.
Example: handling
`git clone`
.
-
Workhorse can modify requests before passing them to Rails. Example:
when handling a Git LFS upload Workhorse first asks permission from
Rails, then it stores the request body in a tempfile, then it sends
a modified request containing the tempfile path to Rails.
-
Workhorse does not connect to Redis or Postgres, only to Rails.
-
We assume that all requests that reach Workhorse pass through an
upstream proxy such as NGINX or Apache first.
-
Workhorse does not accept HTTPS connections.
-
Workhorse does not clean up idle client connections.
-
We assume that all requests to Rails pass through Workhorse.
For more information see
[
'A brief history of
gitlab-workhorse'
][
brief-history-blog
]
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment