什么是最好的Drupal部署策略？ [英] What's best Drupal deployment strategy?
问题描述
我正在我的MacBook上进行XAMPP上第一个Drupal项目。这是一个原型，并从我的客户那里获得积极的反馈。
I am working on my first Drupal project on XAMPP in my MacBook. It's a prototype and receives positive feedback from my client.
我将在两个星期后在Linux VPS上部署该项目。有没有比从头开始在服务器上重新做所有事情更好的方法？
I am going to deploy the project on a Linux VPS two weeks later. Is there a better way than 're-do'ing everything on the server from scratch?
- 安装Drupal
- 下载模块（CCK，Views，Date，Calendar）
- 创建内容
- ...
- install Drupal
- download modules (CCK, Views, Date, Calendar)
- create the Contents
- ...
谢谢
推荐答案
几个提示：
-
对文件使用源代码控制，而不是FTP / etc。你用什么都没关系我们倾向于为每个客户端启动一个Unfuddle.com subversion帐户，以便他们也有一个记录错误的地方，但关键的第一步是将您网站的完整源代码树放到版本控制中。当在测试服务器或分段服务器上进行更改时，您会看到它们是否正常工作，然后提交，然后在实时服务器上进行更新。回滚和部署得到很多，更简单。对于多个网页头的群集，您可以从单个规范服务器重复此过程或rsync。
Use source control, NOT FTP/etc., for the files. It doesn't matter what you use; we tend to spin up an Unfuddle.com subversion account for each client so they have a place to log bugs as well, but the critical first step is getting the full source tree of your site into version control. When changes are made on the testing server or staging server, you see if they work, you commit, then you update on the live server. Rollbacks and deployment gets a lot, lot simpler. For clusters of multiple webheads you can repeat the process, or rsync from a single 'canonical' server.
如果您使用SVN，您也可以使用CVS检查Drupal和其他模块/主题和SVN / CVS元数据将能够生活在彼此旁边。
If you use SVN, though, you can also use CVS checkouts of Drupal and other modules/themes and the SVN/CVS metadata will be able to live beside each other happily.
对于庞大的文件夹，如文件目录，在正确位置使用符号链接指向webroot之外的服务器端目录。这可以让您的源代码控制包含所有代码和符号链接，而不是所有代码和用户上传的所有文件。
For bulky folders like the files directory, use a symlink in the 'proper' location to point to a server-side directory outside of the webroot. That lets your source control repo include all the code and a symlink, instead of all the code and all the files users have uploaded.
数据库很棘手;清理开发人员/分期数据库并将其推送到现场是最简单的初步部署，但是如果实时网站上的用户也在生成内容，则在执行增量数据库更新时会出现一些皱纹。
Databases are trickier; cleaning up the dev/staging DB and pushing it to live is easiest for the initial rollout but there are a few wrinkles when doing incremental DB updates if users on the live site are also generating content.
我在 Drupal部署最佳做法去年。随意查看幻灯片。
I did a presentation on Drupal deployment best practices last year. Feel free to check the slides out.
这篇关于什么是最好的Drupal部署策略？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
