3 ms·
The only problem with that point of view is that with containerizing it, and saying, oh you don't have to bring in Ruby, just use Docker, is that you are almost
by indigodaddy 8y ago
The only problem with that point of view is that with containerizing it, and saying, oh you don't have to bring in Ruby, just use Docker, is that you are almost black-boxing it in a way.
The user does hardly any config, really has no idea how it works, which could make diagnosing and troubleshooting issues that crop up problematic.
- h1d 8y agoThe exact reason to use container is so that individual deployment doesn't get that random problem you're trying to bring up. If container deployments have problems, you take it to the upstream because it will likely to be affecting many.