You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To run Puma locally, you must compile the native extension.
65
+
#### Compile the native extensions
66
+
67
+
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:
59
68
60
69
Ubuntu, macOS, etc:
61
70
```sh
@@ -67,6 +76,8 @@ Windows:
67
76
bundle exec rake -rdevkit compile
68
77
```
69
78
79
+
#### Run your local Puma
80
+
70
81
Now, you should be able to run Puma locally:
71
82
72
83
```sh
@@ -112,6 +123,18 @@ To run a single test with 5 seconds as the test case timeout:
112
123
TEST_CASE_TIMEOUT=5 bundle exec m test/test_binder.rb:37
113
124
```
114
125
126
+
#### File limits
127
+
128
+
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.
129
+
130
+
Check your file limit:
131
+
132
+
```
133
+
ulimit -Sn
134
+
```
135
+
136
+
We find that values of 4000 or more work well. [Learn more about your file limits and how to change them here.](https://wilsonmar.github.io/maximum-limits/)
0 commit comments