The gitlab logs are enormous, spammy and are half a terabyte per month.

The DNS resolution issue has been fixed[1][2].

[1] https://gitlab.com/gitlab-org/gitlab/-/issues/331699#note_635123263
[2] https://gitlab.com/gitlab-org/gitlab-pages/-/merge_requests/513

Fix #380

This reverts commit a863917f.

gitlab-pages uses the API source by default now[2] but DNS resolution is
broken[3] so we need to use the disk config source.
Reported upstream here[4].

[1] https://docs.gitlab.com/ee/administration/pages/#gitlab-pages-doesnt-work-after-upgrading-to-gitlab-140-or-above
[2] https://gitlab.com/gitlab-org/gitlab-pages/-/commit/9a30f40a785ffe586a79a75ebebabda5f513b76f
[3] https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4243
[4] https://gitlab.com/gitlab-org/gitlab/-/issues/331699#note_608473496

As keycloak is the canonical source of truth and interacting with gitlab
usually requires the username as identifier. As we don't want to
accidently assign permissions to a changed username disallow changing of
usernames altogether in Gitlab.

yaml: truthy value should be one of [false, true] (truthy)
yaml: wrong indentation: expected 4 but found 2 (indentation)
yaml: too few spaces before comment (comments)
yaml: missing starting space in comment (comments)
yaml: too many blank lines (1 > 0) (empty-lines)
yaml: too many spaces after colon (colons)
yaml: comment not indented like content (comments-indentation)
yaml: no new line character at the end of file (new-line-at-end-of-file)
load-failure: Failed to load or parse file
parser-error: couldn't resolve module/action 'hosts'. This often indicates a misspelling, missing collection, or incorrect module path.

GitLab becomes unhappy if it can't poll localhost.

Kristian Klausen authored 4 years ago and Sven-Hendrik Haase committed 4 years ago

Fix #228

Gitlab uses IMAP to fetch incoming mails. IMAP used to run on port 143
until the recent migration which disabled that port. This change makes
gitlab use port 993 and implicit TLS.

This cuts some complexity while also getting rid of the Docker userspace proxy which is slow compared
to kernelspace routing.
It also allows us to make GitLab consume a second IP for GitLab Pages without too much fuckery.

The idea is to make sure people don't blindly add cleanup tasks.

See https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.10.html#id3

Use Gitlab's official backup tool for dumping the database, git
repositories and other data with a wrapper script similiar to the
postgres and mysql backup scripts.

Signed-off-by: Jelle van der Waa <jelle@archlinux.org>