This simple recipe for zc.buildout fetches data from a given repository and stores it into its part’s directory. A simple task using this could look like this:
[myapp] recipe=sact.recipe.gitrepository repository=git://github.com/securactive/sact.recipe.gitrepository rev=7c73978b55fcadbe2cd6f2abbefbedb5a85c2c8c
This would store the repository under ${buildout:directory}/parts/myapp and keep it at exactly this revision, no matter what happens on the server.
The recipe has following options:
- repository
The absolute URL of the repository to be fetched
- rev
A revision/commit within this repository the environment should use.
- branch
If you want to stay up to date with a certain branch other than “master”, use this.
- paths
List of relative paths to packages to develop. Must be used together with as_egg=true.
- newest
This overrides the newest-option of the global setting for this part
- as_egg
Set to True if you want the checkout to be registered as a development egg in your buildout.
- cache-name
Name of the repository in the download-cache directory.
- recursive
Follow submodules (Note that submodules are not cloned from the download cache).
Offline installation
If you want to install a part from the download-cache, this is now possible, too:
[buildout] parts = myapp download-cache = /var/cache/buildout install-from-cache = true [mylib] recipe = sact.recipe.gitrepository repository = http://domain.com/repo.git
With this configuration, the recipe will look for /var/cache/buildout/repo and clone it into the local parts/ folder.
The recipe also supports an additional “cache-name” setting that lets you configure the folder name of the repository in the download cache.
Version 1.2 (2013-12-03)
Add a example in Buildout
Porting code to Python 3
Version 1.1 (2013-12-03)
Typos in the documentation
Version 1.0 (2013-11-28)
Initial version
Release files for sact.recipe.gitrepository 1.2
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 | Actions |
|---|---|---|---|---|
| sact.recipe.gitrepository-1.2.tar.gz | 7.4 kB | Without provenance | Details for sact.recipe.gitrepository-1.2.tar.gz |
Release files / sact.recipe.gitrepository-1.2.tar.gz
| Download URL | sact.recipe.gitrepository-1.2.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c39afeb10a0d5bc7e2521067bf2ea813c965822e52c9c8d0ae64888884337b00
|
|
BLAKE2b-256 checksum How to use checksums |
b73c118c58618ccf02c6f6906a5603027f2ea2b9171d3f00a78a78370b5af95d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sact.recipe.gitrepository 1.2
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.
