feat: Add packaging and deployment targets to architecture documentation; update roadmap with container packaging details and review policy

2026-05-23 18:15:31 -05:00
parent e20669e42a
commit 94c7cadcd7
4 changed files with 77 additions and 26 deletions
@@ -17,6 +17,19 @@ Out of scope for early phases:
 - Rich social graph features beyond project-oriented interactions.
 - Highly customized recommendation systems.

+## Packaging and Deployment Targets
+
+FeDIY is intended to be shipped and operated through a small set of first-class packaging targets so instance operators can choose the deployment style that fits their environment:
+
+- **Nix flake/devShell**: reproducible development and build environment for contributors and operators who prefer Nix.
+- **Flatpak**: desktop-friendly distribution path for bundled client or companion tooling where applicable.
+- **OCI/Docker container image**: a standard containerized deployment path for managed hosting, Kubernetes, and simple `docker compose` installs.
+- **NixOS module**: optional system integration for operators already using NixOS.
+
+These targets should share the same application artifact and configuration model where possible. Packaging differences should be limited to how the binary is delivered, configured, and run; they should not fork the core runtime behavior.
+
+The flake and related packaging shells should be reviewed periodically so the included tools stay aligned with current phase needs. The default posture is to keep the dev environment lean and add tools only when they directly support active work such as building, testing, localization, accessibility validation, container packaging, or release tasks.
+
 ## Core Domains

 - Identity and actors.