Skip to content

Commit 3478674

Browse files
committed
README.md: fix some typo
- fix some typo in docs - #google-cloud-storage-gcs-remote-backup -> #google-cloud-storage-gcs-remote-backups (missing trailing "s") - opensource -> open source - #generation-of-self-signed-certificate -> #generation-of-a-self-signed-certificate (missing "-a") - postresql -> postgresql (missing "g") - STASRTSSL -> STARTTLS - clientside -> client side - raketasks -> rake tasks - healthcheck -> health check When referring to docker-compose's "healthcheck" setting, the notation without spaces is intentionally left. - fix unclosed parentheses
1 parent 0d39d55 commit 3478674

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@
4545
- [SAML](#saml)
4646
- [Crowd](#crowd)
4747
- [Microsoft Azure](#microsoft-azure)
48-
- [Generic OAuth2](#Generic-OAuth2)
48+
- [Generic OAuth2](#generic-oauth2)
4949
- [OpenID Connect](#openid-connect)
5050
- [Gitlab Pages](#gitlab-pages)
5151
- [External Issue Trackers](#external-issue-trackers)
@@ -59,7 +59,7 @@
5959
- [Restoring Backups](#restoring-backups)
6060
- [Automated Backups](#automated-backups)
6161
- [Amazon Web Services (AWS) Remote Backups](#amazon-web-services-aws-remote-backups)
62-
- [Google Cloud Storage (GCS) Remote Backups](#google-cloud-storage-gcs-remote-backup)
62+
- [Google Cloud Storage (GCS) Remote Backups](#google-cloud-storage-gcs-remote-backups)
6363
- [Rake Tasks](#rake-tasks)
6464
- [Import Repositories](#import-repositories)
6565
- [Upgrading](#upgrading)
@@ -72,7 +72,7 @@
7272

7373
## Introduction
7474

75-
Dockerfile to build a [GitLab](https://about.gitlab.com/) image for the [Docker](https://www.docker.com/products/docker-engine) opensource container platform.
75+
Dockerfile to build a [GitLab](https://about.gitlab.com/) image for the [Docker](https://www.docker.com/products/docker-engine) open source container platform.
7676

7777
GitLab CE is set up in the Docker image using the [install from source](https://docs.gitlab.com/ce/install/installation.html) method as documented in the official GitLab documentation.
7878

@@ -599,11 +599,11 @@ The default path image is configured to look for the trusted SSL certificates is
599599

600600
Copy the `ca.crt` file into the certs directory on the [datastore](#data-store). The `ca.crt` file should contain the root certificates of all the servers you want to trust. With respect to GitLab CI, this will be the contents of the gitlab_ci.crt file as described in the [README](https://github.com/sameersbn/docker-gitlab-ci/blob/master/README.md#ssl) of the [docker-gitlab-ci](https://github.com/sameersbn/docker-gitlab-ci) container.
601601

602-
By default, our own server certificate [gitlab.crt](#generation-of-self-signed-certificate) is added to the trusted certificates list.
602+
By default, our own server certificate [gitlab.crt](#generation-of-a-self-signed-certificate) is added to the trusted certificates list.
603603

604604
#### Deploy to a subdirectory (relative url root)
605605

606-
By default, GitLab expects that your application is running at the root e.g.. /). This section explains how to run your application inside a directory.
606+
By default, GitLab expects that your application is running at the root (e.g.. /). This section explains how to run your application inside a directory.
607607

608608
Let's assume we want to deploy our application to '/git'. GitLab needs to know this directory to generate the appropriate routes. This can be specified using the `GITLAB_RELATIVE_URL_ROOT` configuration option like so:
609609

@@ -1876,7 +1876,7 @@ The database type. Currently only postgresql is supported. Possible values: `pos
18761876

18771877
##### `DB_ENCODING`
18781878

1879-
The database encoding. For `DB_ADAPTER` values `postresql` this parameter defaults and `utf8` respectively.
1879+
The database encoding. For `DB_ADAPTER` values `postgresql` this parameter defaults and `utf8` respectively.
18801880

18811881
##### `DB_HOST`
18821882

@@ -1984,7 +1984,7 @@ Enable SSL. Defaults to `true`.
19841984

19851985
##### `IMAP_STARTTLS`
19861986

1987-
Enable STARTSSL. Defaults to `false`.
1987+
Enable STARTTLS. Defaults to `false`.
19881988

19891989
##### `IMAP_MAILBOX`
19901990

@@ -2528,7 +2528,7 @@ Sentry DSN. No defaults.
25282528

25292529
##### `SENTRY_CLIENTSIDE_DSN`
25302530

2531-
Sentry clientside DSN. No defaults.
2531+
Sentry client side DSN. No defaults.
25322532

25332533
##### `SENTRY_ENVIRONMENT`
25342534

@@ -2670,7 +2670,7 @@ docker run --name gitlab -it --rm [OPTIONS] \
26702670
sameersbn/gitlab:18.0.2 app:rake gitlab:env:info
26712671
```
26722672

2673-
You can also use `docker exec` to run raketasks on running gitlab instance. For example,
2673+
You can also use `docker exec` to run rake tasks on running gitlab instance. For example,
26742674

26752675
```bash
26762676
docker exec --user git -it gitlab bundle exec rake gitlab:env:info RAILS_ENV=production
@@ -2818,7 +2818,7 @@ services:
28182818
start_period: 2m
28192819
```
28202820

2821-
Then you will be able to consult the healthcheck log by executing:
2821+
Then you will be able to consult the health check log by executing:
28222822

28232823
```bash
28242824
docker inspect --format "{{json .State.Health }}" $(docker-compose ps -q gitlab) | jq

0 commit comments

Comments
 (0)