Bad gateway when not precising umask
Hi,
I have setup a gitlab v8.7.0-rc1
backed by a the version v0.7.1
of gitlab workhorse.
Since, I ran all service on a single machine, I want to use unix soxcket connection.
I am using
/home/git/workhorse/gitlab-workhorse -listenNetwork unix -listenAddr /home/git/gitlab
tmp/sockets/workhorse.socket -authSocket /home/git/gitlab/tmp/sockets/gitlab.socket -documentRoot /home/git/gitlab/public
to launch gitlab workhorse.
However, I have a 502 on each page of gitlab.
I need to launch gitlab workhorse with umask override to have a working gitlab
/home/git/workhorse/gitlab-workhorse -listenUmask 0 -listenNetwork unix -listenAddr /home/git/gitlab/tmp/sockets/workhorse.socket -authSocket /home/git/gitlab/tmp/sockets/gitlab.socket -documentRoot /home/git/gitlab/public
Could it be written on the doc please ?