From 423fe751e3193857a68d3ada17de520289e48dfc Mon Sep 17 00:00:00 2001 From: Pedro Alvarez Date: Tue, 2 Jan 2018 12:12:31 +0000 Subject: README.md: Improve a bit markdown for Gitlab --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 8349d987..a93908a5 100644 --- a/README.md +++ b/README.md @@ -551,7 +551,7 @@ we use the [autoscaling feature] of GitLab Runner to spawn new VMs for building in. The configuration for this is in `/etc/gitlab-runner/config.toml`. Each build occurs in a Docker container on one of the transient VMs. As per -the [\[runners.docker\] section] of `config.toml`, each gets a newly created +the ['runners.docker' section] of `config.toml`, each gets a newly created volume mounted at `/cache`. The YBD and BuildStream cache directories get located here because jobs were running out of disk space when using the default configuration. @@ -569,5 +569,5 @@ The Minio cache is used for the [distributed caching] feature of GitLab CI. [docker-machine]: https://docs.docker.com/machine/ [autoscaling feature]: https://docs.gitlab.com/runner/configuration/autoscale.html [Minio]: https://www.minio.io/ -[\[runners.docker\] section]: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-docker-section +['runners.docker' section]: https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runners-docker-section [distributed caching]: https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching -- cgit v1.2.1