WickedBox
Private file and app yard with Ceph-backed storage, upload pipelines, sync lanes, and GitOps-managed operator infrastructure behind the curtain.
About This Project
WickedBox is private on purpose, but the inspected repo still tells a lot about what it really is. This is not just “a box site” — it is a storage and transfer yard with Kubernetes manifests for the main box service, Ceph-backed PVCs, ingress and middleware rules, ZeroTier-connected access lanes, Syncthing pieces, migration jobs, and a separate Rusty-Uppah uploader path for resumable intake. Public screenshots and mystery vibes are fine, but the honest project story is that WickedBox already has serious operator plumbing under the hood.
Current Highlights
- Private operator file yard — not publicly exposed yet
- Ceph-backed persistent storage for app, metadata, and bulk lanes
- Ingress, middleware, and network-policy wiring for the main box surface
- Rusty-Uppah uploader infrastructure included for resumable upload handling
- Syncthing and migration resources present in the repo for data movement workflows
- ZeroTier / SSH-connected operator access paths in the deployment layer
What the Private Repo Actually Shows
The attached repo is mostly infrastructure and deployment material, but that is exactly what makes the current state clearer. WickedBox already has real manifests, PVCs, configmaps, middleware, and uploader-side services. It is not an empty idea waiting for a front end.
Private by Design
- No public project URL is shared right now
- The source is not being published yet
- The current page should describe the shape honestly without oversharing the fun bits
- Some of the more interesting experiments are better left in operator territory for now