Create Seperate Dev and Prod environments

The Swish backend (and later frontend) will require a logical (or virtual) separation between production data. To do so, all services used must be namespaced into separate environments.

Algolia: Algolia supports separate indices. One index will be made for each environment, and upon startup, the application will specify a different index ID depending on the loaded environment.

2 indices: dev_swish, prod_swish

Mux: Mux supports separate "environments". Mux environments act as separate namespaces for all their video resources. One Mux environment will be made for each environment, and upon startup, the application will choose the correct API credentials depending on the loaded environment. This also means there will be different webhook secrets, so 2 event pipelines are needed.

2 environments: Development, Production
2 google functions: dev-muxWebhookPortal, prod-muxWebhookPortal
2 PubSub topics: dev-mux-events, prod-mux-events
2 PubSub subscribers (1 for each topic): dev-swish-api, prod-swish-api

CDN: Google Cloud Storage has separate buckets. One bucket will be made for each environment, and upon startup, the application will choose the correct bucket ID depending on the loaded environment.

2 buckets: dev-swish, prod-swish

Database: While Google Firestore does not support any native namespacing, I can create my own by prefixing. Collections will be prefixed so the application can choose where to look for resources depending on the execution environment.

2 prefixes: dev, prod

(From GitLab)

shetaye / swish

Create Seperate Dev and Prod environments #25