We do currently have some sort of continuous deployment onto a VPS provided to us by UdeM at capstone.cyberjustice.ca. It's currently configured to deploy after the end of a successful Travis build, but with the parallelization, it often fails and is extremely error prone. We've begun investigating standing up a webhook notification server on capstone.cyberjustice.ca that GitHub can push a notification to once a PR is merged, but it has not been flawless either.
Scope of Work
[ ] Task 1
[ ] Task 2
[ ] Task n-1
[ ] Task n
Demo requirement
The user does x
The system does y
n. Rest of a use case of a flow chart
Description
We do currently have some sort of continuous deployment onto a VPS provided to us by UdeM at
capstone.cyberjustice.ca
. It's currently configured to deploy after the end of a successful Travis build, but with the parallelization, it often fails and is extremely error prone. We've begun investigating standing up a webhook notification server oncapstone.cyberjustice.ca
that GitHub can push a notification to once a PR is merged, but it has not been flawless either.Scope of Work
Demo requirement
Acceptance Criteria