0

Currently i have my central repo (origin repo) on a Bonobo Git Server.

I have followed those steps to use Acquia Cloud with a remote repository.

On my Acquia cloud repo i installed Drupal 8.

  • also i already cloned my origin repo (Bonobo Git Server) locally to my computer.

Now i think the best workflow is to clone the Acquia Cloud repo locally isn’t it? With the whole Drupal 8 core and all files from the Drupal 8 installation.

So after that i can add contributed modules and themes to my local repo and commit and push them to my origin repo (Bonobo Git Server) and the Acquia Cloud repo?

  1. Is this the a correct workflow? And how do i get all the Drupal 8
    files from Acquia Cloud to my local repo?
  2. i have read also something about 'Translating your root directory with git subtree' in this article. Is this correct and what do i have to do exactly regarding my workflow
  3. Is it advisable to use Acquia dev desktop also?
1

Disclaimer: I work for Acquia

This library article you linked to originates from an blog post that was written 4 years ago to answer questions about deploying from Jenkins build servers, private Github repos, etc. There's nothing specific to Acquia Cloud per se and it's rather a Git strategy you need to come up with for your development needs.

Is the Bonobo Git Server going to be the 'origin' going forward?

  • If yes, then simply add the Acquia Cloud as a new remote (e.g. 'ac'). Git allows you to push to different remotes without any issue.
  • If not, then you should make Acquia Cloud the 'origin' and Bonobo a regular remote (probably easier).

Since Git is decentralized, you 'own' the repo at any point in time and the main reason for keeping a remote is if you have a continuous integration system you need to pass your codebase through before you deploy code to Acquia Cloud. Another good reason is if you have a preferred Git workflow (think Github pull requests for instance) you wish to continue working with. But if you simply want to mirror your Acquia Cloud repo to (for instance) back it up, then I'd argue to just keep the Acquia Cloud repo and simplify your workflow.

The idea to keep in mind is you need only one checkout of your codebase. Having several remotes allows you to handle where to push to as described in the article.

  • thanks a lot. What do you mean exactly with 'Is the Bonobo Git Server going to be the 'origin' going forward?' and the Bonobo server is setup by my client because he has also commit code to it. I think i want to use Acquia cloud to have a staging environment which is visible for everyone and maybe we want to host the live website at Acquia to benefit of stage > production environment. Is that the best setup of workflow? – meez Feb 27 '16 at 7:09
  • So the only fixed values are: the Bonobo Git Server (setup by my client), where my client also can commit code and i need a staging environment and a live environment. – meez Feb 27 '16 at 8:26
  • sorry but do you have an answer on above, so i can continue setup my workflow and use Acquia Cloud. I installed Drupal 8 on Acquia Cloud already. How do i have to continue? How do i get this Drupal 8 core code in my local repo and the Bonobo server? And from that point i can add contributed modules and themes to my local repo isn't it? – meez Feb 29 '16 at 8:44
  • I understand using the Bonobo server isn't really a preference but a requirement from your client. In that case, it needs to stay the default / preferred remote Git server and you could push both to it and to Acquia Cloud by having several git remotes (git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes). This workflow is quite typical. You can use Dev to mirror the Bonobo (e.g. with branch master), then push to Stage for QA (creates a git tag) or have another branch, and finally push to Prod (creates a new tag) for the live site. – anavarre Feb 29 '16 at 9:26
  • 1) what should you suggest and what should be your preferred workflow/best workflow? Show me also your workflow without the Bonobo server. 2) If i keep my current workflow (with Bonobo server and Acquia Cloud like i now have, how do i somehow merge Drupal 8 core files from Acquia Cloud to my local repo? – meez Feb 29 '16 at 10:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.