diff --git a/src/pages/[platform]/deploy-and-host/fullstack-branching/mono-and-multi-repos/index.mdx b/src/pages/[platform]/deploy-and-host/fullstack-branching/mono-and-multi-repos/index.mdx index 3bd78f78fc6..02e537473d6 100644 --- a/src/pages/[platform]/deploy-and-host/fullstack-branching/mono-and-multi-repos/index.mdx +++ b/src/pages/[platform]/deploy-and-host/fullstack-branching/mono-and-multi-repos/index.mdx @@ -75,8 +75,7 @@ This will generate the `amplify_outputs.json` file that contains all the informa 4. To validate that your frontend can connect to the backend, add the `Authenticator` login form to your app. -```ts -// pages/_app.tsx +```ts title="pages/_app.tsx" import { withAuthenticator } from '@aws-amplify/ui-react'; import { Amplify } from 'aws-amplify'; import outputs from '@/amplify_outputs.json'; @@ -150,7 +149,7 @@ aws amplify create-webhook --app-id FRONTEND-APPID --branch-name main --region 1. Now update the build settings for the `backend-app` to include the `curl` command to trigger a frontend build any time there are changes to the backend. -``` yaml +```yaml title="amplify.yml" version: 1 backend: phases: diff --git a/src/pages/[platform]/deploy-and-host/sandbox-environments/features/index.mdx b/src/pages/[platform]/deploy-and-host/sandbox-environments/features/index.mdx index 1fae0711111..236e28ce044 100644 --- a/src/pages/[platform]/deploy-and-host/sandbox-environments/features/index.mdx +++ b/src/pages/[platform]/deploy-and-host/sandbox-environments/features/index.mdx @@ -219,12 +219,12 @@ Alternatively, if you want to generate the config for a branch environment to te For Web and React Native, generating the config with the default format and output directory. ```bash title="Terminal" showLineNumbers={false} -npx ampx generate config --app-id --branch main +npx ampx generate outputs --app-id --branch main ``` ```bash title="Terminal" showLineNumbers={false} -npx ampx generate config --app-id --branch main --format dart --out-dir lib +npx ampx generate outputs --app-id --branch main --format dart --out-dir lib ``` @@ -240,7 +240,7 @@ npx ampx generate outputs --app-id --branch main --out-dir app/src/main ```bash title="Terminal" showLineNumbers={false} -npx ampx generate config --app-id --format json-mobile +npx ampx generate outputs --app-id --format json-mobile ``` Once the sandbox environment is running, it will generate the backend outputs file for your frontend application. However, Xcode won't be able to recognize them. For recognizing the files, you need to drag and drop the generated files to your project. diff --git a/src/pages/[platform]/reference/amplify_outputs/index.mdx b/src/pages/[platform]/reference/amplify_outputs/index.mdx index aaf518698f9..1719e0dd0d3 100644 --- a/src/pages/[platform]/reference/amplify_outputs/index.mdx +++ b/src/pages/[platform]/reference/amplify_outputs/index.mdx @@ -31,7 +31,7 @@ export async function getStaticProps() { In Amplify Gen 2, the CLI will generate an `amplify_outputs.json` file with your backend's outputs such as your Data endpoint and Auth metadata. This file -- also known as the "client configuration file" -- is used to configure the client libraries in order to interact with your backend resources. Locally, this file is created while using `ampx sandbox`. In Amplify's CI/CD, this is created automatically for you based on the current Amplify app ID and git branch. -You can also manually create this file for a specified Amplify app ID and branch, or an AWS CloudFormation stack name with [`ampx generate config`](/[platform]/reference/cli-commands#npx-ampx-generate-config). +You can also manually create this file for a specified Amplify app ID and branch, or an AWS CloudFormation stack name with [`ampx generate outputs`](/[platform]/reference/cli-commands#npx-ampx-generate-outputs). {/* @TODO full type/interface to reference */}