4 ms·
[1] You've basically listed the very reason I'm using docker. It makes my code deployment agnostic. Bash "setup" files? been there. I write Dockerfiles. I thin
by avip 7y ago
[1] You've basically listed the very reason I'm using docker. It makes my code deployment agnostic. Bash "setup" files? been there. I write Dockerfiles.
I think that's the only thing I'm strongly opinionated about as a developer.
--- EDIT
This is a classic. Reading the backend "how to run" guide I see:
DATABASE=<your-mongodb-connection-string>
PORT=5000
SERVER_URL=http://localhost:5000
This should settle any debate about docker being "overkill". Developers are notoriously reluctant to install things on their dev machines. As-is this repo has non-trivial setup friction which will reduce # of potential users/testers.
TL;DR: docker-compose up
- dvt 7y agoLike I mentioned, I have laptops that can't even run Docker. I've had to fix CMOS/BIOS settings to be able to run Docker on my main dev box. Also, running Docker can sometimes mean not being able to run VMWare (due to virtualization settings). Not to mention that version controlling Docker repos is a huge pain in the butt, we've had to call our dev ops guy in the middle of the night because some random dependency changed some version that broke something down the line. Pretending that using Docker is as easy as "docker-compose up" is either disingenuous, or you simply haven't used Docker as much as I have. Either way, I still contend that Dockerfiles have no room in a source code repository.
- avip 7y agoI'm in agreement with you that docker on windows is less enjoyable an experience. btw enabling VT-x is required for other tools as well (Android Studio for device emulation).
- jtchang 7y agoWhat would you recommend then? Dockerfiles are super useful in a source code repository and has saved me a ton of time.