Commit f778df3a authored by Marcel Amirault's avatar Marcel Amirault
Browse files

Merge branch 'eread/use-latest-docs-linting-image' into 'master'

Use latest docs linting image

See merge request gitlab-org/omnibus-gitlab!4662
parents af4b58d9 425b6edb
......@@ -25,7 +25,7 @@ For installation details, see [Installing Omnibus GitLab](installation/index.md)
 
## Running on a low-resource device (like a Raspberry Pi)
 
You can run GitLab on supported low-resource computers like the Raspberry Pi 3, but you will need to tune the settings
You can run GitLab on supported low-resource computers like the Raspberry Pi 3, but you must tune the settings
to work best with the available resources. Check out the [documentation](settings/rpi.md) for suggestions on what to adjust.
 
## Maintenance
......@@ -34,7 +34,7 @@ to work best with the available resources. Check out the [documentation](setting
- [Starting and stopping](maintenance/README.md#starting-and-stopping)
- [Invoking Rake tasks](maintenance/README.md#invoking-rake-tasks)
- [Starting a Rails console session](maintenance/README.md#starting-a-rails-console-session)
- [Starting a PostgreSQL superuser psql session](maintenance/README.md#starting-a-postgresql-superuser-psql-session)
- [Starting a PostgreSQL superuser `psql` session](maintenance/README.md#starting-a-postgresql-superuser-psql-session)
- [Container registry garbage collection](maintenance/README.md#container-registry-garbage-collection)
 
## Configuring
......@@ -44,7 +44,7 @@ to work best with the available resources. Check out the [documentation](setting
- [Storing Git data in an alternative directory](settings/configuration.md#storing-git-data-in-an-alternative-directory)
- [Changing the name of the Git user group](settings/configuration.md#changing-the-name-of-the-git-user--group)
- [Specify numeric user and group identifiers](settings/configuration.md#specify-numeric-user-and-group-identifiers)
- [Only start Omnibus GitLab services after a given filesystem is mounted](settings/configuration.md#only-start-omnibus-gitlab-services-after-a-given-filesystem-is-mounted)
- [Only start Omnibus GitLab services after a given file system is mounted](settings/configuration.md#only-start-omnibus-gitlab-services-after-a-given-file-system-is-mounted)
- [Disable user and group account management](settings/configuration.md#disable-user-and-group-account-management)
- [Disable storage directory management](settings/configuration.md#disable-storage-directories-management)
- [Configuring Rack attack](settings/configuration.md#configuring-rack-attack)
......
......@@ -112,7 +112,7 @@ the user or the `RAILS_ENV` environment variable; this is taken care of by the
This content has been moved to the
[GitLab debugging tips documentation](https://docs.gitlab.com/ee/administration/troubleshooting/debug.html#starting-a-rails-console-session).
 
## Starting a PostgreSQL superuser psql session
## Starting a PostgreSQL superuser `psql` session
 
If you need superuser access to the bundled PostgreSQL service you can
use the `gitlab-psql` command. It takes the same arguments as the
......@@ -128,7 +128,7 @@ least once. The `gitlab-psql` command cannot be used to connect to a
remote PostgreSQL server, nor to connect to a local non-Omnibus PostgreSQL
server.
 
### Starting a PostgreSQL superuser psql session in Geo tracking database
### Starting a PostgreSQL superuser `psql` session in Geo tracking database
 
Similar to the previous command, if you need superuser access to the bundled
Geo tracking database (`geo-postgresql`), you can use the `gitlab-geo-psql`.
......
......@@ -505,7 +505,7 @@ manage_storage_directories['enable'] = false
```
 
**Warning** The Omnibus GitLab package still expects these directories to exist
on the filesystem. It is up to the administrator to create and set correct
on the file system. It is up to the administrator to create and set correct
permissions if this setting is set.
 
Enabling this setting will prevent the creation of the following directories:
......@@ -526,10 +526,10 @@ Enabling this setting will prevent the creation of the following directories:
| `/var/opt/gitlab/gitlab-ci/builds` | `0700` | `git` | Holds CI build logs |
| `/var/opt/gitlab/.ssh` | `0700` | `git:git` | Holds authorized keys |
 
## Only start Omnibus GitLab services after a given filesystem is mounted
## Only start Omnibus GitLab services after a given file system is mounted
 
If you want to prevent Omnibus GitLab services (NGINX, Redis, Puma, etc.)
from starting before a given filesystem is mounted, add the following to
from starting before a given file system is mounted, add the following to
`/etc/gitlab/gitlab.rb`:
 
```ruby
......
......@@ -148,7 +148,7 @@ rubocop:
- gems
 
docs-lint:
image: "registry.gitlab.com/gitlab-org/gitlab-docs/lint:vale-2.3.4-markdownlint-0.23.2"
image: "registry.gitlab.com/gitlab-org/gitlab-docs/lint:ruby-2.7.2-alpine-3.12-vale-2.4.3-markdownlint-0.24.0"
stage: check
cache: {}
dependencies: []
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment