pub fn serve_resolved(
socket: &Path,
manifest: Manifest,
read_only: bool,
governing: Option<&Path>,
) -> Result<(), ServerError>Expand description
serve_at, with the governing manifest named explicitly (F73 phase 3).
governing is the path resolution actually settled on — under
PUSHKIN_MANIFEST it is not under the watch root at all, and from a
subdirectory it is not the watch root’s own pushkin.toml. Only that file
reloads. None keeps the historical default of the watch root’s manifest,
which is what the in-crate callers and their suites mean.
Resolution stays in the CLI: this crate has no git and no environment knowledge, and giving it any would put two answers to “which manifest” in the tree — the F73 defect wearing a different hat.
§Errors
Io when the socket cannot be created/bound; Protocol when the
runtime cannot be built.