Skip to content

Conversation

@jacobherrington
Copy link
Contributor

Description

Personally, I think puma -C "-" is pretty opaque, but puma --no-config is a bit easier to understand at glance.

This is totally my opinion, but I feel like it's an improvement and doesn't risk changing the old behavior unintentionally.

I'm also not quite sure how to best test this, so if there are any suggestions I'm happy to jump on that!

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.

@nateberkopec
Copy link
Member

Seems good to me 👍 Thanks!

@nateberkopec nateberkopec merged commit 3b2eb69 into puma:master Sep 5, 2021
dentarg pushed a commit that referenced this pull request Sep 7, 2021
Related to #2689

[ci skip]
JuanitoFatas pushed a commit to JuanitoFatas/puma that referenced this pull request Sep 9, 2022
JuanitoFatas pushed a commit to JuanitoFatas/puma that referenced this pull request Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants