Skip to content

Fix Procfile parsing when there is no space after the colon - #220

Open
vulragrag-star wants to merge 1 commit into
DarthSim:masterfrom
vulragrag-star:fix/procfile-missing-space-after-colon
Open

vulragrag-star wants to merge 1 commit into
DarthSim:masterfrom
vulragrag-star:fix/procfile-missing-space-after-colon

Conversation

@vulragrag-star

Copy link
Copy Markdown

Summary

Procfile lines without a space after the colon (e.g. web:rails s) were ignored by the parser regex (:\s+), so Overmind reported No entries were found in Procfile. Allow zero-or-more whitespace after the colon so those entries load the same way as web: rails s.

Fixes #217

Test plan

  • go test ./start/ -run TestParseProcfileAllowsMissingSpaceAfterColon
  • Manual: Procfile with web:echo hi starts without the empty-Procfile error

Foreman-style entries like `web:rails s` previously failed the
`^\w+:\s+` regex and surfaced as "No entries were found in Procfile".
Allow zero-or-more whitespace after the colon and cover it with a unit
test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing blank after Procfile target breaks startup

1 participant