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.

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.

Avoid AMD? Why do you say that?

My solution is to use Rathole. I rent a wildly cheap (2 core, 4GB memory) VPS and basically just run Traefik there. Then I use Rathole to make some services hosted on my desktop available to Traefik.

I like this solution better than Wireguard for my application. It reduces attack surface to services you’ve explicitly set up, rather than a full data layer trunk between your machine and a potential malicious actor.

Ooh, I’ll definitely check out Voice!

I’m more of a desktop Jellyfin container person myself, but all roads lead to Rome in this case :) thanks for the input!

Does anyone know of a good alternative for Android?

Right now I just use Antennapod, but it would be nice to get chapters and whatnot built in.

My $0.02:

NixOS is excellent, and actually pretty easy if you’re not trying to do anything fancy (running all services under a single user, etc.). Personally this is my pick because I primarily host services for myself, so down time in exchange for learning a new thing is acceptable.

As I mentioned elsewhere, Debian + Incus is a great minimal and rock solid solution for longer standing services. Although, it’s not composeable :(

More directly to your preferences, I would also recommend considering Rocky. Being in the RHEL ecosystem has its perks (especially with rootless support for podman and podman-compose). I’m also generally a fan of SELinux. Rocky is a little less bleeding edge than Fedora with many of the same conveniences and recent packages. In my mind, for my purposes, that makes it a better choice than Fedora for a server OS.

Good bot

I tend to not use the webui, so I prefer the similarly useful combination of Debian + Incus (spawned from the LXC project).

Sure, HA isn’t baked into Incus (to my knowledge) but similar to OP I only have one physical box and don’t necessarily care to manage multiple.

That being said, Proxmox is a good solution in the scheme of things and generally a good recommendation.

Hm, so it’s encrypted from your beeper client to the bridge, decrypted, then re-encrypted with the outgoing platform’s protocol. Seems like a good reason to host your own bridge, and a good call on it being a glaring attack surface.

Seems like the secret sauce is in how they deal with messaging platform integrations? Maybe the goal is to avoid another iMessage lawsuit. With Beeper as a proof of concept it would be cool to start adding integrations in a fully open source way (legality permitting)

That’s a cool solution! I’d be interested in making a nix flake to do something similar to that Ansible project. Thanks for linking!!

Agreed! I’m pretty psyched about their transparency and the overall model. Especially in the universe where this Apple lawsuit results in Beeper being allowed to connect to iMessage again.

Would love to hear any results you find with hosting! I’ll give it a try too and maybe do a follow on post with what I learn.

I’m an old man when it comes to major changes. If it’s salvageable then maybe stick with what you’ve got. Have you used lazy docker or watchtower?

Lazy docker should give you a more reliable interface (TUI, over ssh, not a GUI)

Watchtower (aims to) update your containers for you so you don’t have to go through this pain in the first place :)

Personally, I run my Nextcloud and Jellyfin servers on NixOS with auto updates on. It’s been chugging along great!

I agree gluetun is de way 😂 unfortunately my CPU is nowhere near 100%

Using gluetun to connect my containers to Mullvad I’m getting 60+% of my bare network speeds.

Another option that doesn’t achieve that performance is torproxy which can achieve a similar result.