paratix 0.4.0 → 0.6.0

package/README.md

@@ -20,7 +20,7 @@ The result is a practical server automation tool with a compact mental model: mo
 - **Structured orchestration**: recipes and signals keep service reloads and grouped changes explicit.
 - **Declarative host guards**: gate modules on package, command, file, directory, symlink, or socket state without embedding shell checks in strings.
 - **Strong bootstrap story**: supports explicit first-run flows and strict host-key handling.
-- **Practical built-in modules**: packages, files, services, users, SSH, firewall, systemd, sysctl, mount, rsync, and more.
+- **Practical built-in modules**: packages, files, services, users, SSH, firewall, systemd, sysctl, swap, mount, rsync, and more.
 
 ## Getting Started
 
@@ -86,6 +86,8 @@ A playbook is a TypeScript file that default-exports `server(...)`. It defines t
 
 Modules are the smallest units of work. Each module checks whether its target state already exists and only applies changes when needed.
 
+For filesystem metadata, you can now also use dedicated modules such as `file.chmod(...)` and `file.chown(...)` when you want to manage permissions or ownership without coupling that change to a file upload or template render.
+
 ### Recipes
 
 Recipes group related modules into a named unit. They help structure larger playbooks and keep the CLI output readable.
@@ -94,10 +96,24 @@ Recipes group related modules into a named unit. They help structure larger play
 
 Signals are deferred side effects such as `service.reload(...)` or `service.restart(...)`. They run when the surrounding scope actually changed, and can also be flushed explicitly with `signals.flush()` when you need a checkpoint inside a larger flow.
 
+### Compose + systemd
+
+`compose.systemd(...)` can generate a native systemd unit for Docker Compose or Podman Compose projects. By default it now starts the stack with `compose up --remove-orphans`; set `detached: true` if you explicitly want the old `-d` behaviour in the generated `ExecStart`.
+
+### Podman Quadlets
+
+For Podman-native services, Paratix now also includes `quadlet.container(...)`. It writes a `.container` file under `/etc/containers/systemd`, reloads systemd when the content changes, and works cleanly with `service.enabled(...)` and `service.running(...)` for the generated service.
+
+When you need a targeted image refresh outside the normal deploy flow, `quadlet.updateImage(...)` pulls exactly one image, reuses existing Podman registry auth on the host, optionally supports `authFile`, and only restarts the generated service when the pull actually downloaded a newer image.
+
 ### Guards
 
 Paratix also supports declarative host-state guards. Use `when.packageInstalled(...)`, `when.commandExists(...)`, `when.fileExists(...)`, `when.pathExists(...)`, `when.symlinkExists(...)`, or `when.socketExists(...)` and their inverted forms to gate modules or recipes on remote host state without shell-heavy playbooks.
 
+### Swap
+
+Paratix can also manage file-backed swap directly. Use `swap.file(...)` to provision and persist a swap file, then tune common memory behaviour with `swap.swappiness(...)` or `swap.vfsCachePressure(...)`.
+
 ## CLI
 
 ```text