Building of the gitlab front-end showed the following error:

> Error: Cannot find module 'postcss'

Even though it did not fail the actual build. THis has been reported,
and a merge request was provided to fix this, but that has not been
merged yet.

Apply that patch to fix the build.

In CI, the images should always be built from scratch, and not use
cached layers. So pass --no-cache to `docker-compose build` to make sure
this happens.

This makes sure it only tries to strip elf binaries. Gets rid of some
warnings during build that shell scripts are not recognized file
formats.

`xargs` has the `-P` parameter to execute commands in parallel, so let's
use that.

We patched the Makefile to prevent the ruby component from being built
in the golang stage. But upstream already has a provision for this. By
creating the .ruby-bundle file, the target is already satisfied, so it
will be built. So let's use that.

These settings determine the group of gems to install. We disable the
testing group when building gitaly-ruby, but in the final image, these
settings are missing. That results in bundle trying to load the testing
gems, but since they have not been installed, it fails.

cmd -> cmds

To make sure they are restarted when the host or docker daemon is
restarted.

This allows us to persist gitaly logs

This makes it easier to updat to a new version on hosts

This ensures that zombie processes are cleaned up. Currently there are a
lot of git zombie processes in the gitaly container.

Each Dockerfile hardcoded what Alpine Linux version to use, and to
upgrade to a newer Alpine version, each occurrence has to be adjusted.

There should not be a reason to combine different Alpine Linux versions,
so it makes sense to define the Alpine Linux version in a single
location.

Add a ALPINE-VERSION file where the version is determined and provide it
as build args for each Dockerfile.

This does not work, as nginx only receives http connections, so it would
always be off.

This reverts commit 687a5894.

This allows gitlab to be tested locally where no https is used.

The files in /etc/gitlab/nginx need to be migrated, not in /etc/nginx.

155e8cab (gitlab/nginx: link config in new location, 2021-11-21) adjusted
the nginx configuration to a new location, but for existing setups, the
configuration still lives at the old location.

If the nginx config is missing, but still exists at the old location,
move it to the expected location.

This header is required for rails to recognize the connection is
encrypted and send the _gitlab_session cookie.

155e8cab (gitlab/nginx: link config in new location, 2021-11-21) moved
the default location for the nginx config to match upstream. Because in
already deployed setups, the config is missing, the entrypoint will copy
the default gitlab nginx config to the new location. This file was
missing the required header, resulting in a 422 unprocessible entity
error when trying to login, because the session cookie is missing.

Add the X-Forwarded-Ssl header to the default nginx config to address that.

Use `docker image inspect` to verify the image exists. If not, it should
obviously be built, even though none of the source files changed.

Gitlab checks the gitlab-shell version by looking at the VERSION file
that's present in the gitlab-shell directory. But because we copied
gitlab-shell only after installing gitlab in the image, gitlab could not
determine the version and would always show a warning that the version
is unknown.

Because the gitlab-shell directory contains a dangling
.gitlab-shell-secret symlink, gitlab fails during setup because it sees
that the size of the file is 0 and tries to write a new secret into it,
but fails because the file (symlink) exists.

Write a bogus secret in the location that the secrets file points to so
that gitlab skips generating the secret, as gitlab-shell already takes
care of that in the entrypoint.

Gitlab now supports specifying multiple databases for different
components, where the main (and first) entry specifies the main database
to use.

The old format will be unsupported in gitlab 15.

See: https://docs.gitlab.com/ee/development/database/multiple_databases.html#configdatabaseyml

- Describe the toplevel tasks so that they get returned by `task -l`
- Add more files to 'sources' to make sure tasks get executed when necessary

In alpine 3.14, the vhost configuration is expected to be located in
`/etc/nginx/http.d/`

Fixes #6

Since v14.1[0], gitaly requires timezone information. Make sure tzdata
is installed.

Fixes error

> "grpc_message":"unknown time zone Etc/UTC"

[0]:https://gitlab.com/gitlab-org/gitaly/-/merge_requests/3586

Although go is generally statically built, it still links against musl.
musl on Alpine Edge added support for qsort_r, and apparently golang
uses it if present.

When running these binaries on Alpine 3.13, which we still do for
gitlab, we get linking errors:

> Error relocating /usr/local/bin/gitaly-git2go-v14: qsort_r: symbol not
> found

Use golang from Alpine 3.13 to avoid this.