0

Currently i have a workflow of 2 levels (local<->online), but i would like to have a 3 level workflow by getting a demo server in the middle (local<->demo<->online). I will describe in details how it is set up currently, and what in details i would like to achieve eventually.

What i have now -

  • multiple local repositories of the same project (my PC and colluegues PCs)
  • online site server (where the site is available to public use, me or other devs from the team may push their ready parts of work from their localhost repositories to here, and pull from here, this is a bare repository added to the local ones over origin master, once pushed up online a hook automatically deploys the pushed changes).

What i would like to have -

  • multiple local repositories of the same project (my PC and colluegues PCs)
  • demo server where all devs can push and pull from to their local repositories. There should be automatic deployment. Once tested on demo the project should go up online. ( i am in doubt how to incorporate all this part...)
  • online bare repository where, we push and pull from the demo server repository. If pushed from demo, it should be auto deployed.

What is the best way to organize this kind of workflow?

4

1 回答 1

0

我不确定对你来说真正困难的是什么，因为你似乎已经准备好了所有需要的东西……

您已经完成了最困难的工作：从您的在线仓库自动部署。因此，只需为您的演示存储库进行与在线存储库中相同的设置，然后唯一缺少的步骤就是将演示存储库中的状态发送到在线。

但是由于任何 Git 存储库都只是一个 Git 存储库，因此您可以从中推送或获取，因此无论您是从开发人员框推送到在线存储库，还是从演示存储库推送到在线存储库，都没有区别。如果您对演示存储库应该是裸露的事实感到困惑，那么不要害怕——您也可以从裸露的存储库中推送和获取；唯一在裸仓库中不起作用的命令是那些触及索引和工作树的命令。

你应该关注的是你应该如何在更广泛的意义上使用演示 repo。说，您可以在演示存储库中进行快速修复吗？如果是这样，它们必须由开发人员获取，或者必须先推送到在线仓库，然后再从那里获取......

于 2015-04-30T16:25:20.943 回答