Created
January 18, 2016 23:05
-
-
Save xet7/694ec71ca08527485483 to your computer and use it in GitHub Desktop.
GitLab nginx config
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# This file is managed by gitlab-ctl. Manual changes will be | |
# erased! To change the contents below, edit /etc/gitlab/gitlab.rb | |
# and run `sudo gitlab-ctl reconfigure`. | |
## GitLab | |
## Modified from https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/support/nginx/gitlab-ssl & https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/support/nginx/gitlab | |
## | |
## Lines starting with two hashes (##) are comments with information. | |
## Lines starting with one hash (#) are configuration parameters that can be uncommented. | |
## | |
################################## | |
## CHUNKED TRANSFER ## | |
################################## | |
## | |
## It is a known issue that Git-over-HTTP requires chunked transfer encoding [0] | |
## which is not supported by Nginx < 1.3.9 [1]. As a result, pushing a large object | |
## with Git (i.e. a single large file) can lead to a 411 error. In theory you can get | |
## around this by tweaking this configuration file and either: | |
## - installing an old version of Nginx with the chunkin module [2] compiled in, or | |
## - using a newer version of Nginx. | |
## | |
## At the time of writing we do not know if either of these theoretical solutions works. | |
## As a workaround users can use Git over SSH to push large files. | |
## | |
## [0] https://git.kernel.org/cgit/git/git.git/tree/Documentation/technical/http-protocol.txt#n99 | |
## [1] https://github.com/agentzh/chunkin-nginx-module#status | |
## [2] https://github.com/agentzh/chunkin-nginx-module | |
## | |
################################### | |
## configuration ## | |
################################### | |
upstream gitlab-workhorse { | |
server unix:/var/opt/gitlab/gitlab-workhorse/socket; | |
} | |
server { | |
listen *:80; | |
server_name xet7; | |
server_tokens off; ## Don't show the nginx version number, a security best practice | |
root /opt/gitlab/embedded/service/gitlab-rails/public; | |
## Increase this if you want to upload large attachments | |
## Or if you want to accept large git objects over http | |
client_max_body_size 0; | |
## Individual nginx logs for this GitLab vhost | |
access_log /var/log/gitlab/nginx/gitlab_access.log gitlab_access; | |
error_log /var/log/gitlab/nginx/gitlab_error.log; | |
location / { | |
## If you use HTTPS make sure you disable gzip compression | |
## to be safe against BREACH attack. | |
## https://github.com/gitlabhq/gitlabhq/issues/694 | |
## Some requests take more than 30 seconds. | |
proxy_read_timeout 300; | |
proxy_connect_timeout 300; | |
proxy_redirect off; | |
proxy_http_version 1.1; | |
proxy_set_header Host $http_host; | |
proxy_set_header X-Real-IP $remote_addr; | |
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; | |
proxy_set_header X-Forwarded-Proto http; | |
proxy_pass http://gitlab-workhorse; | |
} | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment