Milestone 3A, 3B, and (some of) 4

[spaykel]

Developer: Sammy Paykel

Closes #110, #134, #168

Pull Request Summary

My Milestone 3A pull request is still pending, so I'm adding on some work for 3B and 4 to this pull request here. Milestone 4 is still a work in progress, so I appreciate your understanding as I try to fix up my site. Thanks guys for all the help this quarter with teaching us, and I'll continue working to get my website fully functional soon!

Special Instructions (optional)

Pull Request Checklist

• Code is neat, readable, and works
• Comments are appropriate
• The commit messages follows our guidelines
• The developer name is specified
• The summary is completed
• Ask for a review in communication channels

Screenshots/Screencast

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	MongoDB Credentials	57d25f9	milestone3b/.env	View secret
-	MongoDB Credentials	7b712ba	milestone3a/.env	View secret
-	MongoDB Credentials	57d25f9	milestone2/.env	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[VasPug]

Sounds good. Your code looks great!