Skip to content

Commit 739123e

Browse files
committed
next.js -> nextjs in filter
1 parent fb05a1d commit 739123e

File tree

1 file changed

+3
-6
lines changed
  • src/pages/[platform]/deploy-and-host/fullstack-branching/monorepos

1 file changed

+3
-6
lines changed

src/pages/[platform]/deploy-and-host/fullstack-branching/monorepos/index.mdx

+3-6
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Amplify Gen 2 supports monorepo workflows for fullstack builds with monorepo too
5454
└── package.json
5555
```
5656

57-
Monorepos require a slightly different setup. We are going to deploy 3 Amplify apps:
57+
Monorepos require a slightly different setup. We are going to deploy three separate Amplify apps:
5858

5959
1. `my-shared-backend`
6060
2. `admin-dashboard`
@@ -65,11 +65,8 @@ Monorepos require a slightly different setup. We are going to deploy 3 Amplify a
6565
The first app, `my-shared-backend`, will be the only app that updates changes to the backend. The other apps will only run frontend builds that point to the shared backend.
6666

6767
1. To get started, deploy the shared backend Amplify app. With Gen 2, you can now setup backend-only CI/CD apps. Navigate to the Amplify console and select **Create new app**.
68-
69-
1. Once you connect your repository, select your monorepo project. Check the box that says **My app is a monorepo** and enter the path to your amplify backend.
70-
71-
![monorepo](/images/gen2/fullstack-branching/monorepo.png)
72-
68+
2. Once you connect your repository, select your monorepo project. Check the box that says **My app is a monorepo** and enter the path to your amplify backend.
69+
![monorepo](/images/gen2/fullstack-branching/monorepo.png)
7370
3. Your build settings should be automatically detected. Save and deploy.
7471

7572
## Deploy frontend apps

0 commit comments

Comments
 (0)