| Age | Commit message (Collapse) | Author |
|---|
|
A default usage of `make` does compile binaries
in `_build/bin`. To make a `config.toml.example`
be easy to use in a default setting this aligns
`bin_dir` with this change.
If a `make install` is done, a default `DESTDIR=/usr/local/bin`
a `bin_dir` needs to be aligned as well.
|
|
Now that we're moving git configuration into Gitaly, we are starting to
discourage users to use the global git configuration to configure git.
We must provide a way to inject configuration though to allow customers
to inject custom configuration in special situations.
This commit thus adds new git configuration which allows users to inject
custom git config pairs.
|
|
When the zero value for the maintenance window is provided, Gitaly will
use a default maintenance window that runs on all configured storages at
+1200 GMT for 10 minutes. This way, all GitLab instances can enjoy
optimized repositories. This feature can be overriden by setting
"Disabled = true" in the toml config.
|
|
Related to https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11648
|
|
Fix Git hooks when GitLab relative URL path and UNIX socket in use
See merge request gitlab-org/gitaly!2485
|
|
This moves the integration of the walker and scheduler to the server
factory called by the bootstrap process. This is higher up in the call
stack than the original location.
This also changes the walker to use the client to call the repository
service via internal socket.
|
|
Previously if GitLab were configured to use a relative URL
(e.g. `/gitlab`) and the Gitaly `gitlab.url` configuration used the
http+unix:// scheme, the hooks would not be able to contact the API
server. We add an explicit `relative_url_root` parameter to make it
possible for all connections to go through Workhorse.
This commit depends on changes in
https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/406.
NOTE: This only fixes the Git hooks that are implemented in Go. The Ruby
gitlab-shell hooks don't appear to have ever work with GitLab
installations using a relative URL when a UNIX domain socket is
used. Omnibus installations bypass Workhorse and talk directly to the
Web server.
Relates to https://gitlab.com/gitlab-org/gitlab-shell/-/issues/476
|
|
In order to implement proper support of TLS connections
for the praefect we require some refactoring of the existing
codebase.
Mainly it is about moving the things into other places and
fixing `config.Config` global var usage where is it accessible
as parameter.
Part of: https://gitlab.com/gitlab-org/gitaly/-/issues/1698
|
|
https://gitlab.com/gitlab-org/gitaly/-/commit/87b8dde88db42036d6c03b5537e7ee9b720c1aa5
|
|
Reasoning:
https://gitlab.com/gitlab-org/gitlab-workhorse/-/blob/master/README.md#quick-facts-how-does-workhorse-work
https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/388#note_351164003
|
|
The unicorn replacement 'puma' uses a unix socket in the example config [1] instead of a tcp port.
Using the non-existing tcp port results in "Internal API unreachable" on
git operations.
[1] https://gitlab.com/gitlab-org/gitlab/-/blob/master/config/puma.rb.example#L34
|
|
This reverts commit 51d96bd920b4f07e87e84fd79c72a9b3c2f9902e.
|
|
This reverts commit 5a24d9619e2472d70a9ca4fc8d6d5ec7a9fdbffa, reversing
changes made to 4cd8d0c5614cafc3ca41f3473004adaeabc77e24.
|
|
|
|
|
|
This reverts commit 5a7280c223690cfff32a47f46930af57aa467c09, reversing
changes made to 61dbe2ea087ebe4b5957972c7fb9e55eea1da7c5.
|
|
This reverts commit ee267f173b9ce8db2aaf07491f650bf74894ba31, reversing
changes made to 645cf75dfd53e933f26469c25799a59c2a6db564.
|
|
|
|
In case the `/tmp` directory can't be used for security reasons, this
can be configured. The default behaviour as in production right now will
remain. So if nothing is set, `/tmp` will be reused.
|
|
|
|
This commit adds an optional `git_config_search_path` parameter for
gitaly-ruby.
By default, Rugged searches inside `/etc/gitconfig` instead of
`/opt/gitlab/embedded/etc/gitconfig` for system-wide options unless the
`Rugged::Settings['search_path_system']` is set.
This means that important options such as `core.fsyncObjectFiles` are
not propagated to gitaly-ruby, which can result in data loss after
servers are rebooted.
The command-line `git` doesn't have this issue because it uses the
`prefix` compile-time option, but this isn't available in Rugged.
With this new parameter, package managers (e.g. Omnibus) can specify
where the system `gitconfig` file should be.
Closes https://gitlab.com/gitlab-org/gitaly/issues/2051
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Log level cannot be set for Gitaly, which makes it very verbose in
production. This is not a problem, but in a development environment it
might be. Especially when other applications log to STDOUT too, details
get lost.
Closes https://gitlab.com/gitlab-org/gitaly/issues/1156
|
|
|
|
Closes #988
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Conflicts:
# CHANGELOG.md
# cmd/gitaly/main.go
# config.toml.example
|
|
|
|
|
|
|
|
|
|
|
|
|
