WARNING: This Ansible playbook is not actively maintained anymore. It may be out of date and generally not of very high quality. Send some PRs or get in touch if you'd like to maintain it. Users are generally recommended to migrate their Gitlab installation to the gitea-docker-ansible-deploy playbook (powered by Gitea, an alternative to Gitlab).
This Ansible playbook can help you set up a Gitlab instance:
- on your own Debian/CentOS/RedHat server
- with all services (Gitlab, Postgres, Redis, etc.) being put in Docker containers
- powered by the sameersbn/docker-gitlab Docker image
SSL certificates are automatically retrieved from Let's Encrypt.
To configure and install Gitlab on your own server, follow the README in the docs/ directory.
This playbook sets up your server using the following Docker images:
-
sameersbn/gitlab - the sameersbn/docker-gitlab Gitlab server image. Note: this is not the official gitlab/gitlab-ce Gitlab image. We use the
sameersbn/gitlabimage, because it doesn't force us into running services (Postgres database, Redis server) into the Gitlab container (we run those services in other container ourselves). -
redis - the official Redis image. Note: we don't use the sameersbn/redis image (which is recommended for sameersbn/gitlab), because the official one is more up-to-date
-
sameersbn/postgresql - the sameersbn/docker-postgresql Postgres server. Note: we don't use the official Postgres image, because Gitlab requires additional extensions (
pg_trgm). -
devture/exim-relay - an Exim SMTP server we use by default, so that Gitlab can send emails. By default, email is delivered directly, but you can also configure the service to relay emails through another SMTP server.
- Github issues: spantaleev/gitlab-docker-ansible-deploy/issues