Mauricio Siu 8f84a52855 fix(gitlab-ce): serve on the generated domain (remove removed unicorn config, pin omnibus) ...

The template set unicorn['worker_processes'] / unicorn['worker_timeout'] in
GITLAB_OMNIBUS_CONFIG. Unicorn was removed in GitLab 14.0, so on current
gitlab-ce images `gitlab-ctl reconfigure` aborts with "Removed configurations
found in gitlab.rb" and GitLab never starts serving — the generated domain
returned 502 Bad Gateway (issue #380).

Rewrite the template as the official all-in-one Omnibus setup:
- pin gitlab/gitlab-ce:19.1.2-ce.0 instead of :latest
- external_url http://<domain> with nginx listen_port 80 / listen_https false
  (TLS terminates at Traefik)
- set gitlab_rails['initial_root_password'] from a generated template password
- puma single mode + prometheus monitoring off to keep memory reasonable
- drop the external postgres/redis containers (Omnibus bundles and manages
  its own) and the broken ports entries ("2224" published a random host port
  while sshd listens on 22)

Verified on a live Dokploy instance: domain serves the GitLab sign-in page
and root login with the generated password works.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-14 11:11:25 -06:00

..

docker-compose.yml

fix(gitlab-ce): serve on the generated domain (remove removed unicorn config, pin omnibus)

2026-07-14 11:11:25 -06:00

gitlab-ce.svg

…

meta.json

fix(gitlab-ce): serve on the generated domain (remove removed unicorn config, pin omnibus)

2026-07-14 11:11:25 -06:00

template.toml

fix(gitlab-ce): serve on the generated domain (remove removed unicorn config, pin omnibus)

2026-07-14 11:11:25 -06:00