| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
refresh the path to performance bar in admin settings with the up-to-date value
See merge request gitlab-org/gitlab-ce!23316
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Fix typos in specs and docs
See merge request gitlab-org/gitlab-ce!23084
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Object storage docs are not relevant to GitLab.com and is in Core
See merge request gitlab-org/gitlab-ce!22943
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Fix punctuation error
See merge request gitlab-org/gitlab-ce!22345
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add docs for setting up external Prometheus
Closes #40949 and #37255
See merge request gitlab-org/gitlab-ce!22831
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | |
| | | |
This recently changed on the Gitaly side, but now spotted this in the
docs for the next release. Updated to be more precise, and to signal
users should not want control over this specific hook location.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Feature backported to CE in 11.5, not 10.7
Closes #53648
See merge request gitlab-org/gitlab-ce!22892
|
| | | | | |
|
| |/ / /
| | |
| | |
| | | |
Also corrects capitalisation of Git.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Emphasis the importance of auth registry
See merge request gitlab-org/gitlab-ce!22843
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The container registry requires the `auth` config to be set up properly
or users will be able to download images that they are not authorized to
do so.
For example https://gitlab.com/gitlab-org/gitlab-runner/issues/3652
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now the files are identical again compared to EE.
These are backported from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5050
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Delegate storage health check to Gitaly's health check
Closes gitaly#1336
See merge request gitlab-org/gitlab-ce!22063
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also, since Gitaly now takes care of checking for storage paths
existence/accessibility, we can remove those check from the
gitlab:gitlab_shell_check task and advance further into 0 direct disk
approach on gitlab-rails
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will add audit_json.log that writes one line per audit event. For
example:
{
"severity":"INFO",
"time":"2018-10-17T17:38:22.523Z",
"author_id":3,
"entity_id":2,
"entity_type":"Project",
"change":"visibility",
"from":"Private",
"to":"Public",
"author_name":"John Doe4",
"target_id":2,
"target_type":"Project",
"target_details":"namespace2/project2"
}
|
| |\ \
| | |
| | |
| | |
| | | |
repository check doc: fix a broken link
See merge request gitlab-org/gitlab-ce!22444
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The link to the repocheck.log section of the logs documentation was
added in 7d9191eeff9 ("Small documentation reformatting and updates",
2018-04-23), but seemingly never worked. The markdown formatter turns
"." into "-" in headings.
See
https://docs.gitlab.com/ee/administration/repository_checks.html#what-to-do-if-a-check-failed
which has a broken link to
https://docs.gitlab.com/ee/administration/logs.html#repocheck.log
linking to
https://docs.gitlab.com/ee/administration/logs.html#repocheck-log
instead (just change "." to "-") fixes it.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove beta status on hashed storage and reference to production readiness review.
See merge request gitlab-org/gitlab-ce!22457
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Remove broken link
See merge request gitlab-org/gitlab-ce!22284
|
| | | |
| | |
| | |
| | | |
- And minor linting fixes.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
For more info, see:
* https://gitlab.com/gitlab-org/gitaly/issues/1339
* https://gitlab.com/gitlab-org/gitlab-ce/issues/52017
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove Koding integration and documentation
Closes #39697
See merge request gitlab-org/gitlab-ce!22334
|
| | | |/
| |/|
| | |
| | |
| | |
| | | |
This integration no longer works and does not appear to be supported.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/39697
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Specification change: Fix asciidoctor block context.
See merge request gitlab-org/gitlab-ce!22280
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
docs: match where statements at in omnibus section
See merge request gitlab-org/gitlab-ce!22214
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Add Filesystem Performance Benchmarking documentation
See merge request gitlab-org/gitlab-ce!22202
|
| | |/
| |
| |
| |
| |
| |
| | |
Filesystem performance can have a big impact on overall GitLab
performance, especially for actions that read or write Git
repositories. This information will help benchmark filesystem
performance against known good and bad real-world systems.
|
