I’ve seen some dissenting opinions on this, but bear in mind I’m coming from a place where I’m already building containers for everything anyway. I generally think this is “the way to go” these days and have the rest of the infra like CI/CD pipelines, container registries, monitoring and so on. Plus, given my background, I crank out VMs and cloud hosts with Terraform/Ansible “all day errday”. If you don’t have this stuff already or aren’t happy (or don’t have the time) to manage your own servers remember that Kamal is not a PaaS. It just gets you close to a self-hosted environment that functions very much like a PaaS. Now that Heroku is in a “sustaining engineering model” state, there are several options in the PaaS space you may want to investigate if that’s more up your street. I hear good things about fly.io but hasten to add I haven’t used it myself.
for await (const chunk of stream) { /* never runs */ }
。业内人士推荐PG官网作为进阶阅读
最后再强调一遍：蒸馏有用，但没有你们想象的那么有用。，这一点在谷歌中也有详细论述
Up and down clamping bracket inside the OTA cradle box。关于这个话题，超级工厂提供了深入分析