kotovalexarian-likes-github/puma--puma
1
0
Fork 0
mirror of https://github.com/puma/puma.git synced 2022-11-09 13:48:40 -05:00
Code Releases Activity
puma--puma/CONTRIBUTING.md
Olle Jonsson c7613e334e
Drop stray backslash in Markdown (#2815) 
[ci skip]
2022-01-30 12:13:42 +01:00

7.8 KiB
Raw Blame History

Contributing to Puma

By participating in this project, you agree to follow the code of conduct.

There are lots of ways to contribute to Puma. Some examples include:

Newbies welcome! We would be happy to help you make your first contribution to a F/OSS project.

Setup

First step: join us on Matrix at #puma-contrib:matrix.org

Clone the repo

Clone the Puma repository:

git clone git@github.com:puma/puma.git && cd puma

Ragel

You need to install ragel (use Ragel version 7.0.0.9) to generate Puma's extension code.

macOS:

brew install ragel

Linux:

apt-get install ragel

Windows (Ruby 2.5 and later):

ridk exec pacman -S mingw-w64-x86_64-openssl mingw-w64-x86_64-ragel

Install Ruby dependencies

Install the Ruby dependencies:

bundle install

Compile the native extensions

To run Puma locally, you must compile the native extension. Running the test rake task does this automatically, but you may need to manually run the compile command if you want to run Puma and haven't run the tests yet:

Ubuntu, macOS, etc:

bundle exec rake compile

Windows:

bundle exec rake -rdevkit compile

Run your local Puma

Now, you should be able to run Puma locally:

bundle exec bin/puma test/rackup/hello.ru
# -or-
bundle exec ruby -Ilib bin/puma test/rackup/hello.ru

Alternatively, you can reference your local copy in a project's Gemfile:

gem "puma", path: "/path/to/local/puma"

See the Bundler docs for more details.

Running tests

To run the entire test suite:

bundle exec rake test:all

To run a single test file:

bundle exec ruby test/test_binder.rb

You can also run tests with m:

bundle exec m test/test_binder.rb

To run a single test:

bundle exec m test/test_binder.rb:37

To run a single test with 5 seconds as the test case timeout:

TEST_CASE_TIMEOUT=5 bundle exec m test/test_binder.rb:37

File limits

Puma's test suite opens up a lot of sockets. This may exceed the default limit of your operating system. If your file limits are low, you may experience "too many open file" errors when running the Puma test suite.

Check your file limit:

ulimit -Sn

We find that values of 4000 or more work well. Learn more about your file limits and how to change them here.

How to contribute

Puma could use your help in several areas!

The contrib-wanted label indicates that an issue might approachable to first-time contributors.

Reproducing bug reports: The needs-repro label indicates than an issue lacks reproduction steps. You can help by reproducing the issue and sharing the steps you took in the comments.

Helping with our native extensions: If you are interested in writing C or Java, we could really use your help. Check out the issue labels for c-ext and JRuby.

Fixing bugs: Issues with the bug label have working reproduction steps, which you can use to write a test and submit a patch.

Writing features: The feature label highlights requests for new functionality. Write tests and code up our new feature!

Code review: Take a look at open pull requests and offer your feedback. Code review is not just for maintainers. We need your help and eyeballs!

Write documentation: Puma needs more docs in many areas, especially where we have open issues with the docs label.

Reproduction steps

Reproducing a bug helps identify the root cause of that bug so it can be fixed.

To get started, create a rackup file and config file and then run your test app with:

bundle exec puma -C <path/to/config.rb> <path/to/rackup.ru>

For example, using a test rack app (test/rackup/hello.ru) and a test config file (test/config/settings.rb):

bundle exec puma -C test/config/settings.rb test/rackup/hello.ru

There is also a Dockerfile available for reproducing Linux-specific issues:

docker build -f tools/Dockerfile -t puma .
docker run -p 9292:9292 -it puma

Pull requests

Code contributions should generally include test coverage. If you aren't sure how to test your changes, please open a pull request and leave a comment asking for help.

There's no need to update the changelog (History.md); that is done when a new release is made.

Puma uses GitHub Actions for CI testing. Please consider running the workflows in your fork before creating a PR. It is possible to enable GitHub Actions on your fork in the repositories' Actions tab.

Backports

Puma does not have a backport "policy" - maintainers will not consistently backport bugfixes to previous minor or major versions (we do treat security differently, see SECURITY.md.

As a contributor, you may make pull requests against -stable branches to backport fixes, and maintainers will release them once they're merged. For example, if you'd like to make a backport for 4.3.x, you can make a pull request against 4-3-stable. If there is no appropriate branch for the release you'd like to backport against, please just open an issue and we'll make one for you.

Join the community

If you're looking to contribute to Puma, please join us on Matrix at #puma-contrib:matrix.org.

Bibliography/Reading

Puma can be a bit intimidating for your first contribution because there's a lot of concepts here that you've probably never had to think about before - Rack, sockets, forking, threads etc. Here are some helpful links for learning more about things related to Puma: