fmstrat

It's 6:30 hands down.

Hi everyone,

I've been a single-server built from whatever desktop I upgraded for years kind of guy, with a hostname of the street it is on (better than server, which is what it used to be).

However, at some point in the future my home lab will be located in a place I will not have immediate access to, and since it's getting on in age and due for an upgrade anyway, I'm going to build in some redundancy. So, current names:

• OPNsense micro-router: ingress01
• OPNsense backup: ingress02
• Cluster micro-server with essential services: cluster01
• Cluster micro-server with non-essential services and replicated essential services: cluster02
• NAS: nas
• Powered on remotely when needed:
  • Mac mini dev/release box: macmini
  • Primary remote development server (basically my old desktop): desktop

Bring on the Mini-MacMinifaces, and any other ideas you have.

The GitHub repos at https://github.com/organicmaps are all public archives now, but there's no information on them about why.

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

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!

Since you all liked the tent on the coast, I thought you might also enjoy this sighting. We spotted this species of comfort camper in the wild while we were up there.

Since I agree with @Cirelo@lemmy.world, I will contribute, too. I however, love the snow and ice for camping, hiking, backpacking, whatever.

This was taken on the coast after backpacking through the Olympics in Washington State.

Hey all,

I'm de-googling, and while OctoApp (to control OctoPrint) is open source (https://gitlab.com/realoctoapp/octoapp), there are no APKs in the releases like the README says. I can't report this as an issue because that's turned off on GutLab, so does anyone know of any other way it is distributed outside of thr Play Store?

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.

So I haven't run a custom ROM for a long time and I'm thinking of trying out GrapheneOS. Before I do, is there a modern way to take a full disk image of a stock Pixel 8? The intent would be to factory restore to where I am in this moment if need be.

I use Ollama with continue.dev in code-server, and I wanted a way to hit Cntrl-Shift-Alt-T to get a "top" of sorts that would show CPU, IO, GPU, loaded models, and logs, all in one place quickly.

Set up the below screenrc file and created the shortcut above in Debian. Tab switches between CPU and IO, and Cntrl-a q quits all screens and closes the Gnome shell.

Screenrc:

termcapinfo xterm* ti@:te@
startup_message off
defscrollback 10000

bind q eval "kill" "quit"
caption always "%{= rw}%-w%{= KW}%n %t%{-}%+w"
defbce on

# Start htop and focus
screen -t "HTop" htop
focus

# Split horizontally to put nvtop under htop
split
focus
screen -t "NVTop" nvtop

# Split vertically to put ollama next to nvtop
split -v
focus
screen -t "Ollama PS" watch -n5 'docker exec -ti ai-ollama ollama ps'

# Split horizontally to put logs underneath ps
split
focus
screen -t "Ollama logs" bash -c "docker logs -f --tail 100 ai-ollama | grep -Ev '\"/api/ps\"|\"/\"'"

# Resize PS, then get back to logs
focus up
resize -v 6
focus down

# Get back to htop
focus

The atop script that runs with Cntrl-Alt-Shift-T:

#!/usr/bin/env bash

if [ "${1}" = "new" ]; then
    gnome-terminal --geometry=200x50+0+0 --maximize -- /data/system/bin/atop
else
    screen -c /data/system/setup/common/screenrc-status
fi

Happy to share my htop config as well if anyone wants it.

Since everyone here seemed to like my Pegboard designs, I figured I'd share this as well. When making the Only Sensor (see the home automation community or my site), I used this Solder Fume Extractor to keep my lungs nice and clean.

Fully 3D printable, and a full bill or materials on the link. Enjoy!

Hrm, not sure why the image returned a logo, but here it is:

https://nowsci.com/diy-solder-extractor