PumaCtl invalid option -F

[ball-hayden]

Looks like #694 is back again...

Running puma 3.0.2:

[sparkseat@ford current]$ pumactl -F config/puma.rb start
invalid option: -F

[ball-hayden]

A few trials shows that this regression was introduced in 3.0.0.
2.16.0 is the last version that works.

[irobayna]

Same issue, looking at pumactl --help still shows -F as a valid option

pumactl (-p PID | -P pidfile | -S status_file | -C url -T token | -F config.rb) (halt|restart|phased-restart|start|stats|status|stop|reload-worker-directory)
    -S, --state PATH                 Where the state file to use is
    -Q, --quiet                      Not display messages
    -P, --pidfile PATH               Pid file
    -p, --pid PID                    Pid
    -C, --control-url URL            The bind url to use for the control server
    -T, --control-token TOKEN        The token to use as authentication for the control server
    -F, --config-file PATH           Puma config script
    -H, --help                       Show this message
    -V, --version                    Show version

[dirknilius]

Confirmed.

[klippx]

hear hear +1

Our workaround is to use bundle exec puma -C config/puma.rb

[ball-hayden]

@evanphx Thanks for fixing that.

Would it be worth adding a test for these arguments?