fmstrat

Really wish the DLC for this was still available. Slay away Camp is good, but this was so much better and I missed out on the DLC..

Hi all,

I've been running a bunch of services in docker containers using Docker Compose for a while now, with data storage on ZRAID mirrored NVME and/or ZRAID2 HDDs.

I've been thinking about moving from my single server setup to three micro-servers (Intel N150s), both for redundancy, learning, and fun.

Choosing Kubernetes was easy, but I'd like to get some outside opinions on storage. Some examples of how I'm using storage:

1. Media and large data storage: Currently on the ZRAID2 HDDs, will stay here but be migrated to a dedicated NAS
2. High IO workloads like Postgresql and email: Currently running on the NVMEs
3. General low-volume storage: Also currently on NVMEs, but different use case. These are lower IO, like data storage for Nextcloud, Immich, etc

I'm a huge fan of being able to snapshot with ZFS, as I mirror all my data off-site with hourly pushes for some container data, and daily for the rest. I'd like to be able to continue this kind of block-level backups if possible.

Assume I'm a noob at Kubernetes storage (have been reading, but still fresh to me). I'd love to know how others would set up their storage interfaces for this.

I'm trying to understand if there's a way to have the storage "RAIDed" across the drives in the three micro-servers, or if things work differently than I expect. Thanks!

Hi all,

Working through some things like a Will (I am fine, just normal life planning), and debating on methods for digital management when I do die.

I run a lot of self-hosted services for family and friends, all on secured servers with ZFS and on/off site backups. Key ingredient is Vaultwarden for password management.

I'd like to put something in place so that encryption keys, some docs, and key passwords are released to a tech savvy friend. Anyone know of existing solutions for this?

Requirements of:

• Not providing keys to a third-party beforehand
• Not forgeable to open
• If possible, no "weekly press a button"

I'm thinking some kind of key pair where my friend has the private key and the public key is provided to a family member, and when activated a timer starts where I could cancel the release.

Hey all,

Anyone familiar with the state of Raptor Lake performance + efficiency cores in Linux? I'm specifically curious about how the kernel balances things when running multiple containers (without pinned CPUs)

Thanks!

There's a part as a sniper, I think, and maybe it was third person mostly? The name was initials that remind me of XKCD, like that sound, but probably 3 letters. And I feel like the character wore white cloths. PC game. This is a stretch.

It has fInally happened. And Technology Connections approves.

cross-posted from: https://lemmy.nowsci.com/post/9782596

Hi all,

I've finally gotten around to releasing these formally after much testing of prints and usage.

The Twystlock system is a set of 100% 3D printable gaming accessories that require no printed supports or additional parts. This means no springs to buy and no metal elements to melt in, just access to a 3D printer and a bit of super glue. Originally designed for the Steam Deck, these accessories can be applied to the case of any mobile gaming device.

The Twystlock connector itself is designed as a quick-connect that secures parts together with a simple twist motion, can be fully recreated with affordable home-based 3D printers, and doesn't require complicated supports to print. The first use of this connector has been for the Steam Deck, specifically to supply an alternative accessory platform that is more accessible to the everyday 3D printing hobbyist, however it could be utilized as a connector in almost any environment.

Feel free to download what you like, and if you would like to request a new accessory design, or vote on the next accessory to be created, please visit our Lemmy community at https://lemmy.world/c/twystlock@lemmy.nowsci.com.

All the posts about Reddit blocking everyone except Google and Brave got me thinking: What if SearNGX was federated? I.E. when data is retrieved via a providers API, that data is then federated to all other instances.

It would spread the API load out amongst instances, removing the API bottlenecks that come from search providers.

It would allow for more anonymous search, since users could cycle between instances and get the same results.

Geographic bias would be a thing of the past.

Other than ActivityPub overhead and storage, which could be reduced by federating text-only content, I fail to see any downside.

Thoughts?

Almost 30 more minutes of dishwasher.

Hi all, I'm a Lemmy FOSS app contributor that's made a couple of tools for people starting small instances including Lemmy Community Seeder (LCS) for building content on new server's All Feeds and Lemmy Post Purger (LPP) for clearing old posts on smaller instances.

Today I'm releasing Lemmy Defederation Sync (LDS). When launching a new Lemmy instance, administrators may not understand the necessity of defederation with problem instances. Using LDS, you can sync your instance's "blocked instance" list with that of another server(s) whose admins you trust.