Releases: dcsil/website_development
Software For InfluCo
Overview of this release
-
implement MVP
-
implement the use case of tags/labels search by ranking and filtering
-
implement the use case of influencers browsing and details
-
implement the use case of reviewing history and favourite
-
implement login and register
-
styling the user interfaces
-
write tests for both frontend and backend
-
upload tests to Code Climate
Links to the development repository
Links to deployed frontend and backend
Links to all submitted files/related Dev Env
- database API
- frontend
- frontend components
- frontend tests
- backend server
- backend API
- backend tests
- Code Climate
- demo video
Issue summary
- #11
- Created by: Zuoyu Wang
- #14
- Created by: Zuoyu Wang
- #16
- Created by: Wei Tao
- #18
- Created by: Wei Tao
- #19
- Created by: Wei Tao
- #24
- Created by: Zuoyu Wang
- #29
- Created by: Zuoyu Wang
- #30
- Created by: Zuoyu Wang
- #36
- Created by: Wei Tao
- #38
- Created by: Wei Tao
- #39
- Created by: Wei Tao
- #40
- Created by: Wei Tao
A paragraph explaining the progress your team has made, and contents of this assignment
We have successfully implemented all three use cases of our MVP, three use cases include 'searching by filtering and ranking', 'influencer browing and details', and 'reviewing users' history and favourite'. The tests have covered both frontend and backend. Now the website has successfully launched to Heroku.
Summaries of issues made by your team since last release
Since last release, we have opened several issues regarding different features of frontend. Such as "add like", "remove like", "add history", "clear history", "add login status", "backend test", "backend restapi", "format UI", etc. Those issues have been successfully solved by our teammates.
Summaries of changes to your roadmap, architecture, or use cases
We have slightly modified our user interface regarding the "popular influencers browsing", this user interface used to have a unique page. In this release, we have merge this user interface into "search" user interface. After the user searchs the influencers, he can directly browse the outcomes one by one in the searching page as well as browse the details of influencers in the detail page.
Dev Env, Test Infrastructure, & Production Setup
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
- bootstrap script
- service.yml
- CI/CD
- Sentry (backend)
- Sentry (frontend)
- Sumo logic
- Heroku
- screenshot of dashboard running in Heroku
- screenshot of Sumo logic
- screenshot of Sentry for frontend
- screenshot of Sentry for backend
- screenshot of mongodb
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.