Search Results for "tree directory"

GitPrep is a lightweight, self-hosted web interface for browsing Git repositories, typically deployed on a single server with minimal dependencies. It implements features like commit history browsing, file viewing and diffing, directory tree navigation, tag/branch switching, and README rendering, much like GitHub’s core UI. Because it’s written in Perl and designed for simplicity, setup is often as easy as cloning, configuring a webroot, and pointing to repositories. Authentication and basic permissions can be configured, allowing private or team usage. Unlike full-featured Git lab or hosting suites, GitPrep focuses on just the browser view of repositories, staying lean and ideal for small teams or personal use. ...

Captain - Convert your Git workflow to Docker containers ready for Continuous Delivery. Define your workflow in the captain.yaml and use captain to your Continuous Delivery service to create containers for each commit, test them and push them to your registry only when tests passes. Use captain build to build your Dockerfile(s) of your repository. If your repository has local changes the containers will only be tagged as latest, otherwise the containers will be tagged as latest, COMMIT_ID &...

Gitslave is a script for coordinated version control of large projects combining code from multiple independent repositories using Git. More flexible than traditional git submodules, gitslave provides a simple wrapper around command-line git that manages a directory tree with multiple subsidiary ("slave") git repositories in sub-directories of a "master" git repository. Any git command run from the "gits" wrapper will be performed in all the git repositories; for example gits checkout -b newbranch will create the new branch in all repositories. Gitslave has been used for mid-sized product development with many slave repositories (representing different programs and plugins), branches, tags, and developers; and for single-person repositories tracking groups of .emacs and .vim repositories (in the latter case, it is basically used to keep the slave repositories up to date via a single command).