Skip to content
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.

Dev Env, Test Infrastructure, & Production Setup
Compare
Choose a tag to compare
@WeiTao3 WeiTao3 released this 08 Nov 01:22
· 108 commits to master since this release
v1.0.1
164626d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Overview of this release

  • set up developer environments, including a bootstrap script, service.yml file

  • set up CI and CD Systems

  • set up Sentry for exception tracking

  • set up Sumologic for logging

  • deploy the website to Heroku

  • Update the roadmap, Stack Decisions, and Architecture diagram

Links to deployed frontend and backend

Links to all submitted files/related Dev Env

Issue summary

  • #1
    • Created by: Zuoyu Wang
    • Approved by: Wei Tao & Qiming (Austin) Ye
  • #2
    • Created by: Zuoyu Wang
    • Approved by: Wei Tao & Qiming (Austin) Ye
  • #8
    • Created by: dcsil-team-app
    • Approved by: Zuoyu Wang

A paragraph explaining the progress your team has made, and contents of this assignment

For now, we have switched our backend language from Django to Flask due to the compatibility and convenience with MongoDB database. We have finished setting up bootstrap for installing dependencies, any languages required, and any packages required. We also set up a CI/CD system for automatic testing and deployment. Sentry for exception tracking and Sumologic for logging are also setup successfully. We deployed our HelloWorld website to Heroku successfully.

Summaries of issues made by your team since last release

Since last release, we have closed issue of #14 in InfluCo repository, and closed issue of #1 in website_development repository.

Summaries of changes to your roadmap, architecture, or use cases

Consider about the compatibility with MongoDB database, we have changed our Architecture Diagram in term of the chosen backend language. We have switched our backend language from Django to Flask. It will be convenient for us to implement backend in the future, and probably avoid the unpredictable difficulties and problems. We have updated the roadmap, and closed a finished issue #14 which is regarding the CI setup.

Assets 2
Loading