docs: updated env in readme local setup #378
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request updates the deployment documentation to reflect changes in the infrastructure deployment process and clarifies instructions for environment variable setup. The main improvements are updating the Bicep deployment file paths and providing clearer guidance for managing the
.env
file during setup.Deployment process updates:
docs/DeploymentGuide.md
anddocs/LocalDeployment.md
to useinfra/main.bicep
instead of the outdateddeploy/macae-dev.bicep
path, ensuring consistency with the current infrastructure setup. [1] [2]Environment variable setup clarification:
docs/DeploymentGuide.md
on how to update the.env
file with values from Azure App Service environment variables, and noted that if resources are provisioned withazd
, the.env
file is auto-generated and its location can be found usingazd env list
.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information