GitLab Configuration for Local Users
I just finished installing GitLab and I think the interface is great. I have a few questions for configuring it though.
Previously this server used the most basic ssh management for git. In other words, users would log in using ssh and check out code from a directory like
ssh://user@server:/Git/repo.git, Users would need to belong to the Linux group “
gitusers” for this to work.
- Git add: Why do I have to manually specify which files to commit?
- How do I edit a Git commit that is hundreds of merges and merge conflicts into the past?
- Initial commit of major projects to mercurial
- Git workflow idea to push an unfinished local branch to remote for backup purposes
- Is there a way to get the git root directory in one command?
- Problem cloning gitolite on Windows
Instead of creating users through the gitlab interface, I would like to allow anyone who belongs to the gitusers group to be able to log in using their linux account credentials and see their repositories, is this possible?
I would like SSH clones to work in a similar way. Right now, the ssh link that is listed on a repository on gitlab says to use
ssh://git@server:user/repo.gitI would like that to be user@server. It is fine if the directory itself is something that GitLab manages.
Is there a way to expose a
git://style link from gitlab?
In other words, instead of changing the work flow to match gitlab, I would like to use the GitLab GUI on top of our existing workflow. Any tips for how to change configurations to solve these two issues would be a huge help
One Solution collect form web for “GitLab Configuration for Local Users”
GitLab needs to be able to have the user defined in its user database in order to associate him/her to the repos. The authentication is a different matter and can be delegated to an LDAP, an apache server, or many other mechanisms.
ssh will always use git as a user: the all idea is for the user to never directly access the remote server shell. The public key of the user registered in their GitLab account will be enough to authenticate them.
git://protocol doesn’t support authentication, which means GitLab wouldn’t be able to process any