After deploy helps you to create and manage automated deploy tasks in your Django application. Inspired by Rails after_party
Quick start
Install the package using pip by running:
pip install django-after-deploy
Add “after_deploy” to your INSTALLED_APPS setting like this:
INSTALLED_APPS = [ ... 'after_deploy', ]Now after_deploy commands are available, use install flag:
python manage.py after_deploy --install
Run python manage.py after_deploy -g my_first_task to create your first task, they’ll stay at root project, on tasks folder:
my-project |-- my-app | |-- __init__.py | |-- apps.py | |-- models.py | |-- settings.py |-- tasks | |-- __init__.py | |-- _000001_my_first_task.py |-- manage.py
For execute all unapplied tasks you can run python manage.py after_deploy --run. If you need execute again a specfic task, you can run python manage.py after_deploy -r my_first_task.
Contribute
If you find an issue with AfterDeploy please log an issue. I will accept pull requests.
Metadata
Release files for django-after-deploy 0.0.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 |
|---|---|---|---|---|
| django-after-deploy-0.0.2.tar.gz | 5.1 kB | Without provenance | Details for django-after-deploy-0.0.2.tar.gz |
Release files / django-after-deploy-0.0.2.tar.gz
| Download URL | django-after-deploy-0.0.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c7940cb1a4455de3f2993eaa0a026f9b49ca2dc14099b06652dbbc560686797
|
|
BLAKE2b-256 checksum How to use checksums |
3579d981451ae1be183d13210c518359aa8d0eeb297d46f28773850f809c69ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.7.8
|
Security for django-after-deploy 0.0.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.