create-wirejs-deploy-amplify-basic 1.0.165 → 1.0.166

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,36 @@
1
+ # Amplify Deployment Notes
2
+
3
+ This document covers important topics specific to AWS Amplify deployments of this app.
4
+
5
+ ## Email Sending (SES)
6
+
7
+ This app uses `EmailSender` from `wirejs-resources` to send email. Locally, emails are written to the `.outbox` folder in your project root for easy inspection. In Amplify deployments, emails are sent via [AWS Simple Email Service (SES)](https://aws.amazon.com/ses/).
8
+
9
+ ### Verifying Your Sender Address
10
+
11
+ AWS SES requires that sender email addresses be verified before you can send from them. **During each Amplify deployment, a verification email is automatically sent to any unverified sender address** used in your app. Check your inbox for an email from AWS and click the verification link.
12
+
13
+ If you need to re-trigger verification manually:
14
+
15
+ 1. Open the [AWS SES Verified Identities console](https://console.aws.amazon.com/ses/home#/verified-identities).
16
+ 2. Click **Create identity**.
17
+ 3. Select **Email address** and enter the address used in your `EmailSender` constructor.
18
+ 4. Click **Create identity** and check your inbox for a verification email.
19
+ 5. Click the verification link in the email.
20
+
21
+ ### SES Sandbox Mode
22
+
23
+ New AWS accounts start in **SES sandbox mode**, which means:
24
+
25
+ - You can only send email **to** verified addresses.
26
+ - There are daily sending limits.
27
+
28
+ To send email to unverified recipients (i.e., real users), you must request **production access**:
29
+
30
+ 1. Go to [SES Account Dashboard](https://console.aws.amazon.com/ses/home#/account).
31
+ 2. Click **Request production access**.
32
+ 3. Fill in the request form and submit.
33
+
34
+ AWS typically reviews these requests within 24 hours.
35
+
36
+ For more information, see the [AWS SES documentation](https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html).
package/bin.js CHANGED
@@ -1,5 +1,6 @@
1
1
  #!/usr/bin/env node
2
2
 
3
+ const fs = require('fs');
3
4
  const copy = require('recursive-copy');
4
5
 
5
6
  (async () => {
@@ -7,6 +8,30 @@ const copy = require('recursive-copy');
7
8
  await copy(`${__dirname}/assets/amplify.yml`, `./amplify.yml`);
8
9
  await copy(`${__dirname}/assets/customHttp.yml`, `./customHttp.yml`);
9
10
 
11
+ // Create docs directory and copy Amplify-specific documentation.
12
+ fs.mkdirSync('./docs', { recursive: true });
13
+ await copy(`${__dirname}/assets/docs-amplify.md`, `./docs/amplify.md`);
14
+
15
+ // Append an Amplify Deployments section to the project README if it exists.
16
+ const readmePath = './README.md';
17
+ const amplifySection = `
18
+ ## Amplify Deployments
19
+
20
+ This project is configured for deployment via [AWS Amplify](https://aws.amazon.com/amplify/).
21
+
22
+ For important Amplify-specific topics — including email sender verification for SES — see [docs/amplify.md](./docs/amplify.md).
23
+ `;
24
+ if (fs.existsSync(readmePath)) {
25
+ const existing = fs.readFileSync(readmePath, 'utf8');
26
+ if (!existing.includes('## Amplify Deployments')) {
27
+ fs.appendFileSync(readmePath, amplifySection);
28
+ console.log("Appended Amplify Deployments section to README.md.");
29
+ }
30
+ } else {
31
+ fs.writeFileSync(readmePath, `# My App\n${amplifySection}`);
32
+ console.log("Created README.md with Amplify Deployments section.");
33
+ }
34
+
10
35
  console.log(`
11
36
  Amplify configuration written. Your next steps:
12
37
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-wirejs-deploy-amplify-basic",
3
- "version": "1.0.165",
3
+ "version": "1.0.166",
4
4
  "description": "Initializes very basic Amplify deployment configuration.",
5
5
  "author": "Jon Wire",
6
6
  "license": "MIT",