在Drupal / CMS项目上使用版本控制 [英] Working with version control on a Drupal/CMS project

问题描述

我想知道使用Drupal（或任何其他CMS）开发网站的团队如何将版本控制，子版本，git或类似程序集成到其工作流程中。您显然希望您的自定义代码和主题文件受版本控制，但是当您使用诸如Drupal之类的CMS时，很多工作包括配置所有这些存储在数据库中的模块和设置。

I was wondering how teams that develop sites using Drupal (or any other CMS) integrate version control, subversion, git or similar, into their workflow. You'd obviously want your custom code and theme files under version control but when you use a CMS such as Drupal a lot of the work consists of configuring modules and settings all of which is stored in the database.

所以当你是一个开发团队的时候，你如何协调这样的项目？将数据库转储到文件中并将该文件放置在版本控制下可能会有效我可以，但是当网站正在生效时，客户端会不断添加内容，使同步有一些问题。

So when you are a team of developers, how do you collaborate on a project like this? Dumping the database into a file and putting that file under version control might work I guess, but when the site is live the client is constantly adding content which makes syncing a bit problematic.

我很想知道别人在做什么。

I'd love to know how others are doing this.

推荐答案

你是正确的，这是Drupal- -version控制工作正常，直到您将站点转移到您的客户端或将其打开给用户。

You are correct that this is an issue for Drupal--version control works fine until you turn the site over to your client or open it up to users.

您的问题似乎是这个一个，其中涉及到Drupal工作流程中的版本控制。您可能会在那里找到一些有帮助的答案。

Your question seems like a more specific version of this one, which touched on version control in the Drupal workflow. You may find some answers there that help.

对于某些项目，我已将所有视图导出为代码，使用Views模块的功能，并且我有一个所有的块都已经出口的项目，以及。 （虽然这是一个开发工作，而不是与块有关的习惯）。

For some projects, I have exported all of the views to code, using that feature of the Views module, and I have one project where all of the blocks have been exported, as well. (Although that was a development exercise and not a customary thing to do with blocks.)

看看开发种子正在解决这个问题。他们正在领导上下文，功能和空间模块工作一起将配置数据存储在模块中（DB外），以便可以使用代码进行版本控制。

Take a look at the work that Development Seed is doing to work around this problem. They are leading the development of the Context, Features, and Spaces modules that work together to store configuration data in modules (outside of the DB) so that it can be versioned with the code.

有一个名为 Packaging&部署，讨论正在为此问题开发的各种解决方案。

There is a Drupal group called Packaging & Deployment for discussing the various solutions that are being developed for this issue.

这篇关于在Drupal / CMS项目上使用版本控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！