About
Using git for deployments is a great solution for agile development processes and is implemented by different people with many different flavours. Any solution has one thing in common: You have to move the whole history of your project over to your server. This may be ok for some setups, but has - besides giving many internals to your clients - some disadvantages like:
Rollbacks are more complex, as you need to know which commit is the last release (may be solved using tags)
You have to copy the whole repository over to the server, so you cannot skip any files or add new ones only needed on the server (like aggregated CSS/JS)
fabdeploit tries to solve these issues by using a seprate release branch, not wired to the normal git branches and history. This release branch will only contain release history (one commit for every release/deployment) and allows you to use filters to change the contents of the commit tree. This way you are able to have a very slick deployment process only containing what is necessary, you may even add new files not contained in your normal history.
In addition fabdeploit contains helpers for professional deployment of some common CMS/Frameworks we use. This will help you implementing a clean process of common deployments, including enabling maintenance mode, running database migrations, clearing the caches, …
Documentation
Still not as much as intended, but growing, this is a goal for 1.0. Please feel free to look at the example/ directory or the code itself in addition to the documentation.
1 maintainer
Metadata
1 maintainer
Release files for fabdeploit 0.13.1
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 | |
|---|---|---|---|---|
| fabdeploit-0.13.1.tar.gz | 14.5 kB | Without provenance | Details |
Release files / fabdeploit-0.13.1.tar.gz
| Download URL | fabdeploit-0.13.1.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fd9652f67dcfb3133c195429349d9bf6c63ce5d38afc3cb845a4ff0a2e9835de
|
|
BLAKE2b-256 checksum How to use checksums |
c0bc4ebb57202b25005c2886cacfb1a1cd94fc1cd7f5278533dd1f76144da30f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for fabdeploit 0.13.1
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.
