Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to use Ansible to synchronize GitHub and GitLab. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Protect access to important projects by using the Ansible mirrored Git repository.

Open source is everywhere. It is on computers at home, in the workplace, on the Internet, and many are managed by Git. Because Git is distributed, many people also see it as a crowdsourced backup solution. In theory, whenever someone clones the Git repository to their local computer, they create a backup of the project's source code. If 100 people do this, the repository has 100 backup copies.

In theory, this can mitigate the impact of a "disaster", such as when project maintainers suddenly decide to delete repositories or inexplicably block all traffic, causing developers to search headless for who has the latest version of the main branch. Similarly, the entire code hosting site will disappear. No one would have thought that Google Code, Microsoft CodePlex or Gitorious would be shut down in their heyday.

In short, if the Internet has taught us anything over the past few decades, it is that relying on the Internet to magically create backups is not the surest way to redundancy.

In addition, for many people, it is a problem that many open source projects are hosted on GitHub-GitHub is not an open platform. Many developers and users want to support and interact with stacks such as GitLab, which has an open source community version.

Use Ansible to manage Git

Git's decentralized approach is useful for solving this problem. With pure Git, you can easily push it to two or more repositories using a push command. However, in order to make it useful in the event of an unexpected failure, you must interact with the Git repository frequently (especially push). In addition, even if you may never push or pull the code yourself, you may have some repositories to back up.

However, with Ansible, you can automatically perform Git pull on the main branch of the project (or any other branch), and then automatically push the Git from the repository to the "off-site" image. In other words, you can have your computer pull and push regularly from GitHub to GitLab or Gitolite or Gitea (or any Git hosting host you like).

Ansible module

Were it not for its excellent collection of modules, Ansible would not be so good. Like Python's third-party libraries or Linux applications, one of the useful and surprisingly simple tricks of this technology engine is that Ansible is known for components contributed by others. Because this article is looking at how to back up the Git repository efficiently and reliably, the modules used here are the Git module and the ini_file module.

First, create a file called mirror.yaml as the screenplay playbook. You can start with name and task entries as you usually do with Ansible. This example adds localhost to the hosts list to run the action play on the controller computer (the computer in front of you now), but in real life, you may run it on a specific host or a group of hosts on the network.

-name: "Mirror a Git repo with Ansible" hosts: localhost tasks:Git pull and clone

If you want to make a backup, you need a copy of the latest code. Obviously, the way to achieve this in the Git repository is to execute git pull. However, pull assumes that the clone already exists, while well-written Ansible actions (Ansible scripts) assume as few as possible. It's best to tell Ansible to clone the repository first.

Add your first task to the script:

-name: "Mirror a Git repo with Ansible" hosts: localhost vars: git_dir: / tmp/soso.git tasks:-name: "Clone the git repo" git: repo: 'https://github.com/ozkl/soso.git' dest:' {{git_dir}} 'clone: yes update: yes

This example uses soso, an open source operating system similar to Unix, as the repository I want to mirror. This is a completely arbitrary choice, which in no way means that I lack confidence in the future of the repository. It also uses variables to reference the target folder / tmp/soso.git, which is convenient, and will benefit if you want to extend it to a generic mirror script in the future. In real life, you may have a more permanent location on your work machine than / tmp, such as / home/gitmirrors/soso.git or / opt/gitmirrors/soso.git.

Run your script:

$ansible-playbook mirror.yaml

When you first run the script, Ansible correctly detects that the Git repository does not exist locally and clones it.

PLAY [Ansible Git mirror] * TASK [Gathering Facts] * ok: [localhost] TASK [Clone git repo] * changed: [localhost] PLAY RECAP * * localhost: ok=2 changed=1 failed=0 [...]

If you run the script again, Ansible will correctly detect no changes since the last run and report that no action has been performed:

Localhost: ok=2 changed=0 failed=0 [...]

Next, you must instruct Ansible to push the repository to another Git server.

Git push

The Git module in Ansible does not provide push functionality, so part of the process is manual. However, before you can push the repository to a standby mirror, you must have a mirror, and you must configure the mirror as a standby remote server remote.

First, you must add an alternate remote server to the Git configuration. Because the Git configuration file is an INI-style configuration, you can easily add the information you need using the ini_file Ansible module. Add this to your script:

-name: "Add alternate remote" ini_file: dest= {{git_dir}} / .git/config section='remote\ "mirrored\" option=url value='git@gitlab.com:example/soso-mirror.git' tags: configuration

To do this, you must have an empty repository (in this case, GitLab.com) on the target server. If you need to create a target repository in your script, follow Steve Ovens's excellent article "how to use Ansible to set up a Git server through SSH."

Finally, push the HEAD directly to the alternate remote server using Git:

-name: "Push the repo to alternate remote" shell: 'git--verbose-- git-dir= {{git_dir}} / .git push mirrored HEAD'

Run the script as usual, and then automate the process so you don't have to run it directly again. You can use variables and specific Git commands to adapt scripts to your needs, but regular pull and push operations ensure that important items that reside on one server can be safely mirrored to another.

This is a complete script for reference:

-name: "Mirror a Git repository with Ansible" hosts: localhost vars: git_dir: / tmp/soso.git tasks:-name: "Clone the Git repo" git: repo: 'https://github.com/ozkl/soso.git' dest:' {{git_dir}} 'clone: yes update: yes-name: "Add alternate remote" ini_file: dest= {{ Git_dir}} / .git/config section='remote\ "mirrored\" option=url value='git@gitlab.com:example/soso-mirror.git' tags: configuration-name: "Push the repo to alternate remote" shell: 'git--verbose-- git-dir= {{git_dir}} / .git push mirrored HEAD' on "how to use Ansible to synchronize GitHub and GitLab" ends here Hope that the above content can be helpful to you, so that you can learn more knowledge, if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.