Custom egg upload where the user wants
This package provides a plugin for zest.releaser that offers to upload the released egg via SCP, SFTP or HTTP(S) PUT (WebDAV) to a custom location (instead of or in addition to PyPI).
This plugin is based on gocept.zestreleaser.customupload to do the upload process and uses the distbase and distdefault concept of jarn.mkrelease, so you need to add something like this to your ~/.pypirc like the following:
[cs.zestreleaser.upload] _default_with_input_ = scp://download.gocept.com//var/www/customers/ _default_ = scp://download.gocept.com//var/www/packages
If the option _default_with_input is set, the script will ask the user a folder name that will be appended to the setting, and the created egg will be uploaded there and the script will finish there.
This option is useful if you have a folder where you have one folder per project/customer in the same place.
If the option _default_with_input_ is not set and _default_ is set, the script will upload the egg to that destination. This is usefull as a default destination of your eggs.
Options for HTTP(S) PUT (WebDAV)
This option is the same as in gocept.zestreleaser.customupload so HTTP(S) PUT (WebDAV) is implemented using curl to add options to curl, e. g. to disable certificate checks, add the options in front of the URL like this:
[cs.zestreleaser.upload] gocept.special = --insecure https://dav.gocept.com/special
Development
The source code is available in the git repository at https://github.com/codesyntax/cs.zestreleaser.upload
Please report any bugs you find at https://github.com/codesyntax/cs.zestreleaser.upload/issues
Changelog
2.0 (2020-02-26)
Python3 support [erral]
1.0 (2014-11-07)
Initial implementation [erral]
1 maintainer
Metadata
1 maintainer
Release files for cs.zestreleaser.upload 2.0
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 |
|---|---|---|---|---|
| cs.zestreleaser.upload-2.0.tar.gz | 22.3 kB | Without provenance | Details for cs.zestreleaser.upload-2.0.tar.gz |
Release files / cs.zestreleaser.upload-2.0.tar.gz
| Download URL | cs.zestreleaser.upload-2.0.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4fbdc20489735760fb8bb27f89325d6fb7cd56673f2059b0985d1dbd5efc9eb
|
|
BLAKE2b-256 checksum How to use checksums |
36c3227b35b2c97bb32bf48c4d6e53be43d8811b1c8fc1d91f4d4eb404078397
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.9
|
Security for cs.zestreleaser.upload 2.0
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.
