Each team should be more or less deploying a similar Django architecture in their project.
This should mean that the Travis configuration to build, test and deploy their Django API stack should be similar in layout (if different in the details of repos, bucket names etc).
For those projects now which haven't gotten the backend integrated with Travis, a template to get them started would be helpful.
This is especially true since some projects have had to work around additional details that didn't come up in the class assignments.
Replace the project-specific naming with PLACEHOLDER_TEXT and this could be committed to the devops-17 repo to be re-used by current (and future) seasons' projects.
pdxdiver
commented
7 years ago
Each team should be more or less deploying a similar Django architecture in their project.
This should mean that the Travis configuration to build, test and deploy their Django API stack should be similar in layout (if different in the details of repos, bucket names etc).
For those projects now which haven't gotten the backend integrated with Travis, a template to get them started would be helpful.
This is especially true since some projects have had to work around additional details that didn't come up in the class assignments.
One project with a promising design is Housing: https://github.com/hackoregon/housing-17/blob/master/.travis.yml
Replace the project-specific naming with PLACEHOLDER_TEXT and this could be committed to the devops-17 repo to be re-used by current (and future) seasons' projects.