Each team must deploy their completed software applications to a Digital Ocean Droplet.
- Each project must include a functioning Continuous Integration workflow, where Circle CI or similar hosted continuous integration server, runs a build and test cycle every time a branch is pushed to GitHub or a new pull request is issued.
- Credentials for logging into databases, APIs, or other remote services, must never be shared in version control. They are usually stored in private settings files, such as
.envor similar, which are not included in the version control repository. And so the continuous integration server will not have access to them when testing. Use Circle CI's or other similar server's method of setting environmental variables for passing such credentials safely to the CI server. - Each project must deploy their application front-and-back-ends to a single Digital Ocean Droplet - sign up for Digital Ocean using this referral link to receive $100 of credit (full disclosure, I would receive $25 of credit for anyone who winds up spending $25 on Digital Ocean, but there is no need for you to spend anything since the $100 credit will easily get you through the course).
- Submit a link to your front-end code live on the web, and include that link on your README.md document.
Include a note when submitting, if you have done any of the extra credit.
- Extra credit is given to teams that have deployed to a Docker container, although a non-containerized deployment to a Droplet is fine.
- Extra credit is given to teams that have a Continuous Deployment setup, although a manual deployment is fine.
Individuals will be graded, in part, according to...
- individual code contributions, as visible through git logs - make sure you commit your own work!
- proper adherence to the Feature Branch git workflow
- the quality of the work
- the proper setup and use of a Sprint Task Board to indicate the Sprint Backlog and accurate status of all of their work at all times during the Sprint