Skip to content

Commit f0317f2

Browse files
Apply suggestions from code review
1 parent 45b4df2 commit f0317f2

File tree

1 file changed

+35
-3
lines changed

1 file changed

+35
-3
lines changed

docs/tutorials/migrating-from-heroku.md

Lines changed: 35 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ No, Defang will use [Railpack](https://railpack.com/) to automatically build an
2222

2323
**Do I need a Docker Compose file?**
2424

25-
No, Defang can automatically generate a compose file for your application.
25+
Defang does require a Docker Compose file to deploy your application, but you don't need to write one from scratch. Defang will automatically generate one for your Heroku application.
2626
:::
2727

2828
## Step 1 - Generating a Docker Compose file
@@ -91,7 +91,7 @@ $ heroku ps -a vast-badlands-production
9191
=== web (Eco): bin/rails server -p ${PORT:-5000} -e $RAILS_ENV (1)
9292
```
9393

94-
And a single postgres database:
94+
And a single PostgreSQL database:
9595
```
9696
heroku addons -a vast-badlands-production
9797
@@ -163,7 +163,39 @@ services:
163163
164164
## Step 2 - Deploying to your cloud account
165165
166-
Now all you need to do is deploy your application to the cloud.
166+
Now all you need to do is deploy your application to the cloud.
167+
168+
### Deploying to AWS
169+
170+
If you're deploying to AWS, you'll need to invoke `defang compose up` with your AWS access credentials in the environment:
171+
172+
```
173+
AWS_REGION=us-west-2 AWS_PROFILE=default defang compose up --provider aws
174+
```
175+
176+
See our full tutorial on [deploying to AWS](/docs/tutorials/deploy-to-aws.mdx).
177+
178+
### Deploying to GCP
179+
180+
If you're deploying to GCP, you'll need to invoke `defang compose up` with your GCP project id in the environment:
181+
182+
```
183+
GCP_PROJECT_ID=my-project-123 defang compose up --provider gcp
184+
```
185+
186+
See our full tutorial on [deploying to GCP](/docs/tutorials/deploy-to-gcp.mdx).
187+
188+
189+
### Deploying to DigitalOcean
190+
191+
If you're deploying to DigitalOcean, you'll need to invoke `defang compose up` with your DigitalOcean project id in the environment:
192+
193+
```
194+
DIGITALOCEAN_TOKEN=my-token-123 SPACES_ACCESS_KEY_ID=my-access-key-id SPACES_SECRET_ACCESS_KEY=my-access-key-secret defang compose up --provider digitalocean
195+
```
196+
197+
See our full tutorial on [deploying to DigitalOcean](/docs/tutorials/deploy-to-digitalocean.mdx).
198+
167199
168200
* [Deploying to AWS](/docs/tutorials/deploy-to-aws.mdx)
169201
* [Deploying to GCP](/docs/tutorials/deploy-to-gcp.mdx)

0 commit comments

Comments
 (0)