gitlab
GitLab server, using GitLab omnibus
- Category: Apps
- Status: 0
- Image:
gitlab
, 4, upstream - Healthcheck: Yes
- Backups: Yes
- Email: No
- Tests: No
- SSO: 1 (OAuth)
Quick start
abra app new gitlab --secrets
abra app config <app-name>
- Set REGISTRY_DOMAIN to a domain that you want to use for the GitLab container registry (optional)
- Set PAGES_DOMAIN to a domain that you want to use for the GitLab Pages service. NOTE: This cannot be a subdomain of the domain GitLab is hosted under. (optional)
- Set GITLAB_ROOT_EMAIL to an appropriate email address
abra app deploy <app-name>
Accessing Git via SSH
GitLab is configured to accept ssh:// git connections on the non-standard port 2222. This is because by default the Coop Cloud host server also must accept SSH connections for server management, so port 22 is already occupied and can't be used by GitLab.
To configure your local git client to use the non-standard port by default, modify your local client's ~/.ssh/config file to include the following:
Host: git.yourserver.org
Hostname: git.yourserver.org
Port 2222
SSO Configuration
- Create a Provider and Application in Authentik: https://docs.goauthentik.io/integrations/services/gitlab/#openid-connect-auth
- Note the Provider ID and Secret
- Run
abra app config <app-name>
- Uncomment the Authentik Configuration config block
- Set
SSO_PROVIDER_ID
to the Authentik Provider ID
- Run
abra app secret insert <app-name> sso_provider_secret v1 <Authentik Provider Secret>
For more, see docs.coopcloud.tech
.
Languages
Shell
100%