gitlab
/
omnibus-gitlab
mirror of https://gitlab.com/gitlab-org/omnibus-gitlab.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'docs-lp-fix-links' into 'master' 

Fix links in GitLab Omnibus project

See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/7579

Merged-by: Evan Read <eread@gitlab.com>
Approved-by: Evan Read <eread@gitlab.com>
Co-authored-by: Lysanne Pinto <lpinto@gitlab.com>
This commit is contained in:
Evan Read 2024-05-02 00:48:55 +00:00
parent 504a0928a1 460e3ffd20
commit 105e970b9e
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/architecture/index.md
View File

@ -148,7 +148,7 @@ parsed correctly.
### runit
GitLab uses [runit](http://smarden.org/runit/) recipes for
GitLab uses [runit](https://smarden.org/runit/) recipes for
service management and supervision. runit recipes do the job of identifying the
init system used by the OS and performing basic service management tasks like
creating necessary service files for GitLab, service enabling, and service

2
doc/architecture/multiple_database_support/index.md
View File

@ -82,7 +82,7 @@ cluster for all databases_ to _one cluster per database_.
Therefore the HA configuration of logical databases must be independent of the
deployment model.
Consul [services](https://developer.hashicorp.com/consul/docs/srvices/configuration/services-configuration-reference)
Consul [services](https://developer.hashicorp.com/consul/docs/services/configuration/services-configuration-reference)
can have multiple health-checks and [watches](https://developer.hashicorp.com/consul/docs/dynamic-app-config/watches#service).
At this level, Omnibus GitLab defines _a Consul service per database cluster_
and _a service watch per logical database_.

2
doc/settings/logs.md
View File

@ -77,7 +77,7 @@ The [runit-managed](../architecture/index.md#runit) services in Linux package in
GitLab last wrote to that file.
- `zmore` and `zgrep` allow viewing and searching through both compressed or uncompressed logs.
Read the [svlogd documentation](https://smarden.org/runit/svlogd.8.html) for more information
Read the [svlogd documentation](https://smarden.org/runit/svlogd.8) for more information
about the files it generates.
You can modify svlogd settings via `/etc/gitlab/gitlab.rb` with the following settings:

4
doc/settings/redis.md
View File

@ -120,7 +120,7 @@ redis['announce_ip_from_hostname'] = true
## Setting the Redis Cache instance as an LRU
Using multiple Redis instances allows you to configure Redis as a
[Least Recently Used cache](https://redis.io/docs/manual/eviction/). Note you should only
[Least Recently Used cache](https://redis.io/docs/latest/operate/rs/databases/memory-performance/eviction-policy/). Note you should only
do this for the Redis cache, rate-limiting, and repository cache instances; the Redis queues, shared
state instances, and tracechunks instances should never be configured as an LRU,
since they contain data (e.g. Sidekiq jobs) that is expected to be persistent.
@ -160,7 +160,7 @@ You can configure Redis to run behind SSL.
NOTE:
Some `redis-cli` binaries are not built with support for directly connecting to a Redis server over TLS.
If your `redis-cli` doesn't support the `--tls` flag, you will have to use something like
[`stunnel`](https://redis.com/blog/stunnel-secure-redis-ssl/) to connect to the
[`stunnel`](https://redis.io/blog/stunnel-secure-redis-ssl/) to connect to the
Redis server using `redis-cli` for any debugging purposes.
### Make GitLab client connect to Redis server over SSL

4
doc/settings/smtp.md
View File

@ -142,7 +142,7 @@ gitlab_rails['smtp_force_ssl'] = false
NOTE:
Gmail has [strict sending limits](https://support.google.com/a/answer/166852)
that can impair functionality as your organization grows. We strongly recommend using a
transactional service like [SendGrid](https://sendgrid.com/) or [Mailgun](https://www.mailgun.com/)
transactional service like [SendGrid](https://sendgrid.com/en-us) or [Mailgun](https://www.mailgun.com/)
for teams using SMTP configuration.
```ruby
@ -1216,7 +1216,7 @@ gitlab_rails['gitlab_email_from'] = 'username@example.com'
gitlab_rails['gitlab_email_reply_to'] = 'username@example.com'
```
Check the SMTP user name and SMTP user password from the ESS [dashboard](https://pfs.nifcloud.com/help/ess/dashboard.htm).
Check the SMTP user name and SMTP user password from the ESS [dashboard](https://docs.nifcloud.com/ess/help/dashboard.htm).
`gitlab_email_from` and `gitlab_email_reply_to` must be ESS authenticated sender email addresses.
### Sina mail