Summary Git on the Server The Protocols Local Protocol The HTTP Protocols The SSH Protocol The Git Protocol Getting Git on a Server Putting the Bare Repository on a Server Small Setups Generating Generating Your SSH Public Key Setting Up the Server Git Daemon Smart HTTP GitWeb GitLab Installation Administration Basic Usage Working Together Third Party Hosted Options Summary Distributed Git and Whitespace Server Configuration Git Attributes Binary Files Keyword Expansion Exporting Your Repository Merge Strategies Git Hooks Installing a Hook Client-Side Hooks Server-Side Hooks An

Summary Git on the Server The Protocols Local Protocol The HTTP Protocols The SSH Protocol The Git Protocol Getting Git on a Server Putting the Bare Repository on a Server Small Setups Generating Generating Your SSH Public Key Setting Up the Server Git Daemon Smart HTTP GitWeb GitLab Installation Administration Basic Usage Working Together Third Party Hosted Options Summary Distributed Git and Whitespace Server Configuration Git Attributes Binary Files Keyword Expansion Exporting Your Repository Merge Strategies Git Hooks Installing a Hook Client-Side Hooks Server-Side Hooks An

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Git on the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Getting Git on a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Setting Up the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. 1.11.1 Accessing repositories The VCS hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 110 Chapter

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. 1.11.1 Accessing repositories The VCS hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 110 Chapter

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. 1.11.1 Accessing repositories The VCS hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 110 Chapter

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit, Subversion and Bitbucket Server pull requests) and Mercurial as version control back-ends. Accessing repositories The VCS repository hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: GitHub repositories

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 100 Chapter in the last step of the component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated

machine, you can use the repository directly. For anonymous access, you might want to run a Git server and let it serve the repository to the outside world. Alternatively, you can use Git exporter inside hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. The added keys with fingerprints are shown in the confirmation message: 100 Chapter in the last step of the component configuration. Reasons to use this: • Saves disk space on the server, the repository is stored just once. • Makes the updates faster, only one repository is updated