zebflow 0.9.1

Reactive web automation platform — pipelines, templates, and real-time collaboration in a single binary.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

//! Swappable infrastructure engines: metadata, objects, runtime data, state bus, and cache.
//!
//! This layer exists so Zebflow can keep one product model while swapping implementations:
//!
//! - local filesystem vs. object storage
//! - in-memory bus vs. Redis-like shared bus
//! - process-local caches vs. distributed caches
//! - platform-local metadata vs. future externally managed catalog stores
//!
//! # Structure
//!
//! | Module | Responsibility |
//! |---|---|
//! | [`catalog`] | Platform metadata contracts and catalog-backed implementations |
//! | [`object`] | Repo/files/assets/bundle storage |
//! | [`runtime_data`] | Per-project runtime data roots and engines |
//! | [`state`] | Shared KV/pubsub/lease semantics |
//! | [`cache`] | Generic cache contracts and implementations |
//! | [`durable`] | Strict versioned JSON and crash-safe local file replacement |
//! | [`path`] | Containment for caller-supplied relative paths |
//!
//! # Boundary rule
//!
//! `io/` is about *where state lives* and *how it is exchanged*.
//! It is not where project/business decisions belong.

pub mod cache;
pub mod catalog;
pub mod durable;
pub mod object;
pub mod path;
pub mod runtime_data;
pub mod state;