Welcome to git-recipe doc page
Usage
Recipe clones git repository and checkouts to revision, if it is provided in configuration. You can use recipe like this:
For python
[buildout] parts = data [data] recipe = git-recipe repository = git://example.com/my-git-repo.git ref = origin/redevlop-branch as_egg = True newest = True
For static resouces
[jquery]
recipe = git-recipe
repository = git://github.com/jquery/jquery.git
ref = origin/master
download-directory = ${buildout:directory}/static/js/
For django plugins with bad repository name
[paypal] recipe = git-recipe repository = git://github.com/johnboxall/django-paypal.git ref = origin/master repo_name = paypal as_egg = True
Options
repository - repository url
- ref - git reference wich you want to checkout.For example, it can be a
branch name or a tag name like “origin/master”、or “v1.0”.
download-directory - If filled it will make the clone in this folder.
repo_name - If filled it will change the repository name.
- as_egg - Set to True if you want the checkout to be registered as a
development egg in your buildout.
newest - always download newest repository, default is true.
And you can use buildout’s global offline configure.
About
This is a fork of gitrecipe , which doesn’t support the as_egg feature of zerokspot.recipe.git .
CHANGES
0.2 add custom repository name for django plugins.
0.1 add custom directory support for static resources.
0.0.4 determine repository now support ‘.’ and ‘_’ in its name.
0.0.3 add offline/newest configuration.
Metadata
Release files for git-recipe 0.2.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| git-recipe-0.2.7.tar.gz | 5.1 kB | Without provenance | Details |
Release files / git-recipe-0.2.7.tar.gz
| Download URL | git-recipe-0.2.7.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1805449d173513ce38f7fc61b2a3a82c2e80d5e4f752eddb19cddd0692a6c70
|
|
BLAKE2b-256 checksum How to use checksums |
022d315012bd69f41f5a999896eab7c7bfde27076ecc34a424816e8d9c7d7b58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for git-recipe 0.2.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.