I appreciate the hard work that goes into poal and vid8.
I'm on my own journey into self hosting. I run a few websites myself and recently discovered how consolidated hosting became. I therefore decided to build out my own data center. Keep in mind when I say data center, I'm talking about a single 10U rack containing everything I need. All I need is a single RJ45 connection and 110 volt line.
The servers is a cluster of Raspberry Pis. Before you laugh hysterically, the goal is to build a simple, cheap, self contained web server cluster. So far, the performance is quite good. When I run bench marks with small loads, I'm getting sub second page loads.
The software architecture is to use one Pi as a reverse proxy using Apache. Amazingly enough, I discovered Apache has built in reverse proxy, load balancing, fail over and many other features I had never known because I only cared about its one feature of serving web pages.
I'm now going through the dance of configuring it to use http2. I had no idea it was capable of that either. The real challenge here is to ensure http2 is supported from the reverse proxy all the way to the source. I think once I have http2 working all the way through the chain, the performance will improve more.
In short, I realize there is a lot to building a fast website and also making it reliable. Raspberry Pis are not high performance servers but they are cheap, use only 3 watts or less and very capable of serving multiple websites over a single gigabit connection.
I take it you're not looking to have thousands of concurrent users. In that case, yeah rPis are fine.
Correct. Most of my sites are small businesses and typically have under 100 connections per day.
I used to dev poal on a pi2, was working perfectly fine.
What's the full url? Vid8.?
It was a local instance I migrated to a VM (better performance, especially for node/webpack)
(post is archived)