mgit - Multi-Repository Git Management Tool

mgit is a command-line tool for managing and executing commands across multiple Git repositories simultaneously.

Download

Download the latest version from the Releases page.

Install on Linux

App Binary

chmod +x mgit
sudo mv mgit /usr/local/bin/mgit

Shell Completion

Bash/Zsh/Fish (Linux)

sudo mv <mgit_completion> /etc/bash_completion.d/<mgit_completion>
source /etc/bash_completion.d/<mgit_completion>

Install on MacOS

App Binary

chmod +x mgit
sudo mv mgit /usr/local/bin/mgit

Shell Completion

Zsh (macOS)

mkdir -p ~/.zsh/completions
mv <_mgit> ~/.zsh/completions/
echo 'fpath+=~/.zsh/completions' >> ~/.zshrc
autoload -Uz compinit && compinit

Install on Windows

App Binary

Move-Item mgit.exe "$env:USERPROFILE\bin\mgit.exe"
# Ensure $env:USERPROFILE\bin is in your PATH

Shell Completion

PowerShell temporary use

go run ./ completion powershell > mgit_completion.ps1

. .\mgit_completion.ps1 # for temporary use 

Build from source (requires Go to be installed)

Build Binaries

Linux/macOS

cd mgit
go build -o mgit
chmod +x mgit
sudo mv mgit /usr/local/bin/mgit

Windows (PowerShell or CMD)

cd mgit
go build -o mgit.exe
Move-Item mgit.exe "$env:USERPROFILE\bin\mgit.exe"
# Ensure $env:USERPROFILE\bin is in your PATH

Completion

bash

mgit completion bash > mgit_completion.bash

zsh

mgit completion zsh > mgit_completion.zsh

fish

mgit completion fish > mgit_completion.fish

powershell

mgit completion powershell > mgit_completion.ps1

Usage

Add repositories/projects

# Add a new repository to current project
mgit add repo --path <full-path> #name of the repository is automatically sourced from the end of the path

mgit add repo --path <full-path> --name custom-name

# Add a new project
mgit add project --name <project-name>

Delete repositories/projects

# Delete a repository from current project
mgit delete repo <repo-name>

# Delete a project
mgit delete project <project-name>

List repositories

# List repositories in current project
mgit list

# List repositories in a sepecified project
mgit list --project name

# List repositories in all projects
mgit list --all

Switch between projects

mgit switch <project-name>

Execute commands on repositories

mgit exec repo1 repo2 repo3 -- command
mgit exec -- command

Examples

1. Add repositories to your workspace:

   mgit add repo --path /home/username/projects/project1
   mgit add repo -p /home/username/projects/project2
   

2. Create and switch to a new project:

   mgit add project work-projects
   mgit switch work-projects
   

3. Check status of specific repositories:

   mgit exec project1 project2 -- git status
   

4. Pull latest changes from all repositories in current project:

   mgit -- git pull
   

5. List all tracked repositories across projects:

   mgit list --all
   

Configuration

mgit uses a SQLite database to store your repository information and projects. The database is automatically created at ~/.mgit as db.sqlite on first run.

It also keeps track of the current project in ~/.mgit/config.json

Contributing

Contributions are welcome! Please open an issue or submit a pull request for any improvements or bug fixes.

License

This project is licensed under the Apache-2.0 License - see the LICENSE file for details.

DevOps Showcase

Architecture Overview

Microservices

Technologies: Python, Flask, MongoEngine, Celery, Redis.

Technologies used in Jenkins pipeline: Docker, Trivy, Azure Container Registry

These microservices communicate with each other using Celery tasks over Redis queues.

Frontend

GitOps

Provisioning

DeploymentNote

a simple cli tool to add notes to deployments in case you want to access some info fast

Prerequisites

• Go: Version 1.16 or higher.
• Kubernetes: A working Kubernetes cluster with kubectl installed and configured.
• Sudo Privileges: Required for system-wide installation.

Installation

Follow these steps to install DeploymentNote system-wide:

1. Clone the Repository:

   git clone https://github.com/yourusername/deploymentnote.git
   cd deploymentnote
   

2. Build the Binary:

   go build -o deploymentnote
   

3. Make the Binary Executable:

   chmod +x deploymentnote
   

4. Move the Binary to /usr/local/bin (requires sudo):

   sudo mv deploymentnote /usr/local/bin/
   

5. Generate the Bash Completion Script:

   go run ./ completion > deploymentnote_completion
   

6. Install the Completion Script (requires sudo):

   sudo mv deploymentnote_completion /etc/bash_completion.d/deploymentnote
   

7. Reload Bash Completions:

   source /etc/bash_completion.d/deploymentnote
   

Usage

Once installed, simply run deploymentnote

Commands Overview

Both adding and deleting notes supports autocompletion of deployment name

• Show Deployments:

  Running deploymentnote without any subcommands displays a table of deployments with available custom notes:

  deploymentnote
  

• Add a Note:

  deploymentnote add deployment_name "write note here"
  

• Delete a Note:

  deploymentnote delete deployment_name
  

Configuration

• Custom Data File:

  DeploymentNote uses a JSON file at /tmp/custom_values.json to store and retrieve custom notes. You may edit this file manually if needed.

• Kubernetes Integration:

  Deployment data is fetched via the command kubectl get deployments. Ensure your kubectl context is correctly set for your target cluster.

Azure Docker Provisioning

Terraform and Ansible automation for Azure infrastructure: VM provisioning, Docker setup.

TLDR: a way to just create a ready vm to just clone and docker compose up my projects that need to download Gigs of dependencies

ty azure for providing student pack and having fast internet

Components

• Terraform - Azure VM provisioning
• Ansible - Configuration management
  • Docker installation
  • Git installation

    Prerequisites

1. Local Tools

Ensure you have the following installed on your local machine:

• Terraform
• Ansible (including ansible-playbook)
• Azure CLI

2. Authentication & Credentials

• Azure Account: Authenticate your CLI session by running:

  az login
  

• Azure Subscription: Export your Subscription ID as an environment variable: (If you want this to be a one time thing paste that line in your .bashrc or wherever you usually put environment variables)

  export ARM_SUBSCRIPTION_ID="your_subscription_id_here"
  

• SSH Keys: The provisioning process requires an SSH key pair securely located at ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub.
  • If you don’t have an SSH key pair, you can generate one using:

    ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_rsa
    

Usage

cd terraform
terraform init
terraform apply
# Set ssh_enabled variable to run Ansible configuration
# Ansible runs automatically after VM creation

License

MIT License