Development Environment & Software Architecture
Published in
1 min readMay 3, 2018
Development Environment
Following the “Panduan GIT” on scele we use:
Master as our deployment branch,
sit_uat as our staging or mirror environment of production to test our code in front of product owner and scrum master,
coba_coba as our testing branch when creating a UserStory for each task,
hotfix as our branch to correct bugs in the master branch,
coldfix as our branch to rollback and correct our mistake after sprint review.
Software Architecture
Below is the attached of MeetU deployment diagram.
This diagram explains how each of the services interact, basically consists of 3 parts:
- Android/Frontend services
- Django/Backend services, and
- The Postgres(sit_uat/production)/Sqlite(coba_coba) database.
The difference between master, sit_uat and coba_coba branch is when we build the app uder the coba_coba branch we use localDB instead of PostgreSQLDB when we deploy to sit_uat and master.
