Go app embeds a frontend that has to be built first
This project embeds files that have to be produced by an earlier build step, and that step is not part of the automatic recipe. It needs a PanelAlpha page to describe its build.
TypeErrorAn error that occurred in the deployed application. It is not necessarily a PanelAlpha Engine error, but we keep working on improvements so you run into fewer of them.
Seen63 times · 21 variants
WhereDockerfile, Go
StatusIn AnalysisOur team will look into this soon, verify the cause and try to fix it in an upcoming release.
Why it happens
The Go code embeds files (usually a built web UI) that the repository does not contain; they come from an earlier build step the Go build does not run, so compilation stops with "pattern ... no matching files found".
What the log looks like
Deploy log
Detected project type: GoUsing strategy: goCompiling application on hostlib/challenge/preact/preact.go:23:12: pattern static/app.js: no matching files foundDeploy failed: missing embedded assets