FT Edit: Access on iOS and web
人 民 网 版 权 所 有 ，未 经 书 面 授 权 禁 止 使 用
，详情可参考爱思助手
https://www.businessreport.com/newsletters/lapolitics-roedel-parsons-disbands-members-launch-pelican-state
These days I prefer to do the building of containers myself. Creating an OCI image as an artifact gives me flexibility over where things run and opens up all kinds of options. Today it might be a simple docker-compose stack on a single VPS, tomorrow it could be scaled out across a Kubernetes cluster via a Helm chart or operator. The container part is straight-foward as Rails creates a Dockerfile in each new application which is pretty much prod-ready. I usually tweak it slightly by adopting a “meta” container approach where I move some of the stuff that changes infrequently like installing gems, running apt-get and so on into an image that the main Dockerfile uses as a base.