This release is a pre-release and may not be stable for production use.
Greyskull
An NTrack Implementation
Setup Instructions
Greyskull is configured using the following environment variables:
Name |
Description |
Default |
|---|---|---|
GREYSKULL_EXTERNAL_PORT |
The internet-facing port that greyskull is being served on. |
80 |
GREYSKULL_MEMCACHED_ENDPOINTS |
A comma separated list of memcached endpoints for greyskull to talk to. |
'127.0.0.1:11211' |
GREYSKULL_MAX_PEERS |
The maximum number of peers to return in a single request. |
32 |
GREYSKULL_STATS |
True |
|
GREYSKULL_ERRORS |
True |
|
GREYSKULL_INTERVAL |
18424 |
As you might know, environment variables must be strings. For the most part this isn’t an issue, except in the case of GREYSKULL_STATS and GREYSKULL_ERRORS where a boolean is expected. In this case use 1 for True and 0 for False.
Contact
Carlos Killpack <carlos.killpack@rocketmail.com>
License
All original code is in the public domain, MIT, or ISC at your choice.
The Bencode generation code originally from the standard python bittorrent implementation is by Petru Paler and under a MIT licenses (AFAIK).
Metadata
Release files for Greyskull 0.0.1.dev1
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 |
|---|---|---|---|---|
| Greyskull-0.0.1.dev1.tar.gz | 3.6 kB | Without provenance | Details for Greyskull-0.0.1.dev1.tar.gz |
Release files / Greyskull-0.0.1.dev1.tar.gz
| Download URL | Greyskull-0.0.1.dev1.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed906e11d4500e16a79fa7a5b7cbb6639cc52014ee4283c990406740aa1a1d24
|
|
BLAKE2b-256 checksum How to use checksums |
b50b41937af4a6f736f9b7c073cac19ecd3dd3f1b0ddd0ed17ad913c462f24da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Greyskull 0.0.1.dev1
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.