Integrations overview
Git providers, Docker registries, and cloud accounts used by dFlow Services and Worker Nodes.
Written By Zoro
Last updated 3 days ago
dFlow connects to external systems
dFlow connects to external systems so Services can pull source code, images, and (on dFlow Cloud) provider-managed Worker Nodes.
Git sources
Connect repositories for App Services:
- GitHub integration: manual token or GitHub App flows.
- Git source integrations: GitLab, Bitbucket, Gitea, Azure DevOps, and shared patterns (tokens, branches, deploy triggers).
Automatic deploy on push depends on provider and configuration; see each guide.
Container registries
Docker registry integration: pull private images into Docker Services.
Cloud providers
AWS integration and Cloud provider accounts cover linking provider accounts where the product provisions or manages infrastructure.
Permissions and troubleshooting
- Integration permissions and prerequisites
- Integration troubleshooting
- Integration issues under Troubleshooting in the sidebar (symptom-led fixes and links to deploy logs)
Security and Organisation access
Integrations authorize dFlow to reach Git hosts, registries, and cloud APIs on behalf of your Organisation. Who may add or rotate those connections is governed by Roles and permissions under Security and Team Management in the sidebar and the Tenant access model under Security and Team Management in the sidebar.
SSH access to Worker Nodes and cloud firewall rules are separate from Git or registry tokens. Use SSH keys under Security and Team Management in the sidebar and Security groups under Security and Team Management in the sidebar when you attach compute.