The githost.log name was often confused with GitHost.io. Rename this to
git_json.log to make it clear it's coming from Git and that it's JSON
data.

As decided in https://gitlab.com/gitlab-org/gitlab-ce/issues/53593

Nick Thomas authored 5 years ago and Douwe Maan committed 5 years ago

We're removing the ability for MRs in a single project to block each
other, and performing a rename of the feature to go along with that.
This necessitates documentation changes

Reuben Pereira authored 5 years ago and Achilleas Pipinellis committed 5 years ago

- Add documentation under security/webhooks since similar docs are
present there.

- Original EE MR: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14827

No reason to keep them separate.

Marcel Amirault authored 5 years ago and Evan Read committed 5 years ago

Move the api resources section from the api readme
to it's own file, and adjust/link accordingly

Expose time since starring on project/:id/starrers API endpoint; exclude private profiles here as well

Fix API endpoint for starred projects of a user; add info about starred projects on profile to documentation

Jason Goodman authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Add updated screen shots

Part of: https://gitlab.com/gitlab-org/gitaly/issues/1715

Marcel Amirault authored 5 years ago and Evan Read committed 5 years ago

Fix links as discovered by the lint in the docs project

Tiger Watson authored 5 years ago and Thong Kuah committed 5 years ago

Kubernetes deployments on new clusters will now have
a separate namespace per project environment, instead
of sharing a single namespace for the project.

Behaviour of existing clusters is unchanged.

All new functionality is controlled by the
:kubernetes_namespace_per_environment feature flag,
which is safe to enable/disable at any time.

These were disabled in production mode, but that also broke the rest of
the performance bar. As they were only enabled in development mode, we
can just remove them for now.

Merge Requests Approvals can be restricted to prevent the merge
request author or merge request committers from self approving. The
author restriction is already available in the API, but the committer
restriction was not.

Red Hat finally fixed the NFS server delegation problem that caused the
TEST_STATEID flood. Mention the docs that disabling delegation may
no longer be needed.

Docker 19.03 enables TLS by default:

```
Starting in 18.09+, the dind variants of this image will automatically
generate TLS certificates in the directory specified by the
DOCKER_TLS_CERTDIR environment variable.

Warning: in 18.09, this behavior is disabled by default (for
compatibility). If you use --network=host, shared network namespaces (as
in Kubernetes pods), or otherwise have network access to the container
(including containers started within the dind instance via their gateway
interface), this is a potential security issue (which can lead to access
to the host system, for example). It is recommended to enable TLS by
setting the variable to an appropriate value (-e
DOCKER_TLS_CERTDIR=/certs or similar). In 19.03+, this behavior is
enabled by default.
```

Update the example to use docker over TLS.

This reverts commit d754beb74fbc06a2c744e15be4aa2831d8cef1c0.

Matt Penna authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Reviewed all docs in the customization section
and updated them to adhere to our SSoT standards.

Jason Colyer authored 5 years ago and Evan Read committed 5 years ago

* Added elasticsearch.md
* Added reference to guide in Troubleshooting section