| display_name | DigitalOcean Droplet (Linux) | |||
|---|---|---|---|---|
| description | Provision DigitalOcean Droplets as Coder workspaces | |||
| icon | ../../../site/static/icon/do.png | |||
| maintainer_github | coder | |||
| verified | true | |||
| tags |
|
Provision DigitalOcean Droplets as Coder workspaces with this example template.
To deploy workspaces as DigitalOcean Droplets, you'll need:
-
DigitalOcean personal access token (PAT)
-
DigitalOcean project ID, which the template builder prompts for. You can get your project information via the
doctlCLI by runningdoctl projects list. -
Optional: DigitalOcean SSH key ID, which the template builder prompts for (obtain via the
doctlCLI by runningdoctl compute ssh-key list).- Note that this is only required for Fedora images to work. Leave it as
0if you don't need it.
- Note that this is only required for Fedora images to work. Leave it as
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.
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.