Adventures in homelabbing and other goofy computer stuff.
2019-12-20 - I recently got my hands on a Ryzen chip. I’m going go test how well it works with the stuff below and see if I can’t come up with a better, cheaper ingest machine. I’m curious as to how well that $50 Athalon machine would handle pulling all of this off, as that’d make a strong case for a sub $200 ITX build that could fit in a bookbag and eliminate the need for us having a big tower on stage all the time.
2019-12-20 - I’ve gotten a lot of requests for a follow up. Glad to help! I’m finally getting around to writing the follow up posts and they should hopefully be up in a week or two.
Up until this point, I’ve been using my Guacamole server to SSH in to my web server and edit my posts using Vim. I use VSCode for basically everything else, so it’d be way more convenient to edit my posts in that, and then use git to push them to my server and have Jekyll automatically rebuild the site. Having the option to use HTTP as well as SSH is preferable considering I do a lot of work away from my main laptop, and SSH isn’t always an option.
I’m going to assume you already have a working nginx installation. There are a lot of other tutorials out there that explain this better than I could. I’d suggest this one from DigitalOcean. You’ll also need git installed. If you don’t have it, run:
yum install git-core
To start, you’ll want to get a git directory set up. I chose to use /var/git as my root. htpasswd will generate an htpasswd file for something to authenticate against.
mkdir /var/git htpasswd -c /etc/nginx/htpasswd <user name> chown -R nginx:nginx /var/git chmod 700 /etc/nginx/htpasswd
CentOS 7 doesn’t offer fcgiwrap in its repos, so we’ll have to build it from source.
yum install fcgi-devel spawn-fcgi git clone https://github.com/gnosek/fcgiwrap.git cd fcgiwrap autoreconf -i ./configure make make install
fcgiwrap should have compiled and should now exist at /usr/local/sbin/fcgiwrap. Now we need to configure /etc/sysconfig/spawn-fcgi to start fcgiwrap.
It begins. I’m finally getting to a point that I’d consider “ready”. So currently, I have three servers set up as virtualization hosts with XCP-ng. I was planning on using ESXi, but XCP-ng offers me the option to run the latest version on nearly any piece of kit I throw at it without having to worry about version incompatibility and the like. Had I gone with ESXi, I’d have the PE1900 on 4.x and the other two on 5.5, missing out on all the relevant features added in 6.x. Nope. I try to run the PE1900 as little as possible because even with the L5335s I dropped in there, it still slurps power like crazy. The rack and rails are in the mail, so the R310 and my networking gear can finally move from their temporary home on or next to an old end table I have down in the basement to their permanent home in the laundry room. I’m sure the girl will appreciate not having a line hanging out of a ceiling tile to get the AP over to the router anymore.
As it stands right now, I’m okay with how things are, for the most part. Since I’m on a pretty stringent budget, I’m limited on expansion, but there’s only a few more pieces I want to add before I’d consider the setup to be the ideal minimum.