| Age | Commit message (Collapse) | Author |
|---|
|
When interacting with Git repositories the Gitaly team contains a lot of
knowledge, but it's not written down. This makes it harder for
maintainers to spread their knowlegde, and would ease reviews if
contributors can learn what to do and not to do.
This would also allow maintainers to link to the docs during reviews
without explaining the full story, and speed them up.
|
|
|
|
|
|
|
|
|
|
|
|
Being under the impression that the gitaly-ssh docs still needed to be
written, I set out to do so. Luckily while I was reading the source I
saw the doc existed as a readme file.
The index now links to a document outside of the docs directory, though
I expect our users to be able to handle that.
|
|
|
|
|
|
|
|
|
|
Snapshot storage for repositories
See merge request gitlab-org/gitaly!1279
|
|
|
|
|
|
To prevent only a few people to have the understanding of Gitaly, the
feature is explained on a technical level. Thus it lives in the Gitaly
repository as these are features that end users don't have an interface
to other than their usual interface, `git fetch` or `git clone`.
|
|
When investigating the integration of praefect in the GDK and Omnibus it
seemed that using sockets is much more convenient. From a configuration
perspective the behaviour of Gitaly is largely copied.
Closes: https://gitlab.com/gitlab-org/gitaly/issues/1523
|
|
If one wanted to read all the documentation in the Gitaly repository the
best way to do so was opening the doc directory. Structure was missing.
This commit updates the documentation and adds an index page.
|
