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

Are puma and pumactl unnecessary duplicates? #2244

Closed
anon987654321 opened this issue May 1, 2020 · 2 comments
Closed

Are puma and pumactl unnecessary duplicates? #2244

anon987654321 opened this issue May 1, 2020 · 2 comments
Labels

Comments

@anon987654321
Copy link

Is it just me or is there some inconcistency between the startup options in puma and pumactl? Some switches are missing, some named differently etc.

Wouldn't it be simpler if pumactl was just a wrapper for the puma command, except ofcourse with the additional daemon management options?

Or maybe pumactl is deprecated, and one is supposed to just use puma combined with the --daemon switch and some kill tool?

Thanks!

@dentarg
Copy link
Member

dentarg commented May 2, 2020

There might be some inconsistencies, I think the CLI tools have just grown organically with contributions to the Puma project.

Please note that daemonization (--daemon) has been removed (#2170, #1983) from the master branch and will not be in the next release of Puma (5.0). So it is probably wise to adjust your deployment after that.

@anon987654321
Copy link
Author

Gonna cram all this stuff into a new feature request and do my best to help once I become skilled enough.

Please not that daemonization (--daemon) has been removed (#2170, #1983) from the master branch and will not be in the next release of Puma (5.0). So it is probably wise to adjust your deployment after that.

Awesome, thanks for the heads up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants