b6d343bf09
When SCM-Manager is used behind a reverse proxy like Nginx it may be the case, that lfs PUT requests are buffered by the reverse proxy and will be sent to the SCM-Manager after the whole file has been received. Due to the expiration time of 5 minutes for the authentivation token that had been requested by Git before the upload has been started, this request from the proxy to SCM-Manager fails if the upload from the client to the reverse proxy took longer than these 5 minutes. To solve this, we make this expiration time configurable, so that whenever you have very large files or small bandwidth the expiration timeout can be increased.
1.2 KiB
title, subtitle
| title | subtitle |
|---|---|
| Administration | Git |
In the git section there are the following git specific settings:
-
GC Cron Expression
If this is set, SCM-Manager will execute a git garbage collection matching the given cron expression.
-
Disable Non Fast-Forward
Activate this to reject forced pushes that are not fast forwards.
-
Default Branch
The branch name configured here will be used for the initialization of new repositories. Please mind, that due to git internals this cannot work for empty repositories (here git will always use its internal default branch, so at the time being
master). -
LFS authorization expiration
Sets the expiration time of the authorization token generated for LFS put requests in minutes. If SCM-Manager is run behind a reverse proxy that buffers http requests (eg. Nginx), this should set up to the time, an LFS upload may take at maximum. If you experience errors during long-running LFS push requests, this may have to be increased. The default value is 5 minutes.
