uploads
v0.1.43
v0.1.49 (latest) v0.1.48 v0.1.47 v0.1.46 v0.1.45 v0.1.44 v0.1.43 v0.1.42 v0.1.41 v0.1.40 v0.1.39 v0.1.38 v0.1.37 v0.1.36 v0.1.35 v0.1.34 v0.1.33 v0.1.32 v0.1.31 v0.1.30 v0.1.29 v0.1.28 v0.1.27 v0.1.26 v0.1.25 v0.1.24 v0.1.23 v0.1.22 v0.1.21 v0.1.20 v0.1.19 v0.1.18 v0.1.17 v0.1.16 v0.1.15 v0.1.14 v0.1.13 v0.1.12 v0.1.11 v0.1.10 v0.1.9 v0.1.8 v0.1.7 v0.1.6 v0.1.4 v0.1.3 v0.1.2 v0.1.1 v0.1.0
Kickside uploads — upload API, storage pipeline, preview endpoints, artifact storage, file capabilities, and default text/image/document processors.
BUSL-1.1 6.3k downloads
Updated 4 days ago Repository
kicksideuploadsfiles
Run
wippy run kickside/uploadsKickside Uploads
Kickside-owned upload API, storage pipeline, preview endpoints, file-management traits, default upload type declarations, and derived artifact storage.
What it provides
- Upload API, durable core-job submission, upload tokens, and status callbacks.
- Default
upload.typeregistry entries for text, images, and documents. - Processors:
kickside.uploads.text:processor,kickside.uploads.images:processor, andkickside.uploads.documents:processor. They run after the native upload completes and write upload artifacts. - Repositories for original upload records, deduplicated artifact blobs, and artifact aliases.
Boundary
kickside/uploads owns upload persistence, processor routing, and upload
artifact policy. Pure converters, such as kickside/doc2md, stay below this
layer and are imported by upload processors.