Remote Development on DigitalOcean Droplets

Provision DigitalOcean Droplets as Coder workspaces with this example template.

Prerequisites

To deploy workspaces as DigitalOcean Droplets, you'll need:

DigitalOcean personal access token (PAT)
DigitalOcean project ID (you can get your project information via the doctl CLI by running doctl projects list)
- Remove the following sections from the main.tf file if you don't want to associate your workspaces with a project:
  - variable "project_uuid"
  - resource "digitalocean_project_resources" "project"
Optional: DigitalOcean SSH key ID (obtain via the doctl CLI by running doctl compute ssh-key list)
- Note that this is only required for Fedora images to work.

Authentication

This template assumes that the Coder Provisioner is run in an environment that is authenticated with Digital Ocean.

Obtain a Digital Ocean Personal Access Token and set the DIGITALOCEAN_TOKEN environment variable to the access token. For other ways to authenticate consult the Terraform provider's docs.

Architecture

This template provisions the following resources:

DigitalOcean VM (ephemeral, deleted on stop)
Managed disk (persistent, mounted to /home/coder)

This means, when the workspace restarts, any tools or files outside of the home directory are not persisted. To pre-bake tools into the workspace (e.g. python3), modify the VM image, or use a startup script.

Note

This template is designed to be a starting point! Edit the Terraform to extend the template to support your use case.