Skip to content
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.

Commit

Permalink
Post tweak for actions runner
Browse files Browse the repository at this point in the history
  • Loading branch information
brandonb927 committed Jun 10, 2024
1 parent 77a9478 commit 4d83839
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ In this post I talk about building a new machine to replace my aging [media serv

### Goodbye, Windows 10; Hello, unRAID

Since I built my original [media server]({{ site.url }}{% post_url 2017/2017-08-10-ultimate-media-server-setup %}) that was running Windows 10, I've been taking notes from the homelab community. Being a member of a Discord server started by some friends and former coworkers of mine centered around the topic opened by mind to the possibility of running Linux fulltime instead. I had toyed with the idea of this route initially setting up my previous server but was not comfortable with running Docker in that way at the time. Thinking back to my university days I knew it was possible because we hosted linux servers all the time, my issue was that I just didn't have the level of confidence in troubleshooting when it goes pear-shaped. After soliciting some advice in this endeavor from a few of the folks in said Discord, they all pointed me at something I had heard of while reading their conversations but had been unfamiliar with until now: [unRAID](https://docs.unraid.net/unraid-os/manual/what-is-unraid/).
Since I built my original [media server]({{ site.url }}{% post_url 2017/2017-08-10-ultimate-media-server-setup %}) that was running Windows 10, I've been taking notes from the homelab community. Being a member of a Discord server started by some friends and former coworkers of mine centered around the topic of maintaining a homelab opened by mind to the possibility of running Linux fulltime instead of being complacent with Windows. I had toyed with the idea of this route initially setting up my previous server but was not comfortable with running Docker in that way at the time. Thinking back to my university days I knew it was possible because we hosted linux servers all the time, my issue was that I just didn't have the level of confidence in troubleshooting when it goes pear-shaped. After soliciting some advice in this endeavor from a few of the folks in said Discord, they all pointed me at something I had heard of while reading their conversations but had been unfamiliar with until now: [unRAID](https://docs.unraid.net/unraid-os/manual/what-is-unraid/).

On paper, unRAID is one of those pieces of software that has all the features I've always wanted but never had the skills to put together into a single package. If you don't know, it's a linux operating system purpose-built for NAS-focused machines with RAID. It's popularity stems from its very large community of users, it has application support by way of Docker containers, a virtual machine manager, and developmental support for it through a [paid license structure](https://unraid.net/pricing). It's [very easy](https://old.reddit.com/r/unRAID/comments/16o4bvs/unraid_guide_for_noobs_made_by_a_noob/) to setup as it boots off a USB stick and runs entirely in RAM when it is operating. It even saves its own settings back to the flash drive so that in the event you need to remove the drive, all is not lost (however the drives in the array shouldn't be read by an OS without your unRAID config loaded as you may risk data loss).

Expand Down

0 comments on commit 4d83839

Please sign in to comment.