3 ms·
Try not running it on ubuntu, or in a location that doesn't allow sudo to be setup to allow any command in quite the same way as the install docs assume. I've
by mitchty 13y ago
Try not running it on ubuntu, or in a location that doesn't allow sudo to be setup to allow any command in quite the same way as the install docs assume.
I've a forked version of their startup script that doesn't use sudo for the init script (honestly wtf why is this so common redis does the same). sudo the init script don't sudo in init scripts. Meh, its not too bad I'm at the point of 15 minutes to upgrade between releases so its not too bad but yeah it isn't a trivial install.
- sytse 13y agoGood to hear you managed to install without sudo. Does this mean you didn't create the git user? How did you solve the git@ urls for git over ssh connections? Did you use the init.d scripts?
- mitchty 13y agoNope, git user is created, but I just use su to do things as git. If you're running as root using sudo doesn't make sense, thats what su is for. https://gist.github.com/mitchty/6b9bc8c7dd41cd925b82#file-gitlab-sh-L42 https://gist.github.com/mitchty/6b9bc8c7dd41cd925b82#file-gi... Thats basically it, nothing overly special, just switched sudo for su mainly. I could test to see if i'm root and then su or then sudo but don't see a point.
- sytse 13y agoI agree. In the installation manual most commands are 'sudo -u git', they run as the git user but they use sudo to make them foolproof (some people skip the instruction to login as the git user).