We host our development environments on All-Inkl.
In order to set up a new project, go to the staging server’s KAS and create a new sub-account specific for this project only. This enables us to give only specific people SSH access to that environment and is great for allowing external people to deploy code or clone assets for this project. SSH access can be configured in the parent KAS account of the staging server.
An automated project setup repository for Flynt can be found on GitHub.
During development, the remote development server is our source of truth. However, to work on code locally, every developer clones the development database and uploads to her local machine.
TODO: explain workflow, ./run command, and implications for deployment