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

Hacktoberfest spam grammar nitpciks

Browse source
This commit is contained in:
Nate Berkopec 2020-10-01 07:35:57 -06:00
parent de632261ac
commit 0d354a4a52
No known key found for this signature in database
GPG key ID: BDD7A4B8E43906A6
2 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
docs/deployment.md
View file

@ -1,4 +1,4 @@
# Deployment engineering for puma
# Deployment engineering for Puma
Puma is software that is expected to be run in a deployed environment eventually.
You can certainly use it as your dev server only, but most people look to use
@ -7,12 +7,11 @@ it in their production deployments as well.
To that end, this is meant to serve as a foundation of wisdom how to do that
in a way that increases happiness and decreases downtime.
## Specifying puma
## Specifying Puma
Most people want to do this by putting `gem "puma"` into their Gemfile, so we'll
go ahead and assume that. Go add it now... we'll wait.
Welcome back!
## Single vs Cluster mode
@ -20,7 +19,7 @@ Welcome back!
Puma was originally conceived as a thread-only webserver, but grew the ability to
also use processes in version 2.
To run puma in single mode (e.g. for a development environment) you will need to
To run `puma` in single mode (e.g. for a development environment) you will need to
set the number of workers to 0, anything above will run in cluster mode.
Here are some rules of thumb for cluster mode:

2
docs/systemd.md
View file

@ -76,7 +76,7 @@ pass the `--keep-file-descriptors` flag. `bundle exec` can be avoided by using a
`puma` executable generated by `bundle binstubs puma`. This is tracked in
[#1499].
**Note:** Socket activation doesn't currently work on jruby. This is
**Note:** Socket activation doesn't currently work on JRuby. This is
tracked in [#1367].
To use socket activation, configure one or more `ListenStream` sockets