Test Azure deployment workflow#7
Merged
Merged
Conversation
ml-evs
had a problem deploying
to
Test deployment
GitHub Actions
Failure
ml-evs
had a problem deploying
to
Test deployment
GitHub Actions
Failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR sets up automated Azure deployments of the app.
Any push made to
Livewill be deployed to the test deployment at https://pascal-notts-test.azurewebsites.net/, and if a deployment to the main server at https://pascal-notts.azurewebsites.net is desired, this can be triggered via aworkflow_dispatchfrom theActionstab by an admin of this repo. We could change this rule slightly in the future to deploy on new releases, if we wish.Brief notes:
Azure doesn't like poetry, and is awkward to configure without direct access to the app dashboard. To get around this, this PR uses poetry to create a
requirements.txtfile that also includes a "." entry for the local code, and bundles this in the zip that is sent to Azure. Azure also expects a file calledapp.pyat the top-level, which it runs with gunicorn directly. It can be configured to look in a different directory, but for now, this PR copies all the required files to the top-level before zipping. I don't think this has any other side effects.