CF Swarm: End-to-End Coldfusion Pipeline with Cont
  • Preface: Who Is This Guide For?
  • About the Author & License
  • Part 1: What Containers Mean To Web Applications (and You)
  • Part 2: Before You Begin
  • Part 3: Docker in Development
    • Installing Docker: Initial Setup
    • Running Docker: Clone a Working Development Stack
    • docker-compose.yml: A Closer Look
    • nginx.conf: Reverse Proxy to a CF Engine
  • Part 4: Building Images and Container Registries
    • Our First Image: A Sample Build Environment
  • Part 5: Choosing a Cloud Infrastructure Provider
  • Part 6: The Production Network Layout (How Many Instances and What Kind)
    • Your First Instance: Provisioning
    • Your First Instance: Basic Configuration & Security
    • Your First Instance: (Optional) Provider-Level Firewall
    • Your First Instance: Taking A Snapshot
  • Part 7: Production Setup (Outside the Swarm)
    • Pipeline Setup: Instance Prep
    • Pipeline Setup: VPN Server
    • Pipeline Setup: Source Control & Container Registry
    • Pipeline Setup: Database Prep
      • Pipeline Setup: MySQL
    • Pipeline Setup: Microsoft SQL Server
    • Pipeline Setup: Provider Firewall
  • Part 8: Production Setup (The Swarm)
    • Container Strategy
  • Credits & Acknowledgments
Powered by GitBook
On this page
  • Take a Template Snapshot
  • Destroy Your Droplet
  1. Part 6: The Production Network Layout (How Many Instances and What Kind)

Your First Instance: Taking A Snapshot

PreviousYour First Instance: (Optional) Provider-Level FirewallNextPart 7: Production Setup (Outside the Swarm)

Last updated 7 years ago

Take a Template Snapshot

Time Required: 5 Minutes (Mostly waiting for snapshot generation)

Once you've completed the Initial Server Setup, shutdown your instance with:

sudo shutdown -h now

You can power off your instance from your provider control panel (The Power sub-menu for your droplet on DigitalOcean) but it is always best to do so from the command line. (Note: On occasion, you may still have to power off your droplet from the control panel, even if you shut it down from the command line)

Select your template Droplet:Then select the Snapshots menu and enter a name for your template snapshot. By default, the snapshot will be named after the instance, followed by a unique code; You can remove the trailing -code and just call it template since we'll be destroying our Droplet with the same name in a moment and left with only one thing called template.

Destroy Your Droplet

Now that we have a snapshot we can use to build all our future Droplets, we don't need this one anymore. Select the Destroy submenu for your Droplet.