🚀 GitLab Docker Setup

Self-host GitLab Community Edition + a Group Runner with Docker Compose in under 5 minutes. Includes ready-to-use Apache/Nginx reverse-proxy configs, optional SMTP, and a battle-tested CI/CD setup for SSH-based deployments.

---

📚 Documentation

• 🇬🇧 English — main setup guide
• 🇫🇷 Français — guide d'installation

For the full CI/CD + SSH-deploy walkthrough:

• 🇬🇧 CI/CD guide (EN)
• 🇫🇷 Guide CI/CD (FR)

For the optional GitLab Stats dashboard (Nuxt 4 team commit activity, OAuth-protected):

• 🇬🇧 Stats dashboard (EN)
• 🇫🇷 Dashboard Stats (FR)

📊 Optional: GitLab Stats dashboard

A small Nuxt 4 + Nuxt UI + ApexCharts dashboard ships in gitlab-stats-nuxt/ to visualise development activity (commits, lines, types, by developer) across every project visible to a server-side admin token. Visitors log in via OAuth GitLab so the link can safely be shared with the team / your manager. Read-only by design — only read_api on the token and read_user on the OAuth scope.

Highlights:

• Filters: period (7d / 30d / 90d / 6 months / 1 year / all), project, multi-developer selector.
• Multi-developer stacked charts with legend (top 10 + "Autres"): by day, by ISO week, by month, by hour (UTC), by day of week.
• Donut for commit types, top-15 by project, top-15 by developer, additions/deletions per month.
• KPIs: projects, commits, active days, average per active day, lines added / removed / changed.
• In-memory cache with manual refresh, clickable project + commit links.

The service is fully optional — leave STATS_* empty in .env and only GitLab + Runner start. To deploy it later, follow docs/en/STATS.md (or FR) and run:

docker compose build gitlab-stats
docker compose up -d --no-deps gitlab-stats

--no-deps guarantees your running GitLab and Runner are never recreated.

🧹 Optional: Auto-clean unused Docker volumes

CI jobs that run Docker Compose tests can leave unused volumes behind (node_modules, build artifacts, runner cache volumes, anonymous volumes, and so on). If the host runs several projects, avoid deleting volumes by project name. A safer generic cleanup is to remove only Docker volumes that are already marked as dangling/unused.

Preview what would be removed:

sudo docker volume ls -f dangling=true --format 'table {{.Name}}\t{{.Driver}}\t{{.Scope}}'

Run the cleanup manually:

sudo sh -c 'docker volume ls -qf dangling=true | xargs -r docker volume rm'

Install a daily cron job at 03:00:

sudo tee /etc/cron.d/docker-volume-cleanup >/dev/null <<'EOF'
# Remove unused Docker volumes every day at 03:00.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

0 3 * * * root docker volume ls -qf dangling=true | xargs -r docker volume rm >/dev/null 2>&1
EOF

sudo chmod 644 /etc/cron.d/docker-volume-cleanup
sudo chown root:root /etc/cron.d/docker-volume-cleanup

Verify the installed cron file:

cat /etc/cron.d/docker-volume-cleanup

This does not remove volumes attached to existing containers. It should not touch active volumes such as portainer_data, rabbitmq_*, or a mounted GitLab Runner config volume/path while they are in use.

---

📜 Changelog

See CHANGELOG.md.

📄 License

MIT — see LICENSE.