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: README.md
+15-13Lines changed: 15 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ The production cloud deployment without much activity is $1-$2 per day to run on
30
30
- You must also bring your own production postgres database or you need to add RDS to the SST stack. I use [Digital Ocean managed databases](https://www.digitalocean.com/products/managed-databases-postgresql).
31
31
- Your domain should be set up in Route 53 and you will need the Hosted Zone ID for cloud deployments (not needed for local deployments).
32
32
- IAM user access key/secret [Setup Guide](https://guide.sst.dev/chapters/create-an-iam-user.html) and [Permissions Guide](https://sst.dev/docs/iam-credentials/#iam-permissions)
33
+
- Mailgun Account [Get API Key](https://help.mailgun.com/hc/en-us/articles/203380100-Where-can-I-find-my-API-keys-and-SMTP-credentials)
33
34
34
35
You can do a global find for `chipgpt` (case insensitive) and locate most things that need to be updated with your own project name and description.
35
36
@@ -41,12 +42,12 @@ Log in to AWS SSO:
41
42
npm run sso
42
43
```
43
44
44
-
Copy the `.env` file and populate them. You don't need a development cloud deployment but it supports it if you want a staging server eventually:
45
+
Copy the `.env.example` file and populate them. You don't need a development cloud deployment but it supports it if you want a staging server eventually:
45
46
46
47
```bash
47
-
cp .env .env.local
48
-
cp .env .env.development.local
49
-
cp .env .env.production.local
48
+
cp .env .env.{{username}}
49
+
cp .env .env.development
50
+
cp .env .env.production
50
51
```
51
52
52
53
Install dependencies:
@@ -134,19 +135,20 @@ To get the GitHub action deployment working you will need an IAM user with acces
134
135
- AUTH_SECRET
135
136
- DATABASE_URL
136
137
- AWS_HOSTED_ZONE_ID
138
+
- MAILGUN_API_KEY
137
139
- NEXT_PUBLIC_POSTHOG_KEY (not really a "secret", it could be a variable instead)
138
140
139
141
## Things I intend to add as I add them to my own SaaS:
140
142
141
-
- Add SES email management for production SES access
142
-
- Add a paid account tier (most likely using Stripe as the payment gateway)
143
-
- Add a propper logging utility that works better with AWS CloudWatch.
144
-
- Add Alarms/Alerts for cloud deployments to be proactive about issues.
145
-
- Auto-Generate REST API Documentation.
146
-
- Support for Amazon RDS + Proxy (had trouble getting it working with Sequelize, didn't feel like finding a new ORM)
147
-
- Add proper Sequelize migrations.
148
-
- Update to use the new Cognito UI mode.
149
-
- Switch to the official `@auth/sequelize-adapter` package after [PR #13120](https://github.com/nextauthjs/next-auth/pull/13120) is merged.
143
+
- [x] ~~Add SES email management for production SES access~~ Add Mailgun email for sending emails
144
+
- [ ] Add a paid account tier (most likely using Stripe as the payment gateway)
145
+
- [ ] Add a propper logging utility that works better with AWS CloudWatch.
146
+
- [ ] Add Alarms/Alerts for cloud deployments to be proactive about issues.
147
+
- [ ] Auto-Generate REST API Documentation.
148
+
- [ ] Support for Amazon RDS + Proxy (had trouble getting it working with Sequelize, didn't feel like finding a new ORM)
149
+
- [ ] Add proper Sequelize migrations.
150
+
- [ ] Update to use the new Cognito UI mode.
151
+
- [ ] Switch to the official `@auth/sequelize-adapter` package after [PR #13120](https://github.com/nextauthjs/next-auth/pull/13120) is merged.
0 commit comments