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

问题描述

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

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.)

看看开发种子正在解决这个问题。他们正在领导上下文的发展，功能和 Spaces 模块

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屋！