Skip to content

Commit c9cda1a

Browse files
committed
Update configuration.mdx
1 parent 4fbfa26 commit c9cda1a

File tree

1 file changed

+3
-20
lines changed

1 file changed

+3
-20
lines changed

content/docs/configuration.mdx

Lines changed: 3 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -105,28 +105,11 @@ npx add-in db-identity
105105

106106
### App Settings Secrets
107107

108-
You could register any App-specific secrets here, although our preference is to instead save all your secrets in a single `APPSETTINGS_JSON` GitHub Action Secret which will get written inside the Docker container `appsettings.Production.json`, e.g:
108+
Instead of polluting each GitHub Repository with multiple App-specific GitHub Action Secrets, all templates includes built-in support in its GitHub Action workflows for updating an App's entire `appsettings.Production.json` inside a single `APPSETTINGS_JSON` GitHub Action Secret.
109109

110-
```json
111-
{
112-
"ConnectionStrings": {
113-
"DefaultConnection": "Server=service-postgres;Port=5432;User Id=dbuser;Password=dbpass;Database=dbname;Pooling=true;"
114-
},
115-
"SmtpConfig": {
116-
"UserName": "SmtpUser",
117-
"Password": "SmtpPass",
118-
"Host": "email-smtp.us-east-1.amazonaws.com",
119-
"Port": 587,
120-
"From": "[email protected]",
121-
"FromName": "MyApp",
122-
123-
}
124-
},
125-
126-
}
127-
```
110+
### Workflow: Development to Production
128111

129-
After changing `appsettings.Production.json` update your `APPSETTINGS_JSON` GitHub Action Secret with:
112+
Run the `secret:prod` npm script to securely store your production configuration in GitHub Actions:
130113

131114
```bash
132115
npm run secret:prod

0 commit comments

Comments
 (0)