Commit 7ad70a56 authored by dosire's avatar dosire

Git over ssh and http are different things.

parent 119c782e
...@@ -203,8 +203,8 @@ production: &base ...@@ -203,8 +203,8 @@ production: &base
git: git:
bin_path: /usr/bin/git bin_path: /usr/bin/git
# Max size of a git object (e.g. a commit), in bytes # Max size of a git object (e.g. a commit), in bytes
# This value can be increased if you have very large commits # This value can be increased if you have very large commits with git over ssh
# Please also change the limit for your webserver (for Nginx see lib/support/nginx/gitlab) # Git over http is limited by your webserver (for Nginx see lib/support/nginx/gitlab)
max_size: 5242880 # 5.megabytes max_size: 5242880 # 5.megabytes
# Git timeout to read a commit, in seconds # Git timeout to read a commit, in seconds
timeout: 10 timeout: 10
......
...@@ -12,8 +12,8 @@ server { ...@@ -12,8 +12,8 @@ server {
server_tokens off; # don't show the version number, a security best practice server_tokens off; # don't show the version number, a security best practice
root /home/git/gitlab/public; root /home/git/gitlab/public;
# Set value of client_max_body_size to at least the value of git.max_size in gitlab.yml # Increase this if you want to upload large attachments
# Also increase this if you want to upload large attachments # Or if you want to accept large git objects over http
client_max_body_size 5m; client_max_body_size 5m;
# individual nginx logs for this gitlab vhost # individual nginx logs for this gitlab vhost
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment