... | ... | @@ -928,8 +928,8 @@ notifications, for example for issues with an due date, which might be |
|
|
confusing for users if this is a development server. If this is a
|
|
|
production server, that's a good thing. If it's a development server,
|
|
|
you may want to disable email altogether in the GitLab server, with
|
|
|
this line in `hiera/roles/gitlab_dev.yml` in the `tor-puppet.git`
|
|
|
repository:
|
|
|
this line in Hiera data (eg. `hiera/roles/gitlab_dev.yml`) in the
|
|
|
`tor-puppet.git` repository:
|
|
|
|
|
|
profile::gitlab::app::email_enabled: false
|
|
|
|
... | ... | @@ -1254,10 +1254,6 @@ rates and so on. There was an issue open about [monitoring individual |
|
|
runners](https://gitlab.torproject.org/tpo/tpa/team/-/issues/41042) but the runners do not expose (nor do they have access to)
|
|
|
that information, so that was scrapped.
|
|
|
|
|
|
There is a development server called `gitlab-dev-01` that can be used
|
|
|
to test dangerous things if there is a concern a change could break
|
|
|
the production server.
|
|
|
|
|
|
## Logs and metrics
|
|
|
|
|
|
GitLab keeps an extensive (excessive?) amount of logs, in
|
... | ... | |