command reference

devopsgen detect

Name: DevOpsGen
Author: Bangkah

Inspect the current project and report what DevOpsGen would scaffold for it: the programming stack, the exact files that shaped the decision, and the candidate application types.

devopsgen detect output in a terminal reporting stack go with indicators go.mod — devopsgen detect inside a Go module — chain of evidence straight from the filesystem.

Reading the output

Line	Meaning
`stack: go`	The detected programming stack (`go` or `nodejs`).
`indicators: go.mod, ...`	The files that produced evidence — your audit trail for why the stack matched.
`app-type candidates: binary`	Application types plausible for this project; the wizard default comes from here too.

How it decides

Go — go.mod and its module directive looking like module example.com/app.
Node.js — package.json, plus its dependencies, and lockfile flavours (npm / pnpm) that later steer Docker image commands.
Ambiguity or zero indicators produce a distinct exit code (5) so scripts can branch safely — see exit codes.

Detection semantics: DevOpsGen detects in the current working directory, not in --output-dir. Run it from the project you want scanned.