Guides
Step-by-step guidance for getting specific things done with Snap CD. Where the How it Works section explains the mechanisms, this section gives the steps.
- Maintenance Mode: bringing the Server to a safe stop so infrastructure underneath it can be changed, without losing in-flight work
- Switching Service Bus: moving between the SQL Server and Azure Service Bus transports, or to a different Azure Service Bus namespace
- Monorepos: scoping gitops triggers to the directories a Module depends on, and versioning components independently with tag prefixes
- Splitting a Monolith: using the demonolith CLI to split a monolithic Terraform/OpenTofu root into independent Modules, migrate the state safely, and adopt the result into Snap CD
- Platform Team on Azure: deploying Snap CD on AKS from a bootstrap, then a platform team that gives an application team its own tenancy and Runner
Last updated on