Open clezag opened 2 hours ago
There's a few things to do, to bring this in line with our internal standards, so that we can put it into testing (I'd recommend doing them in this order):
.env
file, we usually keep a .env.example
file in our repos, that serves as an example for the .env
, without any secrets, so that i can be pushed to the repo.docker-compose.yml
which, using the .env
file builds and launches the application locally for developmentinfrastructure
folder, which contains among other things the Dockerfile, ansible scripts, and compose files. You can refer to this (python) or this (js) repo as a starting point. Copy the whole infrastructure folder, and then customize the Dockerfile
for your application, the rest should already be good..github/workflows
folder from here and customize them. Swapping out the project names and setting your own specific .env
variables should be all you needLet me know if you need help with any specific step.