Skip to content

Commit 12b0ac5

Browse files
committed
updated readme
1 parent 62a881f commit 12b0ac5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -137,11 +137,11 @@ Start the Azure Static Web App server (in the root folder):
137137
swa start --api ./api
138138
```
139139

140-
You can now work locally.
140+
Enjoy the Static Web Site running locally!
141141

142142
## Running on Azure
143143

144-
This is the amazing part of using Azure Static WebApps. Deploying to Azure is completely automated via GitHub actions.
144+
This is the amazing part of using Azure Static Web Apps. Deploying to Azure is completely automated via GitHub actions. There are some manual steps because the Static Web Apps CLI is still in Preview at the moment of writing and because Prisma and the Azure Static Web App GitHub Action need some help the get along.
145145

146146
1. Fork this repository
147147
1. Get a [GitHub Token](https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line)
@@ -152,7 +152,7 @@ This is the amazing part of using Azure Static WebApps. Deploying to Azure is co
152152

153153
## Fixing generated workflow file
154154

155-
The generated workflow file will not work. Even if the CI/CD pipeline will complete successfully, the Azure Static Web App will not work. This is due to how Onyx, the tool the automate the building and the deployment for Static Web Apps, doesn't now how to properly deal with the nuances of Prisma, that generates the client right away. Fixing this issue is quite easy, just add the following enviroment variable to the workflow.
155+
The generated workflow file will not work. Even if the CI/CD pipeline will complete successfully, the Azure Static Web App will not work. This is due to how [Oryx](https://github.com/Microsoft/Oryx), the tool the automate the building and the deployment for Static Web Apps, doesn't now how to properly deal with the nuances of Prisma, that generates the client right away. Fixing this issue is quite easy, just add the following enviroment variable to the workflow.
156156

157157
The workflow file you have to change is in `./github/workflow` and in the name has the name retured by the deployment script. For example if the deployment script reported that:
158158

0 commit comments

Comments
 (0)