Opload: Open Loading Server
Local installation
You should be able to clone this repo and install the package:
$ pip install -e opload
For local testing, be sure to set the following env.variables:
OPLOAD_BACKEND_SERVICE=STDLIB
To facilitate endpoint calling while developing, you may also want to set FRD_RESTAPI_DISABLE_AUTH=1.
Start the server:
$ fred serve --classname RouterCatalog --classpath opload.router.catalog
- Or just
fred serveif the env.variables are correctly set. - Or use the direct
opload servecommand.
A key that doesn't exist will return a null value (i.e., "val":null):
$ curl --request GET http://0.0.0.0:8000/get?key=demo/1.txt
You can define the holding value of a key via the set endpoint:
$ curl --request POST http://0.0.0.0:8000/set --data '
{
"key": "demo/1.txt",
"value": "Hello, world."
}
'
Metadata
Release files for opload 0.4.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 |
|---|---|---|---|---|
| opload-0.4.0.tar.gz | 4.4 kB | Without provenance | Details for opload-0.4.0.tar.gz |
Release files / opload-0.4.0.tar.gz
| Download URL | opload-0.4.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fff2bce07a4e1537c24eb4ee1975051fa2b65879fe5a3b2364433ea07b34c60e
|
|
BLAKE2b-256 checksum How to use checksums |
7f0560f9d0abbf3ed003ee47395ff8f4503c7fc49d7f8d53ede228f76ad12475
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for opload 0.4.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.