5 ms·
Love Docker Compose. At an old job, we used it to provide every developer with a local version of the frontend, backend and database, all in separate containers
by apozem 3y ago
Love Docker Compose. At an old job, we used it to provide every developer with a local version of the frontend, backend and database, all in separate containers that only talked to each other. All of that with one command!
- salawat 3y ago...that none of them could figure out how to debug. >t. The guy who gets endlessly tired of having to unfsck the layers of abstraction into something mere mortal devs/testers can reason through about.
- giobox 3y agoPeople have been making this facetious argument since Docker launched a decade ago, it's even more ridiculous to make it now. My job would very literally be harder and take much longer to accomplish things without the benefits of containers. Anyone who still feels this way about containers for software dev today needs to get off their grumpy stool and embrace the benefits.
- gnulinux 3y agoThis is the current setup I have at my current day job and it's pretty awesome. Wouldn't change it for anything else.
- dharmab 3y agoI've been use interactive debuggers with Docker since 2017. It's quite easy.
- airza 3y agoFunnily enough I chose docker compose because it was such an easy abstraction. I tell it i want a bunch of containers and specify their network relationship in a simple flat file. I tell it that I want each of them to expose their debugger port on a different local port, then I can just hook up a normal debugger and go. Couldn't be easier!
- jayd16 3y agoI had a similar set up and it made debugging really easy. Instead of building and running every app you could just run the full environment with known good images and replace the app you're working on with the debuggable instance running in the IDE. These days you can even build, and deploy a debuggable image from an IDE easily so you don't need to bridge the network.