How hakhavanpour82/gitlab-portainer-cd-pipeline works
This repository documents a GitLab-to-Portainer deployment pipeline: a developer pushes a commit, GitLab builds and publishes a SHA-tagged image, then updates a Portainer stack; the backend runs on a private host. The available tree contains only the CI configuration and container/development configuration, not the documented application or stack template, so those components have no supported source path. Relationships shown here come from the README; no source excerpts were available.
Main entry points: .gitlab-ci.yml GitLab CI · Dockerfile SHA image
Components 7
Connections 7
- Developer → GitLab CI: pushes commit
README.md - GitLab CI → SHA image: builds image
README.md - GitLab CI → Container registry: publishes image
README.md - GitLab CI → Portainer CE: updates stack
README.md - Portainer CE → Portainer Agent: connects via
README.md - Portainer Agent → Backend container: runs workload
README.md - Container registry → Portainer Agent: image pull
README.md