Infrastructure

Where the Applications section is about what you deploy, this section is about where and how it runs. Notploy is built on standard infrastructure components — Docker, Docker Swarm and Traefik — and this section documents how Notploy manages them and how you configure the surrounding services.

Servers and execution targets

Your workloads run on one or more servers. Start with the deployment options to choose a topology, then learn how each type works:

Networking and routing

• Traefik — the reverse proxy that routes traffic to services and terminates TLS.
• DNS providers — automate DNS records (Cloudflare, Route53).
• Certificates — automatic and custom TLS certificate lifecycle.

Storage

• Registries — push and pull images for remote servers and clusters.
• Object storage (S3) — destinations for backups.
• Backups and volume backups — protect data and restore it.

Secrets and integrations

• Secrets providers — read secrets from external vaults.
• Notifications — delivery channels for deployments and alerts.

How each infrastructure guide is structured

Because infrastructure mistakes are expensive, each guide in this section covers, where relevant:

• Purpose — what the component is for and when to use it.
• Architecture — how it fits into Notploy and what it depends on.
• Prerequisites — resources, permissions, ports and protocols.
• Configuration — how to set it up.
• Verification — how to confirm it works.
• Troubleshooting and recovery — common failures and their consequences.

Related

• Discover → Architecture
• Ecosystem
• Operate & administer