4 ms·
This is a great point and has bugged me for for the past few months - I'm sat there watching my 'npm install' whir by and I'm thinking - 'I reckon this is not t
by binocarlos 12y ago
This is a great point and has bugged me for for the past few months - I'm sat there watching my 'npm install' whir by and I'm thinking - 'I reckon this is not the "docker way"'
Having said - I'm still trying to work out the combination of source repo and docker repo - i.e. 1 dev makes a code change - they commit the code to github - they then commit the docker image to the registry.
Now - does developer number 2 'git pull' or 'docker pull'
What I really like is how docker does not really enforce anything upon you - leaving the above question to be answered any which way.
Docker ftw!
- jafaku 12y agoI don't think sharing the image is necessary during development. I just add the Dockerfile to the repository and each dev builds their own image. If they are methodical they can pull the repo and rebuild the image at the beginning of their work day. Most times it will be rebuilt in a second because there have been no changes. If they don't rebuild the image, it will be the main suspect as soon as something breaks anyway, so I can't see this causing much trouble.
- quaunaut 12y agoThis is exactly what I do, just using Trusted Builds. Right now one of my biggest curiosities, is doing mass deploys and unified logs. I've not tried to so it hasn't mattered yet, but it could be fun.
- opendais 12y agoPersonally, I git pull and I just have all the important repos [e.g. things with Dockerfiles that people want to be notified if they should rebuild] dump to chatroom notifications so people know they might want to rebuild.