Skip to content

Commit 0a14a1d

Browse files
DO notes in heroku migration doc
1 parent 28d9206 commit 0a14a1d

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

docs/tutorials/migrating-from-heroku.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -350,6 +350,24 @@ GCP_PROJECT_ID=my-project-123456 defang compose up --provider gcp
350350
```
351351
</details>
352352
353+
### Deploying to DigitalOcean
354+
355+
If you're deploying to GCP, you'll need to invoke `defang compose up --provider digitalocean` with your DigitalOcean access credentials in the environment:
356+
357+
:::warning
358+
Some Heroku applications may require some manual adjustments to be deployed to DigitalOcean with Defang.
359+
Defang does not yet support deployments to DigitalOcean without a Dockerfile, so you will need to create one.
360+
Defang also does not yet support release tasks on DigitalOcean, so you will need to modify your services to run these tasks during initialization.
361+
:::
362+
363+
```
364+
export DIGITALOCEAN_TOKEN=your_digitalocean_token
365+
export SPACES_ACCESS_KEY_ID=your_spaces_access_key_id
366+
export SPACES_SECRET_ACCESS_KEY=your_spaces_secret_access_key
367+
$ defang compose up --provider digitalocean
368+
```
369+
370+
353371
## Step 3 - Migrating your data
354372
355373
:::tip

0 commit comments

Comments
 (0)