Drupal:您使用 SVN 进行网站开发吗?
您在使用 drupal 开发网站时使用 Subversion 吗?
我不是在谈论模块开发,而是网站开发(即添加钩子函数,修改模板文件..等)
谢谢
Do you use Subversion while developing a website with drupal ?
I'm not talking about modules development, but websites development (i.e. adding hook functions, modifying template file.. etc)
thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
是的。
任何正在进行的开发或将随着时间的推移而改变的东西都应该进行版本控制。
即使您只是在做一个非常小的项目,拥有版本历史记录的价值也是无可争议的,并且能够进行更改而不必担心覆盖其他人的更新是无价的。
Yes.
Anything that's got any kind of ongoing development or is going to change over time should be version controlled.
Even if you're just doing a very small project, the value of having a version history is indesputable, and being able to make changes without worrying about overwriting someone else's updates is priceless.
是的,保持 SVN 存储库与本地实例同步是很好的。为此,您可以使用 Eclipse。
Yes, its's good keep a SVN repository synced with your local instance.For that purpose you can use Eclipse.
是的,但我们将在不久的将来转向 git,因为它提供了更好的功能集(分布式 SCM ftw)和更多用于管理代码库的选项(git 子模块、存储、更好的挂钩集成、更好的合并支持、变基等等)更多)。目前,我们的存储库设置如下:
每个分支都是主干存储库(我们在其中进行大部分开发)的
svn 副本
,每个标签都是svn 副本其相应分支的
。core
分支是我们分发到所有具有大学外观和风格的网站的主要发行版,每个子网站都是一个具有特殊模块、自定义主题或任何其他功能的网站。主要发行版的一部分。它使得在 drupal 版本之间移动变得更加容易,但是您偶尔会遇到合并问题。当存储库开始增长时,您还会遇到性能问题,这是迁移到 git 的部分原因。Yes, but we are moving to git in the near future because it offers a better feature set (distributed SCM ftw) and more options for managing our code base (git submodules, stashing, better hook integration, better merging support, rebasing, and so much more). For the time being we've got our repos setup like so:
Each branch is a
svn copy
of the trunk repo (where we do most of our development) and each tag is asvn copy
of it's corresponding branch. Thecore
branch is the primary distro that we distribute to all of our sites that share the university's look and feel, and each subsite is a site with special modules, custom theme, or any other functionality that isn't part of the primary distro. It makes moving between drupal releases a lot easier, but you can start to run into problems merging occasionally. Also you run into performance issues when the repo starts to grow, which is part of the reasoning behind moving to git.是的。版本控制至关重要。 Git、Mercurial 和 Bazaar 等分布式版本控制系统特别好,可以让您立即开始提交,而无需将这些更改推送到中央服务器。
我的 Drupal 工作流程:使用 Mercurial 及其子存储库功能为 1) Drupal + 贡献模块、2) 主题和 3) 自定义模块创建独立存储库。这样,我可以从单个 URL 进行克隆,获取整个项目,并能够独立跟踪每个不同部分的更改。
Yes. Version control is critical. Distributed version control systems such as Git, Mercurial, and Bazaar are particularly nice, and let you start committing immediately, without the need to push those changes to a central server.
My Drupal workflow: use Mercurial and its sub-repositories feature to create independent repositories for 1) Drupal + contributed modules, 2) theme, and 3) custom modules. That way, I can clone from a single URL, get my entire project, and be able to track changes to each distinct piece independently.