Gitolite windows

Unless the documentation says "do this from root ", assume it is to be done from the hosting user account. This page is about an ssh mode installation. It should work for most people, but if you are an absolute newbie to Unix etc. If ssh is not your thing, there's a different page for http mode installation. Please DO read the concepts and terminology page before doing anything here. If you're installing gitolite, you're a "system admin", like it or not.

Since most people use the ssh mode, ssh is therefore a necessary skill. Please take the time to learn at least enough to get passwordless access working.

You also need to be somewhat familiar with git itself. You cannot administer a whole bunch of git repositories if you don't know the basics of git. Please make sure you understand at least the following concepts: bare versus non-bare repos, cloning a repo, making changes and committing them, pushing commits to a 'remote', the special remote called 'origin', difference between a fast-forward push and a rewind push, 'refs' i.

Regular expressions are a big part of gitolite in many places but familiarity is not necessary to do basic access control. A dedicated Unix userid to be the hosting user, usually "git" but it can be any user, even your own normal one. If you're bringing existing repos into gitolite, please see this first. Gitolite does NOT like it if you fiddle with files and directories it cares about in any way except as directed in the documentation.

Gitolite depends on several system-installed packages: openssh, git, perl, sh being the main ones. They should all be configured sensibly and with most of the normal defaults. For example, if your sshd config says the authorized keys file should be placed in some directory other than the default, expect trouble.

If you're not sure if gitolite is right for you or your system, it's easy to take it for a trial run, in ssh mode, and play with all of its features except mirroring. This is very safe, and does not affect anything on your system permanently.

Ideally, you should use a throwaway userid. This is intentional; I've had people who don't pay attention to the "data loss" warning, and then complain that it was not prominent enough. Forcing them to read a much smaller page appears to focus their attention better! When gitolite is told to create a new repository by the admin , it installs a special update hook.

This hook takes all the information presented, looks at the config file, and decides to allow or reject the update. From here you can search these documents. Enter your search terms below. Search Previous Next. Therefore, gitolite is usually heavily dependent on ssh. Hopefully by the time you finish reading this page you will understand why :- The way you set this up is you generate a key pair on your workstation, and give the server the public key.

On Windows machines with msysgit installed, you should do this from within a "git bash" window. The command will report the full path where the files have been written; make a note of this, and use those files in any of the description that follows. How does it restrict what I can do within a repository. And that's basically it. Keys Action? In addition, kernel. The Mageia Project is using gitolite 3 to manage its git repositories and access control.

The repositories are defined in yaml files. A tool called mgagit has been created and is repsonsible for the generation of the gitolite configuration from the yaml repos definitions, and the extraction of users' ssh keys from an ldap directory into the gitolite configuration.

Gitolite and mgagit are installed using rpm packages and a puppet module. A general note: if you see the list of high-profile users above, you will see that gitolite benefits as much as they do; possibly more. From here you can search these documents. Enter your search terms below. Search Previous Next. Here are the features that most people see: Use a single unix user "real" user on the server. Provide access to many gitolite users: they are not "real" users, so they do not get shell access.

Can be installed without root access, assuming git and perl are already installed. Authentication is most commonly done using sshd, but you can also use "smart http" mode if you prefer this may require root access for the initial setup. However, gitolite does this much better, and offers many more features. Convenience features for writing the rules repo groups, user groups, get user group info from LDAP, include files, macros Highly customisable and scriptable, especially custom commands for users.

Many built-in commands and options. Powerful and flexible mirroring system. Users can create their own repos and set access rights if you allow them. Here are some other disadvantages of the Unix ACL method: Every user needs a userid and password on the server. Changing access rights involves complex usermod -G Auditing historical permissions or permission changes is impossible.

Gitolite uses a plain text config file; gerrit uses a database. A more detailed explanation, with figures, is here. Keys Action?