For that workload? I quite literally run more than that on a (le)potato

That’s not even to mention declarative, rootless, podman containers via systemd or quadlet (the containers, too, can be NixOS)!

NixOS Containers can also be a good option if you don’t care about rootless.

Apparently I’m in the minority, but I love Logseq. I’ve used it with Syncthing for personal notes and grad school for the past three years with no hiccups. Maybe my success with it is partially due to nested bullet points already being how my brain works but the default paradigm is perfect for me.

The plain markdown files are organized reasonably, so I can straight up use Vim as my notes editor if I want.

Tags (#) create a new page to easily circle back to topics later without interrupting your thought pattern to make that structure manually. Once you leave edit mode for the line the tag becomes a link to that page. Some of my favorites are #clothes-that-fit (where I can easily embed a picture of the tag of what I’m trying on to look for deals online later), or #reading-list.

It’s just so useful.

I haven’t experienced that at all and I embed all kinds of pictures and links in my 2-3 years of grad school + personal notes. How many is “a lot” to you?

If it genuinely is a logeq problem did you ever try splitting notes into multiple graphs for different topics?

if you could start again in your self hosting journey, what would you do differently? :)

That’s an excellent question.

If I were to start over, the first thing that I would do is start by learning the basics of networking and set up a VPN! IMO exposing services to the public internet should be considered more of an advanced level task. When you don’t know what you don’t know, it’s risky and frankly unnecessary.

The lowest barrier to entry for a personal VPN, by far, is Tailscale. Automatic internal DNS and clients for nearly any device makes finding services on a dedicated machine really, really, easy. Look into putting a tailscale client right into the compose file so you automatically get an internal DNS records for a service rather than a whole machine.

From there, play around with more ownership (work) with regard to what can touch your network. Switch from Tailscale’s “trusted” login to hosting your own Headscale instance. Add a PiHole or AdGuard exit node and set up your own internal DNS records.

Maybe even scrap the magic (someone else’s logic that may or may not be doing things you need) and go for a plain-Jane Wireguard setup.

Another +1 from me. Very similar setup and it’s been working for me for years.

Kind of. Synthing-fork is alive and well.

OpenScale works great and kind of does what you want. If you have an old Android phone laying around you can have it persistently connected to a cheap Bluetooth scale. Functional, but at a much have higher power cost than an ESP32 solution. Automated database exports to a local file (on the android device) and Syncthing can move your data around for analysis.

The good folks over at Gadgetbridge might have a solution too, although their list of supported scales looks pretty short.

You might also look into making a project like rmfakecloud to trick your Fitbit device into pushing data to a local server.

Not sure about home assistant though, I’ve never used it.

I prefer Syncthing-fork for some more straightforward configuration. Mainly the three button options equating to “follow the run conditions, damnit”, “run damnit”, and “stop damnit”

If you want a device to do NFC payments you’ll need to look somewhere other than GrapheneOS. (Believe me, I’ve tried everything)

https://discuss.grapheneos.org/d/475-wallet-google-pay

Even faster – tailscale. For a cheeky way to play with your friends make a burner account with a shared login to get on the same tailnet for free. On the endpoints, turn off tailscale-ssh and any of their other “features” you don’t need.

GrapheneOS! I’ve been using it for a few years. Never going back.

Is this some Network Allowed problem that I’m too Network Not Allowed to understand?

Second this ^

I have one and it’s fine, but not directly supported by OpenWRT. Looks like Beryl and Slate are though