gitsetgo

2.0.0 • Public • Published

:checkered_flag: gitsetgo · Travis Documented with emdaer

Automate synchronized git deployments across multiple repositories.

Why?

Let’s say you have an ecosystem of applications and services, each with its own git repository. Let’s also say you use a CI service like Travis to manage the deployment for each application upon a push to an environment git branch. Manually pushing all the repositories to the appropriate environment remote/branch from the appropriate source remote/branch could be time consuming and error prone. With gitsetgo you use configuration to define repeatable deployment procedures which you can invoke with a single command. You could, for instance, deploy all of your repositories from their QA environment to a staging environment, or to a separate environment for load testing, or perform both procedures at the same time!

How?

You can define any number of “deployments” in configuration each with its own set of repositories. Each repository defines its source and destination remotes and branches. When gitsetgo is invoked with a valid deployment (example: gitsetgo stage-to-prod), it will iterate over each repository, cloning from the source remote at the specified branch and force-pushing to the destination remote at the specified branch.

Installation

Global

yarn global add gitsetgo

OR

npm i -g --save gitsetgo

Per-Project

yarn add gitsetgo

OR

npm i --save gitsetgo

Usage

  1. GIT: Ensure you have git installed and that you have access to the remotes to which you would like to deploy. Gitsetgo uses the git executable under the hood to perform deployments, so if you can’t clone/push from the command line, neither can gitsetgo.

  2. SET: Configure deployments. Create a .gitsetgorc.yml file at the root of your project that looks something like this:

     deployments:
       name: deployment-name # This is the name you'll enter on the cli. 
        repositories:
         -
           name: someRepository
           source: # Deploy from this configuration. 
             remote: git@github.com:chasingmaxwell/example.git
             branch: sourceBranch
           destination: # Deploy to this configuration. 
             remote: git@github.com:chasingmaxwell/example.git
             branch: destinationBranch
         -
           name: someOtherRepository
           source: # Deploy from this configuration. 
             remote: git@github.com:chasingmaxwell/anotherExample.git
             branch: sourceBranch
           destination: # Deploy to this configuration. 
             remote: git@github.com:chasingmaxwell/anotherExample.git
             branch: destinationBranch
         # ... more repositories can go here. 
       # ... more deployment configurations can go here. 
  3. GO: Run gitsetgo from the root of your project.

    If you installed globally:

    gitsetgo <deployment ...>

    If you installed per-project:

    npx gitsetgo <deployment ...>

Contributors

Contributors
Peter Sieg

License

gitsetgo is MIT licensed.

Readme

Keywords

Package Sidebar

Install

npm i gitsetgo

Weekly Downloads

9

Version

2.0.0

License

MIT

Unpacked Size

239 kB

Total Files

41

Last publish

Collaborators

  • chasingmaxwell