• 2x18k - mirrored ZFS pool.
• 1x47k - 2.5" drive from an old laptop used for torrents, temp data, non-critical pod volumes, application logs etc.
• 1x32k - automated backups from ZFS pool. It’s kinda partial mirror of the main pool.
• 1x18k - (NVME) OS drive, cache volumes for pods.

Instead of single pool, I simply split my drives into tiers: cache, storage, and trash due to limited drive counts. Most R/W goes to the cheap trash and cache disks instead of relatively new and expensive NAS drives.

LinkedIn?

I’m currently using InfluxDB + Telegraf + Grafana combination to monitor Linux systems and k3s pods. It’s basically same as Prometheus, but InfluxDB uses push model, which makes it easier to develop tools for collecting custom time series data.

For alerts and dashboards, I think Grafana is the simplest and most hassle free solution available at the moment.

I have a APC Back-UPS 1600VA. It powers two desktop PC/Server, a monitor, and router. So far, it gets the job done.

The biggest downside is; battery is not user replaceable, at least it’s not straight forward like the other models. If possible, prefer a UPS with the easy battery replacement option.

I was a backend developer for a startup company where:

• Windows servers without any firewall and security hardening.
• Docker swarm without WSL. We had to use 4 GB Windows base images for 50MB web apps.
• MSSQL without any replication and backups.
• Redis installed on Windows via 3rd-party tool that looked like a 2010 era keygen generator.
• A malware exploited the Redis * what a surprise * and kept killing processes to mine crypto on CPU…
• VPS provider forgot to activate new Windows Server on production and it kept restart for every 30 minutes until I checked the logs and notified them about the missing license.

I left there after 6 months.

Biggest difference is being able to execute INSTCMD commands, at least that was the main reason why I developed my own tool. Another less important differences are: older ARM support and since it’s written in Rust, it’s much more efficient in terms of resource usage. TBH, being that efficient only makes sense for very low-power devices.

Besides that, I don’t think you can go wrong with either project.

Thanks! I appreciate any kind of feedback.

Jiatan probably is in shambles right now. Poor guy spends years to infiltrate in a project and got caught. Meanwhile CrowdStrike took whole infrastructure down with a single update.

I’m actively using ollama with docker to run llama2:13b model. It’s generally works fine but heavy on resources as expected.

I recommend Obsidian with community plugins. Application itself isn’t open-source but your content stored as markdown files.