We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On Heroku currently, Codon outputs the following warning if an app has a procfile rather than the correctly named Procfile:
procfile
Procfile
~ Mis-cased procfile detected; ignoring. ~ Rename it to Procfile to have it honored.
We should add something similar to this buildpack.
We should likely also make this an error rather than a warning.
The text was updated successfully, but these errors were encountered:
An example of a lower-cased procfile causing confusion even on classic (where there is already a warning): https://heroku.support/1414816
As such it seems either an error or else accepting both capitalisations might be preferable?
Sorry, something went wrong.
accepting both capitalisations might be preferable?
Seems good. We could downcase everything so PrOcFiLe would be accepted as well.
PrOcFiLe
Kick it up a notch: When there's no match output the closest 3 Levenshtein distance filenames
No branches or pull requests
On Heroku currently, Codon outputs the following warning if an app has a
procfile
rather than the correctly namedProcfile
:We should add something similar to this buildpack.
We should likely also make this an error rather than a warning.
The text was updated successfully, but these errors were encountered: