[Blute]

Why

rustcfml-warm-extensions (run by the entrypoint at every container start, before the server) ran rustcfml -c 'writeOutput("")' from the webroot. Inline code run there picks up the app's Application.cfc, so each start booted the application once before serving:

• onApplicationStart ran, including any database work it does;
• onRequest ran with an empty target page. An onRequest that includes its target page then fails, because an empty include resolves to the Application.cfc's own directory (Cannot read '<dir>': Is a directory), and the app's onError handles it as a 500.

Summary

• The probe is an empty template in a mktemp -d scratch directory instead of inline code in the webroot.
• An empty Application.cfc beside the probe stops the engine's upward search. The app's own isn't found even when the scratch directory is inside the webroot (TMPDIR under it, or a webroot of /tmp).
• The webroot's extensions/ is symlinked into the scratch directory, because the engine takes its application directory from the template. The search order stays: --extensions / config directory, webroot extensions/, home, beside the binary. The webroot is made absolute first, so a relative RUSTCFML_WEBROOT links correctly.
• The cwd stays the webroot, so the server .cfconfig.json (and its extensions.directory) is found exactly as the server finds it.
• Problems are counted from the engine's unedited output. Only the lines shown are rewritten to report $WEBROOT/extensions/… paths, and that uses a literal awk replacement, so no character in a path can change what's matched.
• With no writable temp directory (a --read-only container), the check falls back to the previous inline probe and says so on stderr, rather than failing the start.

Test plan

• make smoke passes, with five new cases:
  • the check doesn't fire onApplicationStart;
  • the same, with TMPDIR inside the webroot;
  • a broken extension is still fatal (exit 78) from a relative webroot (RUSTCFML_WEBROOT=.);
  • the same from a webroot with | and & in its path, reported with the webroot's path;
  • a --read-only container still passes.
• Each new case fails against the previous script.
• Against a webroot with a .rcx in extensions/ and a throwing Application.cfc: loads the extension and reports the /srv/app/extensions/... path, exit 0.
• Empty webroot: exit 0, quiet.

🤖 Generated with Claude Code