Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

"I'm not a Magnolia International developer. Just let me check out a copy of some_module_version_x"

For this type if users SVN was heaven: Browse the SVN repo on the web browser, find the project and release tag you are interested in, copy the URL and check out the project on the CLI or your favorite SVN tool.

Now with Git, it seems like things have become much more complex. The Git web interface at is not so easy to browse as we were used to. The structure does not seem to be self-explanatory... otherwise there would not have to be a page explaining the structure, right? And what happened to the versions?! In SVN all you needed to do is to click on the "tags" folder and there you had them. Where are they now?

Well, here is a step-by-step guide to check out the STK 2.0.3 (as an example).

  1. Open Magnolia's Gitweb at
  2. Search for "standard-templating-kit" with the search tool at the top of the page. You should get two hits:
    • modules/standard-templating-kit-prototype.git
    • modules/standard-templating-kit.git
  3. Click on the second one (we don't want the prototype). The project summary is loaded.
  4. Copy the anonymous, read-only URL
  5. Go to the command line and change to the directory where you would like to have your copy of the Standard Templating Kit project
  6. Type git clone and paste in the URL. The complete command should like like this:
    git clone
    This will clone the whole git repository for the standard-templating-kit project with all existing versions to your computer. In the case of STK this can take a while...
    (Note: Of course you could do this with a GUI tool as well, but which one do you have...?)
    Now that we have all versions of STK on your computer, how do we get the version we want?
  7. Go back to the project summary on Gitweb and scroll down to the "tags" part. Look for the version tag you are interested in (2.0.3 in our example). If the tag does not show up in the short list, click on "..." at the bottom of the list to reveal the full tag list of this project.
  8. Click on the standard-templating-kit-2.0.3 tag. This will give you the details of this 2.0.3-commit
  9. Copy the commit hash ("2f6f171e8b74e861dd16d0c1240df6c393467682" in our case)
  10. Go back to the command line, change into the standard-templating-kit directory created by our git clone command above and set the clone back to the desired version using the following command:
    git reset --hard 2f6f171e8b74e861dd16d0c1240df6c393467682
    (Note to those with more git experience than me: Is this the best way to do it?)
    Now you should have a perfect copy of Standard Templating Kit 2.0.3.

It's not too hard once you know what you got to do... but compared with SVN I have yet to discover the advantages of Git for this type of user.

  • No labels