DigitalOcean
API › Tokens › Generate, Custom scopes: droplet (create, read, update, delete), regions, sizes, image and actions (read), tag (create, read).
Create the token
In the DigitalOcean control panel, open API › Tokens and choose Generate New Token.
Name it (
codemany) and pick an expiration.Under scopes, choose Custom Scopes and tick exactly these ten:
| Resource | Scopes |
|---|---|
| droplet | droplet:create, droplet:read, droplet:update, droplet:delete |
| regions | regions:read |
| sizes | sizes:read |
| image | image:read |
| actions | actions:read |
| tag | tag:create, tag:read |
Then Generate Token, and copy it.
Connect
In Add a cloud machine, choose DigitalOcean.
Paste the token into API token (one line, no spaces) and choose Connect.
One read call checks the token before it is kept. It is kept in the Mac Keychain or the Linux keyring on this machine, never in a file, and never sent to Codemany's servers. Whatever the token can see, Codemany only touches droplets tagged codemany-managed.
Regions and sizes
- Regions: those taking new droplets.
- Sizes: the droplet sizes available in that region with 2 vCPUs or more, all x86: DigitalOcean has no Arm droplets.
- Image: Ubuntu 24.04 LTS (x64); the disk is the size's own.
- Prices: DigitalOcean's, in USD.
Droplets can't give each job a fresh VM.
Cost
DigitalOcean bills a powered-off droplet in full. Idle stop saves nothing here, so it is off by default, and a spending cap isn't offered. Only removing the machine stops the bill. See Remove a cloud machine.
Revoke access
Delete the token under API › Tokens. Remove the machines from Codemany first, so their runners, seats and fleet membership go too.