Metadata-Version: 2.4
Name: GitLarder
Version: 0.9.3
Summary: Python NoSQL Implementation on top of git
Author-email: Aaron Wilson <aaron@olark.com>
License-Expression: Apache-2.0
Project-URL: github, https://github.com/aawilson/git-larder
Keywords: git,storage,nosql
Classifier: Development Status :: 7 - Inactive
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Operating System :: OS Independent
Classifier: Operating System :: POSIX
Classifier: Operating System :: Microsoft :: Windows
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Description-Content-Type: text/x-rst
License-File: LICENSE
Requires-Dist: GitPython>=0.3.0
Provides-Extra: test
Requires-Dist: nosetests; extra == "test"
Dynamic: license-file

# Git Larder

"A synonym of Git Storage"

## Wrapped NoSQL Built On Git

GitLarder is a dead-simple flat-file storage mechanism meant for data needing
strict version control with few writes. It's built straight on top of git and
works alongside it.

### Usage

A GitRecordFactory object can be instantiated with a repo path. The path should
point to a real git repository, and anything intended to be interacted with
using GitLarder should be simple json files in directories (called "models").
Any tree not intended to be pointed at with GitLarder should be shoved into a
.gitrecord_ignore file in the top level.

A GitRecord object can be instantiated from a dict, but the more likely usage is
to retrieve a class from the GitRecordFactory using get_model. The factory
finder methods can then be called on the generated GitRecord subclass without
having to explicitly pass in a model name.
