...

The members are divided into 5 teams: frontend-appmobile, frontend-web, backend-online, backend-offline, infra

Workflow	User	Interface (frontend)	API (backend)	database
Online	e.g. Parents uploading data/photo	app (iOS, Android)	APIs	Database named "BioHPC"
		(by frontend-app mobile team)	(by backend-online team)

Offline	e.g. Scientists view data	web (React)	APIs	Should also be on "BioHPC"
		(by frontend-web team)	(by backend-offline team)

...

In one word, infra team underlies all other teams.

Workflows

Now having a rough idea about each team's role, let's understand how their code is interacting with each other (workflows).

To understand the workflows, from the link below, read the the last diagram in the bottom

Codebases (GitHub)

You can find a list of all codebases on GitHub for each team at this link.

After cloning your codebase from GitHub, now it's time to write/debug code.

Probably you won't yet have every required library installed, but worry not! We use docker container to standardise everything (versions/libraries).

In one word, you'll find it more convenient and elegant to write/debug code in env docker container (instead of on your laptop's local env).

Read the doc below to know how.

Coding itself is not rewarding, and you probably do want to see your code working.

After reading the previous docs "How do I write/debug code?", you will be able to run code locally (i.e. in dev env).

Now let's see more exciting options of running them in test env and prod env!