gstore 0.0.5

Gstore is a simple tool to synchronize GitHub repositories of your organizations.

Gstore is a simple tool to synchronize GitHub repositories of your organizations.

Overview

This tool uses the GitHub API to get a list of all forked, mirrored, public, and private repos owned by your organizations. If the repo already exists locally, it will update it via git-pull. Otherwise, it will properly clone the repo.

It will organize your repos into the following directory structure:

+ sync-dir
├── organization_1
│   ├── repo_1
│   ├── repo_2
│   ├── ...
│   └── repo_n
├── organization_2
│   ├── repo_1
│   ├── repo_2
│   ├── ...
│   └── repo_n
└── organization_n
    ├── repo_1
    ├── repo_2
    ├── ...
    └── repo_n

Typical use case

Install

Requirements

• Python >= 3.6.7

• Git >= 1.7.0

Installing Gstore

Installing Gstore is easily done using pip. Assuming it is installed, just run the following from the command-line:

$ pip install gstore

Or to install development version:

$ pip install -e git://github.com/sergeyklay/gstore.git#egg=gstore

This command will download the latest version of Gstore from the Python Package Index and install it to your system. The command gstore will be available to you from the command line.

More information about pip and pypi can be found here:

• Install pip

• Gstore on PyPI

Alternatively, you can install from the source as follows:

1. Clone Gstore repository

2. Run pip install -r requirements.txt

3. Run the gstore module (directory) as follows:

$ python -m gstore --help

Getting Started

1. Generate a GitHub Personal Access Token with with at minimum repo scope (Full control of private repositories)

2. Save the token in a safe place; you’ll need it when use Gstore

Usage

gstore [-h] [--user USER] --token TOKEN [--org [ORG ...]] [target]

Positional arguments:

• target base target to sync repos (e.g. folder on disk)

Optional arguments:

• -h, --help — Show help message and exit

• --user USER — Username to use to get organizations list

• --token TOKEN — Personal access token

• --org [ORG ...] — Organizations you have access to (by default all)

Examples

Sync all repos from all organizations

To be able get organizations list for a user, Gstore will need a GitHub username. Thus we pass it bellow (--user).:

$ gstore --token "$TOKEN" --user "$GH_USER" ~/backup

Unless you set the GSTORE_DIR environment variable and don’t provide target, Gstore will sync all the repositories to current working directory.:

# Will sync all the repositories to current working directory
$ gstore --token "$TOKEN" --user "$GH_USER"

# Will sync all the repositories to ~/work directory
$ export GSTORE_DIR=~/work
$ gstore --token "$TOKEN" --user "$GH_USER"

# Will sync all the repositories to ~/backup directory
$ gstore --token "$TOKEN" --user "$GH_USER" ~/backup

Sync all repos from Acme organization

To get all repositories of a specific organization, just specify it as follows:

$ gstore --org Acme --token "$TOKEN" ~/backup

To specify a target directory right after organization list use double dash to signify the end of org option.:

$ gstore --token "$TOKEN" --org Acme -- ~/backup

Sync all repos from Foo, Bar and Baz organizations

To get all repositories of the listed organizations, specify them separated by a space:

$ gstore --token "$TOKEN" --org Foo Bar Baz -- ~/backup

Logging

All informational and error messages produced by Gstore are sent directly to the standard streams of the operating system. Gstore doesn’t have any special tools/options to setup logging to files. Such design was chosen deliberately to not increase Gstore complexity in those aspects where this is not clearly necessary, and also to simplify its administration by end users.

So, informational and error messages produced by Gstore are sent to two separate streams:

• The regular output is sent to standard output stream (STDOUT)

• The error messages and the warning ones are sent to standard error stream (STDERR)

The format of the messages generated by Gstore was chosen in such a way as to preserve human readability, but at the same time to allow specialized tools to parse message entries according to a single template.

Let’s look at a few examples to demonstrate the above:

# All messages are visible
$ gstore --token "$TOKEN" --user "$USER" ~/work

# Only informational message are visible
$ gstore --token "$TOKEN" --user "$USER" ~/work 2>/dev/null

# Only error messages and warnings are visible
$ gstore --token "$TOKEN" --user "$USER" ~/work 1>/dev/null

# Store logs separately
$ gstore --token "$TOKEN" --user "$USER" ~/work > info.log 2> err.log

# Store all the logs in the same file
$ gstore --token "$TOKEN" --user "$USER" ~/work > gstore.log 2>&1

Similar projects

There are some projects similar to Gstore you may be interested in:

• https://github.com/kennethreitz42/ghsync

• https://github.com/adw0rd/github-sync

Support

Feel free to ask question or make suggestions in our issue tracker.

Changes

To see what has changed in recent versions of Gstore see CHANGELOG.rst.

License

This project is open source software licensed under the GNU General Public Licence version 3. © 2020 Serghei Iakovlev