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

pumactl does not understand -F nor --config-file option #694

Closed
yld opened this issue Apr 27, 2015 · 0 comments
Closed

pumactl does not understand -F nor --config-file option #694

yld opened this issue Apr 27, 2015 · 0 comments

Comments

@yld
Copy link

yld commented Apr 27, 2015

-F or --config-file option should be allowed

# pumactl --help                 
Usage: 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

But they are not:

# pumactl -F config/puma.rb start 
* Pruning Bundler environment
(...)puma-2.11.1/lib/puma/cli.rb:295:in `parse_options': invalid option: -F (OptionParser::InvalidOption)
(...)
BenV pushed a commit to BenV/puma that referenced this issue Aug 14, 2015
unageanu added a commit to unageanu/docker-jiji2 that referenced this issue Mar 4, 2016
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

1 participant