3 ms·

CMD ["bin/run-dev.sh"] comes from official Dokku docs, https://github.com/dokku/dokku/blob/master/docs/deployment/methods/dockerfiles.md https://github.com/dok

by pawurb 8y ago

CMD ["bin/run-dev.sh"] comes from official Dokku docs, https://github.com/dokku/dokku/blob/master/docs/deployment/methods/dockerfiles.md https://github.com/dokku/dokku/blob/master/docs/deployment/m... I don't think it has anything to do with running in dev environment only.

yebyen 8y ago
Well that's fine, I don't know who uses Dokku in production... I think it's granted that it is a solution for development. My point is that for Windows users, for example, they might be using containers to do their development because the host environment is unsuitable for running Ruby in. This is not a hypothetical situation. I work in a setting with mixed developers (some using Windows, some using Mac) and the Windows developers need a Virtual Machine or Container in order to run Ruby in. I use a Mac. If I gave them multi-stage containers which had jettisoned a stage and now had no C compilers, they would be stumped the first time they tried running 'bundle update'. And running 'bundle update' is the (only) prescribed way to get new gem versions into your Gemfile.lock, so... back to where we started. Are you sure this is a strategy for Ruby devs using Dokku? (edit: I am shocked to see the number of users who reported that Dokku was for use in production in their orgs here... https://github.com/dokku/dokku/issues/1878 https://github.com/dokku/dokku/issues/1878)
- yebyen 8y ago
  > If you need Node to compile your web assets but don't need it in production, your final container doesn't need to have Node OK, I'm coming around. You could drop node and C compilers from your image, shedding a lot of weight. This still seems like something I'd really only want to do in production. (In a development setting, I'd like my team to be able to break into the containers and execute arbitrary commands. We should be able to, for example, "bundle update" or "assets precompile" without having a need for another separate environment to do those things. But in production, I don't want anyone running arbitrary commands or making "configuration drifts" inside of my running containers. They should be homogenous.)

by pawurb 8y ago

yebyen 8y ago

Well that's fine, I don't know who uses Dokku in production... I think it's granted that it is a solution for development. My point is that for Windows users, for example, they might be using containers to do their development because the host environment is unsuitable for running Ruby in. This is not a hypothetical situation. I work in a setting with mixed developers (some using Windows, some using Mac) and the Windows developers need a Virtual Machine or Container in order to run Ruby in. I use a Mac. If I gave them multi-stage containers which had jettisoned a stage and now had no C compilers, they would be stumped the first time they tried running 'bundle update'. And running 'bundle update' is the (only) prescribed way to get new gem versions into your Gemfile.lock, so... back to where we started. Are you sure this is a strategy for Ruby devs using Dokku? (edit: I am shocked to see the number of users who reported that Dokku was for use in production in their orgs here... https://github.com/dokku/dokku/issues/1878 https://github.com/dokku/dokku/issues/1878)

yebyen 8y ago
> If you need Node to compile your web assets but don't need it in production, your final container doesn't need to have Node OK, I'm coming around. You could drop node and C compilers from your image, shedding a lot of weight. This still seems like something I'd really only want to do in production. (In a development setting, I'd like my team to be able to break into the containers and execute arbitrary commands. We should be able to, for example, "bundle update" or "assets precompile" without having a need for another separate environment to do those things. But in production, I don't want anyone running arbitrary commands or making "configuration drifts" inside of my running containers. They should be homogenous.)