有没有好的策略来管理 Drupal 站点的多个克隆？
我有一个 Drupal 站点的主副本，我为每个客户创建一个副本，然后将客户的品牌标识应用到主题和模板，以便每个站点看起来与其他站点不同，但它们的行为方式几乎相同。
现在可能会发生两件事：
1.客户端请求新功能。
如果该功能通常也适用于其他客户端，我想将其合并到主副本中。如果该功能仅对该客户端有用，则该功能将保留在克隆中。
2.主副本实现了一项新功能，需要将其推广到所有克隆。
随着时间的推移，每个克隆都有不同的增长，我如何将该功能应用到主副本克隆而不干扰每个克隆中的现有内容和功能？我使用该功能模块，但我必须长时间进入每个克隆才能启用该功能，这很痛苦。
当涉及到 Drupal 的这种情况时，这是非常棘手的，因为有些设置在文件中，有些设置在数据库中。我使用 Drupal 6.x，这是持续时间最长的痛苦。 SVN 有很多帮助，但仅限于文件离开。
有人遇到过好的策略吗？
I have a master copy of a Drupal site and for each client I create a copy and then apply the client's branding identity to the theme and template so that each site looks different from the others but they pretty much behave in the same way.
Now two things can happen:
1.A client requests a new feature.
If the feature is also usually to other client, I would like to merge it to the master copy. If the feature is only useful for that client, it stays with the clone.
2.A new feature is implemented to the master copy and needs to be rolled out to all clones.
Overtime each clone has grown differently, how can I apply the feature to the clone without interfering the existing content and feature in each clone? I use the feature module but it's a pain that I have to long into every clone to enable the feature.
It's very tricky when it come to situations like this with Drupal for some settings are in file, some are in the database. I use Drupal 6.x and this has been the longest lasting pain. SVN helps a lot but only in the file leave.
Has anybody come across a good strategy?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
基本上：
站点全部包含所有站点（CCK、视图）通用的模块和主题。站点将继承对它们的访问权限。如果您需要使用较新版本的 CCK，您可以将其放在 site1.com/modules 中，运行 update.php，然后就可以开始了。如果客户想要特定于站点的新功能，请编写模块，并将其放入站点文件夹中。没有其他站点看到它，并且只有该站点运行该代码。
对于配置，功能和 Strongarm 可以让您导出站点功能，理论上您可以将其放入站点/所有/模块中，并且所有站点都可以访问该新功能。
Basically:
Sites all contains modules and themes that are common through all your sites (CCK, Views). Sites will inherit access to them. If you need to use a newer version of CCK, you could put that in site1.com / modules, run update.php, and be good to go. If a client wants a new feature that is site-specific, write the module, drop it in the site folder. No other site sees it, and only that site runs that code.
For configuration, there is Features and Strongarm that let you export site features, which theoretically you could drop into sites/all/modules and all sites would have access to that new feature.
几点想法：
drush 是您推出功能的朋友
查看 http: //aegirproject.org，它也可能成为您的朋友
Few thoughts:
drush is your friend for features rollouts
check out http://aegirproject.org, it may also become your friend