puma – Tarik Billa

How do I get ‘puma’ to start, automatically, when I run `rails server` (like Thin does)

December 30, 2023 by Tarik

After some digging, I’ve found this answer: https://stackoverflow.com/a/14911994/604526 To make Puma the default, paste this code into script/rails above require ‘rails/commands’: require ‘rack/handler’ Rack::Handler::WEBrick = Rack::Handler.get(:puma) Puma is the default server now if you use rails s rails s => Booting Puma => Rails 3.2.12 application starting in development on http://0.0.0.0:3000 => Call with -d … Read more

ActiveRecord::ConnectionTimeoutError: could not obtain a database connection within 5.000 seconds (waited 5.000 seconds)

December 6, 2023 by Tarik

I had the same problems which were caused by too many open connections to the database. This can happen when you have database queries outside of a controller (in a model, mailer, pdf generator, …). I could fix it by wrapping those queries in this block which closes the connection automatically. ActiveRecord::Base.connection_pool.with_connection do # your … Read more

How can I serve requests concurrently with Rails 4?

December 3, 2023 by Tarik

I invite you to read about the configuration options of config.threadsafe! in this article Removing config.threadsafe! It will help you to understand better the options of config.threadsafe!, in particular to allow concurrency. In Rails 4 config.threadsafe! is set by default. Now to the answer In Rails 4 requests are wrapped around a Mutex by the … Read more

Why do I need Nginx with Puma?

September 9, 2023 by Tarik

Nginx is a web server and puma is an application server. Both have their advantages, and you need both. Some examples: Static redirects- you could setup your nginx to redirect all http traffic to the same url with https. This way such trivial requests will never hit your app server. Multipart upload- Nginx is better … Read more

puma gem – Failed to build gem native extension

July 27, 2023 by Tarik

Try the following gem install puma — –with-cppflags=-I/usr/local/opt/openssl/include bundle install You can also specify the gem version, like the following: gem install puma -v ‘2.11.3’ — –with-cppflags=-I/usr/local/opt/openssl/include

Connecting to WSL2 server via local network [closed]

June 19, 2023 by Tarik

See this video, it helped me: netsh interface portproxy add v4tov4 listenport=<port-to-listen> listenaddress=0.0.0.0 connectport=<port-to-forward> connectaddress=<forward-to-this-IP-address> for example netsh interface portproxy add v4tov4 listenport=3000 listenaddress=0.0.0.0 connectport=3000 connectaddress=172.30.16.3 Microsoft has published a little bit of information about this on their WSL1 to WSL2 comparison page

How to restart puma after deploy?

April 27, 2023 by Tarik

You can restart manually using the following command bundle exec pumactl -P /home/deploy/.pids/puma.pid restart Make sure you point to the correct pid path.

What is the difference between Workers and Threads in Puma

February 12, 2023 by Tarik

As the other answer states, this Heroku article is pretty good with explanations of certain configuration items. However if you need to tune your application on Heroku, or anywhere, then it pays to know how things work. I think you are almost correct when you say “a worker is a thread inside the puma process”, … Read more

Rails: Address already in use – bind(2) (Errno::EADDRINUSE)

November 14, 2022 by Tarik

You need to use kill -9 59780 with 59780 replaced with found PID number (use lsof -wni tcp:3000 to see which process used 3000 port and get the process PID). Or you can just modify your puma config change the tcp port tcp://127.0.0.1:3000 from 3000 to 9292 or other port that not been used. Or … Read more

NGINX: upstream timed out (110: Connection timed out) while reading response header from upstream

October 18, 2022 by Tarik

This happens because your upstream takes too long to answer the request and NGINX thinks the upstream already failed in processing the request, so it responds with an error. Just include and increase proxy_read_timeout in location config block. Same thing happened to me and I used 1 hour timeout for an internal app at work: … Read more