How come you can't seem to get a different .env running in tandem on the same machine using compose?
Docker compose seems to struggle with two separate .envs. No amunt of clearing and removing information undoes it. Very confused how I can't seem to run two separate services after raizing the docker info. Just a bit hard to track.
1. I have one service config. I replaced it.
2. the service config that is used for local deploy doesn't seem to work.
3. the production config still runs on any machine.
4. the original local deploy config always worked before I changed it.
This is concerning because it means I likely will struggle to deploy and work with a polylithic architecture with unique backends/databases. Is there a generalized collection of commands that for sure destroy all infrastructure irreperably?
1 Reply
To follow up. The config and everything has been destroyed as far as I can tell, and I get authentication errors when I attempt to redeploy with different configs.