Development
This section covers building, testing, and contributing to S4.
See disk-space validation for tmpfs scenarios, ledger checks and isolated source mutations.
Building and Testing
- Rust through [rustup](https://rustup.rs): the release is pinned in rust-toolchain.toml, and rustup toolchain install in the repository installs it - Git - protoc (protobuf compiler) for the cluster gRPC code generation - nasm 2.14 or newer, on x86_64 only
Code Standards
S4 follows strict coding standards to maintain quality and readability across the team.
Contributing
Thank you for your interest in contributing to S4. This guide will help you get started.
Disk-space validation
The disk-space scenario runs each storage node on a checked tmpfs inside an unprivileged user/mount namespace. It fails if namespaces are unavailable; it never substitutes the host disk. Install curl, Python 3, netcat, coreutils, procps and util-linux. Use a machine with at least 4 GiB for licensed EE. The six-node group measured about 1.18 GiB of aggregate node RSS in addition to its 384 MiB tmpfs allocation; allocator, compiler and host services need more.