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

Adds a --silent option to the CLI #2803

merged 3 commits into from Jan 19, 2022


Copy link


This PR adds a -s, --silent option which deactivate Puma messages displayed on the prompt.

Without the option:

$ bundle exec bin/puma test/rackup/
Puma starting in single mode...
* Puma version: 5.5.2 (ruby 2.6.6-p146) ("Zawgyi")
*  Min threads: 0
*  Max threads: 5
*  Environment: development
*          PID: 88245
* Listening on
Use Ctrl-C to stop
^C- Gracefully stopping, waiting for requests to finish
=== puma shutdown: 2022-01-18 16:38:07 +0100 ===
- Goodbye!

With the option:

$ bundle exec bin/puma --silent test/rackup/

Your checklist for this pull request

  • I have reviewed the guidelines for contributing to this repository.
  • I have added (or updated) appropriate tests if this PR fixes a bug or adds a feature.
  • My pull request is 100 lines added/removed or less so that it can be easily reviewed.
  • If this PR doesn't need tests (docs change), I added [ci skip] to the title of the PR.
  • If this closes any issues, I have added "Closes #issue" to the PR description or my commit messages.
  • I have updated the documentation accordingly.
  • All new and existing tests passed, including Rubocop.

Copy link

Do we really want to silence STDERR?

Copy link
Contributor Author

Good catch, might want to leave the stderr as it is

Copy link

Using @events =, STDERR seems to work, as errors are written.

I think the test will always pass, as Puma::Events.null.class or any call to will have a class of Puma::Events.

Not sure about this, let's see what others think...

Copy link

Agree with Greg. Also, isn't this option usually called quiet?

Copy link

dentarg commented Jan 18, 2022

Puma has -q, --quiet, but it is used to silent the request logging (and it is on by default), from puma --help,

-q, --quiet                      Do not log requests internally (default true)

(we have -v, --log-requests to turn it on)

Copy link
Contributor Author

I've reverted the stderr not to be silent as suggested.

Copy link

Change looks super clean. Glad this wasn't too hard to implement.

@nateberkopec nateberkopec merged commit 3f3c2f6 into puma:master Jan 19, 2022
@gottfrois gottfrois deleted the silent-opts branch January 20, 2022 08:57
JuanitoFatas pushed a commit to JuanitoFatas/puma that referenced this pull request Sep 9, 2022
* Adds a --silent option to the CLI

* Fixes silent opt not to silence stderr

* Removes un-used arg variable from CLI opt block handler
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

4 participants