使用 Git 进行开发的网页设计机构
背景
到目前为止，我们一直使用 Plastic SCM 进行版本控制。最近我们一直在研究 Git，我提出了一个基本计划 - 可在 Google 文档上找到
我的计划是不允许开发者提交或FTP 直接到服务器，相反，我们会将工作推送到实时或验证中心，然后这将导致实时/验证工作区从各自的中心提取更改。
在我看来，这种方法的主要好处之一是我们可以及时了解用户上传的内容。例如，当用户通过我们的 CMS 上传图像时，下次开发人员将某些工作推送到中心时，服务器会自动添加、提交并将其推送到中心。因此，我们可以随时将实时存储库或证明存储库克隆到全新的服务器。
到目前为止，我们在将工作发送给客户端进行验证的同时将新功能上传到实时服务器时遇到了问题 - 验证工作最终会出现在实时站点上，所有的破坏都会失败。
问题
- 您发现这个计划有什么漏洞吗？
- Git 适合这种结构吗？
- 是否有我们可以使用的现有计划？
提前致谢。
Background
Up until now we've been using Plastic SCM for version control. Recently we've been looking into Git and I've come up with a basic plan - Available here on Google Docs
My plan is to not allow developers to commit or FTP directly to the server, instead we would push our work to either the live or proof hub which would then in turn cause the live / proof workspaces to pull the changes from their respective hub.
One of the main benefits of this methodology in my eyes is that we can keep up to date with user-uploaded content. For example, when a user uploads an image via our CMS the server will automatically add, commit and push it to the hub the next time a developer pushes some work to the hub. Therefore at any time we can clone either the live or proof repository to a brand new server.
Up until now we've had problems sending work to a client to proof whilst simultaneously uploading new functionality to the live server - the proof work ends up on the live site and all hell breaks lose.
Questions
- Do you see any holes in this plan?
- Is Git the right thing to use for this kind of structure?
- Is there a pre-existing plan that we could use instead?
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看看 Heroku 和 AppHarbour 是如何工作的。您绝对走在正确的道路上。
Take a look at how Heroku and AppHarbour work. You are definitely on the right track.
您应该考虑使用 Gerrit - 代码审查引擎，它也恰好是完全兼容 git 的 git 服务器。 Gerrit 是 Google 针对 Android 项目需求用 Java 编写的。
您可以使用审核功能让内容“融入”审批队列，直到最终获得批准并成为正式内容（或再次被拒绝/审核）。同时，你可以为不同的人设置灵活的访问权限规则——比如某人可以绕过代码审查直接推送（这样就变成标准的git服务器），或者只能提交审查，或者批准，或者只投票或向下 - 您设定规则。如果您有多个 git 存储库，您还可以限制您不信任的用户或第三方对某些高度机密的存储库的访问。
它易于设置，并且使管理员和最终用户的生活变得更加轻松 - Gerrit Web 界面上自动提供 ssh 密钥管理。
You should consider using Gerrit - code review engine that also happens to be fully git-compliant git server. Gerrit is written in Java by Google for Android project needs.
You can use review functionality to let content "bake in" in approval queue until it finally gets approved and becomes official (or rejected/reviewed again). At the same time, you can set flexible access permission rules for different people - like somebody can push directly bypassing code review (in which case it becomes just standard git server), or can only submit for review, or approve, or only vote up or down - you set the rules. In case you have multiple git repositories, you can also restrict access to some highly secret repositories from users you do not trust or from 3rd parties.
It is easy to set up, and makes life much easier for admins and for end users as well - ssh key management is automatically provided on Gerrit web interface.