blob: a3a2b29af643c664157bf56a75d2aebc195cdbac (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
## Gitaly documentation
The historical reasons for the inception of Gitaly and our design decisions are
written in [the design doc](doc/DESIGN.md).
#### Configuring Gitaly
Running Gitaly requires it to be configured correctly, options are described in
the [configuration documentation](doc/configuration/README.md).
#### Developing Gitaly
- When new to Gitaly development, start by reading the [beginners guide](docs/beginners_guid.md).
- When developing on Gitaly-Ruby, read the [Gitaly-Ruby doc](doc/ruby_endpoint.md)
- The Gitaly release process is descripted in [our process doc](doc/PROCESS.md)
- Tests use Git repositories too, [read more about them](doc/test_repos.md)
#### Gitaly HA
Gitaly does not replicate any data. If a Gitaly server goes down, any of its
clients can't read or write to the repositories stored on that server. This
means that Gitaly is not highly available. How this will be solved is described
[in the HA design document](doc/design_ha.md)
For configuration please read [praefects configuration documentation](doc/configuration/praefect.md).
#### Technical explanations
- [Delta Islands](doc/delta_islands.md)
|