I stumbled on the fact that Puma has a raw tcp mode, also known as Lopez Express. This bypasses rack and provides access to the TCPSocket that’s just connected. Handy, because then puma can handle all the threading etc, and I just get a tcp socket to talk non-http to the client. What!? No http?! Are you mad??
No!! Well, maybe a little…
In fact I need to receive data from a microcontroller board. It doesn’t have sufficient CPU and memory to have an http stack. So we have to use tcp. However, the person implementing it also wants to use ssl. But not http. Yeah, puzzles me too.
I couldn’t find much by way of documentation, so here’s how to do a server for that using Puma:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35
And now (obviously after
gem install puma) you run it with
and you connect to it with
Provided your cert and key are correct and you have the CA root certificates
/etc/ssl/certs, that will also verify the cert. Now you say
enter and the server should tell you what you said.
And nobody else will know. Muahahaha!
As usual, please tell me if you find mistakes.