4 ms·
> using a dockerised version of our internal django project is great for loads of reasons It's an internal project? What is the uptime and DR requirements for
by darkarmani 7y ago
> using a dockerised version of our internal django project is great for loads of reasons
It's an internal project? What is the uptime and DR requirements for it?
It might not be worth dockerizing if you don't need to scale out. Is it a traditional project that can just scale to larger machines as needed? Can you just run on multiple static environments for development?
If you are making something that needs to autoscale on kuberneties, do real CI (not just continuous build), etc, then sure.
- dtjohnnyb 7y agoThanks for the input, given the generally negative outlook in the comments on this idea, maybe multiple static environments might solve enough of our issues. For uptime requirements, it's the main tool our company uses to organise and interrogate our scientific output and processes, so it's important it gets more stable. My primary reason for heading towards containerization was the "Hmm, it worked on my machine" reason someone mentioned above and the fact we were using Gitlab for CI meant that dockerizing seemed like a natural step. I'm definitely going to tread more carefully into this domain given all the feedback here, I appreciate all the comments.