What best practices git repo for complex dev environment? [closed]

folks!

Our infra consists from 7 services. Each of them has own repo, and builds with different technologies, actually: four python, one JS, two rust projects. All of them are dockerized.

We deploy this services in one docker cluster. For now we have custom deployed scripts for each, and it always grows and has many boilerplates. Also we have common .env with bunch of common secrets, like DB creds, API keys etc. Obviously our docker-compose.yml in each project has 80% common section, like db servises, rabits.

I want to move docker-compose.yml to separate repo, and write scripts for create .env for each project.

Then I can simple make docker compose up [SERVICE...] with particular service for current dev targets.

What the best way to do such routine?

I think about creating dir projects and add it to .gitignore, and then from root repo clone each project to this folder.

Are it is correct? Or may be we have other great options?

Leave a Comment