All the times I just put docker-compose.yml to one user (my user) directory and call it a day.
But what about a service with multiple admins or with more horizontally split up load?
All the times I just put docker-compose.yml to one user (my user) directory and call it a day.
But what about a service with multiple admins or with more horizontally split up load?
Env variables get saved to 1Password (self hosted alternative would be Infisical) with a project for each container.
Docker compose files get synced up to my GitHub account.
I have been using the new “include” attribute to split up each container into its own docker compose file.
Usually I organize by service type: media
Not sure if that answers the question…
Can we get a link to your gh
I do similliarly, but my question was about the situation when there are more admins with access to server. Would you create one account for everything or how else to manage it?