# ApiRepl
## What it is If you want API data copied to your database, the workers should fetch for you elastically.
## Setup ### Database Requirement use schema.sql to create a database, and load it with the types of information you need ### Subclass BaseWorker see samples/usage.py for an example. Create an api method and save method for your workflow by subclassing BaseWorker.
## Functionality (requirements) * Splits update task into pieces * Prioritizes pieces * Can be paused and resumed * Can scale across hosts easily using DB * Good test coverage (soon :) )
## Usage See Sample folder
Metadata
Release files for ApiRepl 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 | Actions |
|---|---|---|---|---|
| ApiRepl-1.tar.gz | 2.1 kB | Without provenance | Details for ApiRepl-1.tar.gz |
Release files / ApiRepl-1.tar.gz
| Download URL | ApiRepl-1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8c0d39dfe92061619814082bc5f11400cc3fb6d4a04ed9a25503afba8e213ed
|
|
BLAKE2b-256 checksum How to use checksums |
1544758be90c7e58b4b8f0661499934cba35bca0e59dc98edadf835c2ef6658a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ApiRepl 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.