I’ve been meaning to write this post for a while and kept getting distracted. This evening I sat down and finally hammered it out. The goal is to share some of my favorite Ruby on Rails learning resources with the community. Let’s get started!
If you’ve been following my blog post series on the development of my ever so useful cat cam, powered by a Raspberry Pi, you’ll know I’ve made several attempts at a more stable and scalable streaming solution for my Cat Cam. As it stands today, I’ve been using Motion. While it’s a decent tool, Bandwidth has been my primary concern and I’d like to be able to stream real-time without sucking up what measly bits my ISP gives me if more than a few folks decide to show interest.
It takes a lot for a movie to convince me to write a blog post about it. I generally don’t do movie reviews, and this isn’t one. What this is, is a reflection; a documentation of experiences and feelings. For the next few minutes, I want to pour myself out just a bit.
In the process of trying to figure out the best streaming solution for my cat cam, I had to deviate a bit. I combined my RTMP server for my cat cam and Web server for john.ly into one and the latter didn’t have the RTMP module installed. This module is required for my attempts to push H.264 video and have Nginx relay it to whomever is watching, cutting down on the bandwidth of my one-to-one reverse proxy setup I have, now.
I’ve been waiting to review Appletieser for some time and now that sometime is Friday afternoon. In the past, I’ve been blocked by cost-prohibition and the fact that the first time I tried ordering it, Amazon sent me Grapetiser. If you haven’t read that post, yet, go do it. Now.
This a follow up from this article I wrote talking about trying to get
ffserver running the Cat Cam. I abandoned that project and went in search for a new solution. What I came up with was
nginx. Here’s how that worked out.
Before I begin this seriously long-winded article (I wasn’t expecting it to be nearly 4000 words), I want to let you know that after roughly six hours of poking, yelling at myself, yelling at my screen, yelling at Google for not having the answers I need1, and wishing I had just bought IP cameras, I realized
ffserver doesn’t send
mjpeg with the right
Content-type header for browser viewing, thus said browsers don’t do the right thing to it.2