`procodile start -r -f [PATH_TO_PROCFILE]` doesn't work as expected, but `procodile start -f -r [PATH_TO_PROCFILE]` does work

[viktodorov]

While working on a startup script for procodile, I noticed that procodile start -r -f [PATH_TO_PROCFILE] puts the second flag -f inside the path, while running procodile start -f -r [PATH_TO_PROCFILE] does work as expected:
Error: Procfile not found at /opt/rails/-f/Procfile

I tried changing -f to --foreground as well, and it seems to have the same result:
Error: Procfile not found at /opt/rails/--foreground/Procfile

However, once I swapped both flags, everything worked as expected.

I'm not sure if I missed any piece of documentation that mentions the importance of flag order, sorry in case I did miss it. In any case, is this the intended behavior?

[zw963]

This is not an bug, you need append the PATH_TO_PROCFILE after -r immediately, are you try this?

procodile start -r [PATH_TO_PROCFILE] -f

If you use my fork rewrite use Crystal, you even can run like this:

alias proc="bin/procodile -r spec/apps/basic"
proc start -f