Skip to content

Commit 52a28b7

Browse files
DO notes in heroku migration doc
1 parent ce68232 commit 52a28b7

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
@@ -348,6 +348,24 @@ GCP_PROJECT_ID=my-project-123456 defang compose up --provider gcp
348348
```
349349
</details>
350350
351+
### Deploying to DigitalOcean
352+
353+
If you're deploying to GCP, you'll need to invoke `defang compose up --provider digitalocean` with your DigitalOcean access credentials in the environment:
354+
355+
:::warning
356+
Some Heroku applications may require some manual adjustments to be deployed to DigitalOcean with Defang.
357+
Dockerfiles are required for deployments to DigitalOcean, so you may need to create one if your application does not already have one. Support for automatic Dockerfile generation is coming soon with [Railpack](/docs/concepts/railpack.md).
358+
Defang also does not yet support [one-off jobs](/docs/concepts/one_off_jobs) on DigitalOcean, so you will need to modify your services to run these tasks during initialization.
359+
:::
360+
361+
```
362+
export DIGITALOCEAN_TOKEN=your_digitalocean_token
363+
export SPACES_ACCESS_KEY_ID=your_spaces_access_key_id
364+
export SPACES_SECRET_ACCESS_KEY=your_spaces_secret_access_key
365+
$ defang compose up --provider digitalocean
366+
```
367+
368+
351369
## Step 3 - Migrating your data
352370
353371
:::tip

0 commit comments

Comments
 (0)