amadan
Rootfs apps: run any Linux app (Rails, Laravel, Django) on your own boxes, isolated like a nested instance Feature Request open
On branch design-rootfs-apps
Design: docs/superpowers/specs/2026-10-24-rootfs-apps-design.md on design-rootfs-apps (rev 2, 74107fdb). From a brainstorming session with Paul, 2026-10-24.
A release may carry a read-only root filesystem built locally from an OCI image (carlos ship --rootfs). Boxes run it as a nested instance under systemd (RootImage=), no Docker, no registry, no platform builds. The manifest declares a web process (gets CARLOS_SOCKET/CARLOS_DB) and worker processes (co-spawn sidecars sharing the instance's directory). Always-on by default. Customer fleets only on shared deployments; any box on a single-tenant one. Free testing via a local carlos ship --check.
Also asked for here: an operator-granted egress allow so any nested instance on the customer's own boxes can reach private databases (nested IPAddressDeny= blocks RFC 1918 today).
Follow-up designs: stateless replicas (wanted; S3-CAS apps are first users too), JIT opt-in, multi-db replication.
Astra builder check round 1: six questions, five settled as author's calls (B1-1..5), one open for Paul (§13 Q1: failover acceptable for the first Kubernetes migration, or multi-box from day one?).