4 ms·
Just rebuild your container each time you change one bit. And get gitlab-ci to redeploy it automatically to a kubernetes cluster each time it changes.
by zoobab 8y ago
Just rebuild your container each time you change one bit.
And get gitlab-ci to redeploy it automatically to a kubernetes cluster each time it changes.
- gexla 8y agoThis is what I was going to post before zoobab beat me to it. I'm not a guru with Docker, but this is what I would do. Make use of automation and just rebuild as much as needed. Shared volumes are good for development though.
- zoobab 8y agoSome tips: put the content that changes at the end of your Dockerfile so that you use caching at maximum. It also helps to only push the layers that have changed.
- Kovah 8y agoThis wouldn't work as content is also changed while the site is running. That means content is changed inside the container but won't be pushed everywhere then so the next build would override the changes made.
- gexla 8y agoI think you have to fight pretty hard to justify using Docker. If you don't know why you would need it or how you would use it, then it's possible that you aren't ready for it yet. Keep in mind that development Docker and production Docker are two different worlds. There are things which Docker brings to the table in both worlds and the way you use it is different in both. It's quite possible that it's really helpful for development but not yet needed for production. In your case, you would probably be better off outsourcing the plumbing of your hosting to a service such as Netlify or Heroku. If you still have questions, a better place to check would be one of the StackExchange sites. Post your question there or find a similar question which has already been answered.
- Kovah 8y agoUnfortunately, it was neither my decision to use that CMS nor to use Docker for deployments. But thank you for the input.