semvec/pypi-packages huggingface dataset:
gitvier 0.1.1
A component manager based where your components live in Git.
License: MIT

gitvier
=======

Gitvier is a CLI "component management" tool for when you've got a container repository and then that repository relies
on a bunch of components to operate, which you're then actively working on those components. As such, it aims to allow
the user to try and manage these components, allowing for installing, updating, etc. as well as running commands over
some/all components. However, it differs from something like GitMan in that it will not explicitly revert dependencies
to specified revisions unless explicitly forced as most likely if you install a component on "master" and the
component is currently on branch "develop", if you run "gitvier update", you don't expect that component to be put back
onto master, but rather that maybe just do a git pull on this component (and all others). I primarily built this
to support the usecase of `Submitty`_ and for my research projects.

This borrows concepts heavily from `GitMan`_ which is a great dependency
manager with Git, but less useful as a "component manager" (hence the existance of this tool).

Dependencies
------------

* Python 3.5+
* Git

Others?

Installation
------------
From Pip::

    pip3 install gitvier

From Source::

    git clone https://github.com/MasterOdin/gitvier
    python3 setup.py install


Usage
-----
::

    $ gitvier --help
    usage: gitvier [-h] [-V] <command> ...

    A component manager based where your components live in Git.

    positional arguments:
      <command>
        init         Initialize a new gitvier directory

    optional arguments:
      -h, --help     show this help message and exit
      -V, --version  show program's version number and exit

Gitvier Config File
-------------------

Gitvier operates over a `.gitvier.yml` config file which contains the various components of our system. At the root
level you can specify a `location` (defaults to current directory if omitted) where all components would live and
`components` which is a list of components which contain the following elements::

    name: <component_name/subfolder where component will be installed to>
    repo: <git_url>
    rev: <branch or tag or commit hash or branch/tag@timestamp>
    commands: <list of bash commands to run after install/update> (optional)

An example of a `.gitvier.yml` file (taken from `Submitty`_)::

    location: .
    components:
    - name: RainbowGrades
      repo: https://github.com/Submitty/RainbowGrades
      rev: master
    - name: grading
      repo: https://github.com/Submitty/AutoGrading
      rev: master

.. _Submitty: https://github.com/Submitty/Submitty
.. _Gitman: https://github.com/jacebrowning/gitman
datafaser 0.2.0
Data combiner and converter
License: MIT
Keywords: data conversion

Datafaser
=========

Datafaser collects and generates data, then fills in templates to generate files.

Results of each phase are checked against data schemas and content descriptions.

Requirements
------------

 - Python 3.6

Setup
-----

    . setup-development

Testing
-------

    nosetests --with-coverage --cover-package=datafaser

Use
---

    . local/bin/activate
    python datafaser --help

For example, to output the schema of datafaser as yaml:

    python datafaser utilities/convert-json-to-yaml.yaml < datafaser/data/schema.json

Documentation
-------------

Ideas in doc folder are currently a bit out of date.
howlermonkey 1.0.2
A slack messaging authentication andinterfacing system for the DTG
License: MIT

Howler Monkey
=============
A slack messaging authentication and interfacing system for the DTG
-------------------------------------------------------------------
Intended to allow for automated messaging to our DTG slack group at a controlled endpoint.

Authentication is provided by only allowing connections over local unix domain sockets on a puppy VM. As such any user that can gain access to the host in order to connect must have sufficient monkeysphere auth and thus be a member of the DTG or at least equivalently privileged. Unauthenticated access by minor services can also be mediated by co-locating them on the same host.
git-pretty 0.1.2
An implementation of Justin Hileman's chart from "Changing History, or How to Git Pretty"
License: MIT
Keywords: git

git-pretty
==========

An implementation of Justin Hileman's handy chart from
http://justinhileman.info/article/git-pretty/

.. figure:: http://justinhileman.info/article/git-pretty/git-pretty.png
   :alt: Git Pretty Chart

   Git Pretty Chart

Install
-------

.. code:: bash

    pip install git-pretty

Use
---

Just run

.. code:: bash

    git-pretty

This opens an interactive session like this:

.. code:: bash

    So you have a mess on your hands. What sort of mess?

    1: An uncommitted mess
    2: I accidentally committed something
    3: My Git history is ugly
    >