The solutions you’ve mentioned aren’t exactly equivalent. Proxmox is a hypervisor while Docker Swarm and Kubernetes are container orchestration engines. For example, I use Proxmox in a highly available cluster running on three physical nodes. Then I have various VMs and LXC containers running on those nodes. Some of those VMs are Kubernetes nodes running many Docker containers.
I highly recommend Proxmox as it makes it trivial to spin up new containers and VMs when you want to test something out. You can create and destroy VMs in an instant without messing with any of your actual hardware. That’s the power of a good hypervisor.
For orchestration, I would actually recommend you just stick with Docker Compose if you want something very simple to manage. Resiliency or high-availability usually brings with it a lot of overhead (both in system resources as well as maintenance costs) which may not be worth it to you. If you want something simple, Proxmox can run VMs in a highly-available mode so you could have three Proxmox nodes and set any VMs you deem essential to be highly-available within the cluster.
For my set up, I have certain services that are duplicated between multiple Proxmox nodes and then I use failover mechanisms like floating IP addresses to automatically switch things over when a node goes down. I also run most things in Kubernetes which is deployed in a highly-available manner across multiple Proxmox nodes so that I can lose a physical node and still keep (most) of my services running. This however is overkill for most things and I really only do it because I use my homelab to learn and practice different techniques.
TERRAMASTER F2-223 2Bay NAS Storage – High Performance for SMB with N4505 Dual-Core CPU, 4GB DDR4 Memory, 2.5GbE Port x 2, Network Storage Server (Diskless) a.co/d/iT25GwL
I thought it was quite simple but it depends on your experience of course. It’s a single binary and a single config file, so I felt it was soo much simpler.
You can buy a good udemy course for 10 dollars too which really helps in the beginning.
Yea it’s very easy to learn enough to run, it has built-in service discovery and secrets now, and writing parameterized jobs feels so much nicer than a helm chart in k8s.
I’m kind of excited for LubeLogger, since all the other fuel/maintenance trackers are going down the drain. Currently using Fuelio but I’m not a huge fan.
I’m using terramaster as hdd enclosure. I have two of those, both connected to lenovo thinkcentre. I’ve tried rpi but I needed more power hence the lenovo thingy.
There are a few different components to RSS. The feed (in this case Instagram or something like webtoons), an aggregator (the software that pulls in all the feeds you’re interested in and keeps track of things like read status), and a client (the actual interface you interact with to read your feeds)
A lot of time, the aggregator will include a web client you can use, so these can be bundled together. But, because RSS is an open specification, you could use a client other than the one that comes with an aggregator. Examples of this are Miniflux or FreshRSS. If you’re interested in Nextcloud, there is also an RSS plugin for that
The other part, the feed, is often provided by a website directly. Webtoons does this for instances. For each comic, there is a URL that points to the feed. Some sites will have a little RSS icon that direct you to the feed. While other sites will have you manually add a something likr “/rss” or “/atom.xml” to find that feed
But other sites, like Instagram, don’t provide feeds directly. To get those feeds, you’ll need some kind of service that scrapes content from Instagram and creates a feed from that. I’m sure there are selfhosted options for this, but because the original content had to come from a third party anyway, I don’t mind using a public service to create feeds for me. I personally use openrss.org, which doesn’t require an account to use, though I’m sure there are others as well. It has support for Instagram and a bunch of other sites too. I will warn that by the nature of having a service that scrapes another, things may break sometimes. I don’t follow any Instagram feeds through openrss, but I have some other sites/feeds that I do get through them and am generally happy with it
TLDR: Put something like Miniflux on your server and add the Instagram feeds you want through openrss.org to Miniflux
But other sites, like Instagram, don’t provide feeds directly. To get those feeds, you’ll need some kind of service that scrapes content from Instagram and creates a feed from that. I’m sure there are selfhosted options for this
yeah, once you have the drives, building the rest of the system can be done for dummy cheap if you look at like cheap used workstations that some company or school is offloading. and it would still probably be a more capable system all around.
I ripped out the control board of the 2x bay toaster and then bought some sata extension cables (with power) for 2x HDDs. 3D printed a little drive bay type thing and then slapped the raspi on top with the usb controller. It works great!
Works for my usecase of basic NAS /SMB /SFTP and I can stream 1080p etc.
But would look to sata in the future also like you mention, couldn’t find a hat, but USB speeds are fine for me.
First of all, you will never achieve usb3 full theoretical speed. Its just not going to happen. Even if you could though you wouldn’t be able to get full speeds because your bandwidth is split between devices. You will be sharing the bus between plugged in devices along with on board hardware devices.
A USB 3.2 gen 1 connection (5 Gb/s) is still plenty for multiple HDDs AND when you have no need for compute on the NAS the network Link is the relevant bottleneck which is half of the USB connection.
Then USB 3.2 gen 2 (10 Gb/s) interfaces on HDD enclosures get more common every day which gives even more headroom with little more expenses.
selfhosted
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.