Development, Staging, Production environments

[amaury1093]

Right now we have set up a pretty functional dev environment, and the frontend is pushed to Now on a sort-of production environment. It would be wise to have better-defined environment and deployments.

I believe we need at least 3 environments.

Development

This is pretty straightforward, it's the environment where we code.

Development
Backend	Local machine.
Backend URL	http://localhost:xxxx
Frontend	Local machine.
Frontend URL	http://localhost:xxxx
Auth0 Application	ChronoScio [DEV] bDdG7phORu8x5EXrBa24G7qrXwFYb7FL
Update frequency	On each local re-run.

Staging

I would not recommend pushing directly the master branch of both backend/frontend to production, even if the code is reviewed. Staging serves as this intermediate test environment, where we can put fake data, do whatever we want, and check that everything works as planned. For mappers, it allows them to check the latest version of the website.

Staging
Backend	TBD
Backend URL	TBD
Frontend	Now
Frontend URL	https://chronoscio-staging.now.sh
Auth0 Application	ChronoScio [DEV] bDdG7phORu8x5EXrBa24G7qrXwFYb7FL
Update frequency	On each push to master.

Production

This is the real website, public facing, with the real database. The process to push from staging to production needs to be defined (e.g. every x weeks), but for now we can do manual pushes.

Production
Backend	Liam's personal server
Backend URL	TBD
Frontend	Now
Frontend URL	https://chronoscio.org, which is an alias for https://chronoscio.now.sh
Auth0 Application	ChronoScio, to be created
Update frequency	Manual, we push to production when we decide to push.

Any thoughts?

[quorth0n]

Pretty standard flow, LGTM 👍