You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tutorials/migrating-from-heroku.md
+35-3Lines changed: 35 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ No, Defang will use [Railpack](https://railpack.com/) to automatically build an
22
22
23
23
**Do I need a Docker Compose file?**
24
24
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.
26
26
:::
27
27
28
28
## Step 1 - Generating a Docker Compose file
@@ -91,7 +91,7 @@ $ heroku ps -a vast-badlands-production
91
91
=== web (Eco): bin/rails server -p ${PORT:-5000} -e $RAILS_ENV (1)
92
92
```
93
93
94
-
And a single postgres database:
94
+
And a single PostgreSQL database:
95
95
```
96
96
heroku addons -a vast-badlands-production
97
97
@@ -163,7 +163,39 @@ services:
163
163
164
164
## Step 2 - Deploying to your cloud account
165
165
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
+
167
199
168
200
* [Deploying to AWS](/docs/tutorials/deploy-to-aws.mdx)
169
201
* [Deploying to GCP](/docs/tutorials/deploy-to-gcp.mdx)
0 commit comments