Skip to content
New issue

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

Warn or error on mis-cased Procfile #192

Open
edmorley opened this issue Oct 30, 2023 · 2 comments
Open

Warn or error on mis-cased Procfile #192

edmorley opened this issue Oct 30, 2023 · 2 comments

Comments

@edmorley
Copy link
Member

On Heroku currently, Codon outputs the following warning if an app has a procfile rather than the correctly named 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.

@edmorley
Copy link
Member Author

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?

@schneems
Copy link
Contributor

accepting both capitalisations might be preferable?

Seems good. We could downcase everything so PrOcFiLe would be accepted as well.

Kick it up a notch: When there's no match output the closest 3 Levenshtein distance filenames

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

No branches or pull requests

2 participants