Trying to automatically/programmatically replicate #DockerCompose stacks on the same host. E.g. I have an application that requires multiple containers, and I want to replicate the WHOLE application with its own volumes, networks, subdomain, etc. Any pointers on how to do that? #Ansible? Please don't say #Kubernetes.
I am very excited to see a new #DAP debugger client for #Emacs, Dape! I've already tried it with rdbg over #dockercompose, and I was able to connect, retrieve the stack and variables, and use the REPL to step through code.
I've been wanting something like this to exist for a very long time.
Aaand another update done successfully to 4.1.4 to my Mastodon instance. Just updated the docker tag and updated the compose. Thanks to @linuxserver 's mastodon container 🙏 Thank you @team !
But let's say both ServiceA and ServiceB needs a #MySQL server.
Would you rather, add separate MySQL servers to both docker-compose.yml files or create a new MySQL docker-compose service and then connect ServiceA and ServiceB to that MySQL service?
Today I learned that if you setup a Docker Compose environment variable with a date value that is unquoted it is interpreted as a full datetime.
This could be impactful in situations where the value is not meant to be an actual date but some string-ly value. For example, the API version scheme used by AWS.