vcs-mirrors
A python-only clone of https://github.com/samrocketman/gitlab-mirrors/ with a YAML config file.
Requirements
Python 3.5+ (Debian Stretch+, Ubuntu Xenial+)
virtualenv if you don’t want to mess with System Python
git-remote-bzr https://github.com/felipec/git-remote-bzr for Bazaar support
Features
Mirror different types of source repositories: Bazaar, Git, Subversion. Mirror all into git.
- GitLab mirror adding.
When adding a mirror if the project doesn’t exist in GitLab it will be auto-created.
Set project creation defaults (e.g. issues enabled, wiki enabled, etc.)
- Github mirror adding.
Same as with Gitlab.
mirror anything to Git (not just Gitlab and Github).
Update a single mirror.
Update all known mirrors.
Installation
On Debian
For Bazaar support:
$ apt install git-remote-bzr
Install into a virtualenv:
$ virtualenv -p /usr/bin/python3 --no-site-packages venv
$ venv/bin/pip install "vcs-mirrors[gitlab,github]"
Then copy vcs-mirrors.yaml.example into your current-working-directory:
$ cp venv/lib/python3.6/site-packages/vcs-mirrors/vcs-mirrors.yaml.sample vcs-mirrors.yaml
Edit it for your needs.
Usage
venv/bin/vcs-mirrors -h
venv/bin/vcs-mirrors add -h
add examples:
This one try to create a repo “pcdummy/proxmox-dockerfiles” on git.lxch.eu - the identifier must be unique in the config file:
$ vcs-mirrors add me/p-dockerfiles https://github.com/pcdummy/proxmox-dockerfiles.git git.lxch.eu:pcdummy/proxmox-dockerfiles
This doesn’t:
$ vcs-mirrors add me/p-dockerfiles https://github.com/pcdummy/proxmox-dockerfiles.git git@git.lxch.eu:pcdummy/proxmox-dockerfiles.git
Full mirroring include “prune” and “force” pull/push:
$ vcs-mirrors add -f -p me/p-dockerfiles https://github.com/pcdummy/proxmox-dockerfiles.git git.lxch.eu:pcdummy/proxmox-dockerfiles
If you give an host as target “add” creates the repo on the host and translates it to a git URL else add does nothing else than adding the params to your configuration file.
Development
$ pip install -e ."[development,gitlab,github]"
Keywords
gitlab github sync mirror vcs-mirror bazaar
Changelog
This document describes changes between each past release.
0.0.7 (2018-04-23)
Fix pip install by moving away of PEP 420 Namespaces. [pcdummy]
0.0.6 (2018-04-23)
Fix another typo in MANIFEST.in. [pcdummy]
0.0.5 (2018-04-23)
Include python files in the pip packages, part2. [pcdummy]
0.0.4 (2018-04-23)
Include python files in the pip packages. [pcdummy]
0.0.3 (2018-04-22)
Add another debug line (to show CWD changes). [pcdummy]
Add tag pushes. [pcdummy]
Make mirroring finaly working by using “–mirror”. [pcdummy]
0.0.2 (2018-04-21)
Fixup classifiers. [pcdummy]
0.0.1 (2018-04-21)
Initial Release. [pcdummy]
Contributors
Sam Gleske - Idea and some code from https://github.com/samrocketman
René Jochum <rene@jochums.at>
Metadata
Release files for vcs-mirrors 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vcs_mirrors-0.0.7.tar.gz | 10.7 kB | Without provenance | Details for vcs_mirrors-0.0.7.tar.gz |
Release files / vcs_mirrors-0.0.7.tar.gz
| Download URL | vcs_mirrors-0.0.7.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ba388137c8b1452477ba7897adb407a7e2dfd618e2a5f33ee068abf27040054
|
|
BLAKE2b-256 checksum How to use checksums |
7c12c675b1465679182a6fda0a649bf1d2762c5a47a1be154c9e9abaf510ad56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for vcs-mirrors 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.