Comment by kwakubiney
1 month ago
I’m working on a small deployment tool called push2start[1]. The goal is to make Docker Compose apps easier to deploy from a laptop to a remote server without a lot of custom scripts. Right now, I’m trying to keep Compose as the source of truth and avoid creating another mini orchestrator. You point it at a compose file, it transfers only the images that need to come from local, then deploys and gives status, logs, and restart controls from one CLI.
I remember reading that Docker Compose is for development environments only, and should not be used in production. Did that change?
Nope! This is for development purposes only. Say, for example, you have a frontend team that wants to connect to a service, and that service talks to other services to get a response, and you sort of want like a central point of connection for the frontend team just for development purposes only, not for production.