部署开发环境
One of the things we have discovered while supporting Perch, is that many of the issues that come into support don’t have much to do with our software, and instead stem from development and deployment practices. Customers will develop sites in a way that doesn’t match the live environment, so on going live they are left patching up issues on the live site. Or they will deploy piecemeal using FTP, and find things break due to a core file failing to transfer.
我们在支持Perch时发现的一件事是,支持中涉及的许多问题与我们的软件无关,而是源于开发和部署实践。 客户将以与实时环境不匹配的方式开发站点,因此在上线时,他们会在实时站点上修补问题。 否则他们将使用FTP零散部署,并发现由于核心文件传输失败而导致事情中断。
At Smashing Conference in LA, I ran through the ways in which people could create solid development environments that did match or at least come close to production. I then went on to explain how to use third party deployment services to deploy code to live. Smashing have published all of the videos from the conference so you can watch the talk. Slides and resources are here.
在洛杉矶的Smashing Conference上,我讲解了人们可以创建确实匹配或至少接近生产环境的可靠开发环境的方法。 然后,我继续解释了如何使用第三方部署服务来部署代码。 Smashing已发布了会议中的所有视频,因此您可以观看演讲。 幻灯片和资源在这里。
更进一步 (Taking it a step further)
At Future Insights Live I also spoke about Vagrant as part of my talk on Configuration Management with Puppet for Developers. This more technical talk covered some of the interesting things we do with Puppet – both in development VMs and production. Take a look at the slides and additional resources and I’ll be speaking on the same subject at Future of Web Apps in London later this year.
在Future Insights Live中,我还谈到了Vagrant,这是我与Puppet for Developers进行配置管理的演讲的一部分。 这次技术性演讲涵盖了我们在开发VM和生产中使用Puppet所做的一些有趣的事情。 看一下幻灯片和其他资源 ,我将在今年晚些时候在伦敦的Web Apps的未来主题上发表演讲。
部署开发环境