Expand description
ferro docker:init — generate a production-ready Dockerfile and static
.dockerignore from project metadata. Phase 122.2 §3.
Phase 127 Plan 04: --dry-run renders every output file to memory and
prints it to stdout without touching the filesystem (D-17, D-18). The
“Next steps” footer (D-13, D-14) is printed after a successful
non-dry-run invocation and is suppressed in dry-run (D-16). Render
errors remain hard errors in both modes (D-19).
Phase 130: the dual-manifest pattern is retired. Docker builds read the
project Cargo.toml directly; ferro developers who need to point at an
unpublished local checkout maintain an uncommitted [patch.crates-io]
block by hand.
Functions§
- execute
- Library-level entry point used by integration tests. Returns
Resultinstead of printing to stderr, so tests can assert on failures. - run
- Entry point used by
main.rs. Returns a process-style exit: prints errors to stderr and returns without panicking so clap stays happy. - run_
with - Full entry point supporting the
--ferro-versionoverride and--dry-run.