Thin boots instead of puma

Question

I'm trying to make a chat application deployed on a puma ec2 instance and have puma gem declared on my gemfile, but rails-websockets gem requires thin. For some reason when I start my server it uses thin instead of puma.

How to force my app to boot puma instead of thin?

I'm having issues since I cannot start a thread for web sockets, so I'm getting 500 error trying to access /websockets

score 0 · Accepted Answer · answered Nov 12 '14 at 10:11

Solved my issue chatting on the IRC with the gem developer that requires thin.

He gave me a alternative branch that its not used and Puma started to work normally.

Also, for my websocket problem, I used this guide to understand how my nginx works. So I entered these lines on my ec2 instance nginx config file:

location / {
        proxy_pass http://localhost:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
    }

so my conection could be updradable.

Thin boots instead of puma

1 Answers1