maestral VS k3s

maestral is an open source Mac/Linux client. Just one example, I’m sure there are others.

Worth mention the open source project Maestral: https://github.com/SamSchott/maestral

(an unofficial Dropbox client)

Sometime late last fall, my NAS rebooted and my ZFS pools didn't come back online automatically, but Docker did automatically restart the Maestral client. In so doing, it detected an empty folder...and...promptly deleted EVERYTHING in my Dropbox, assuming I'd just deleted everything locally. It's an issue that has had at least a few bug reports and which as of yet still hasn't been addressed - basically, the client needs but does not have a way to say "a bunch of stuff is changing, are you sure?" before doing it - especially on a restart of the client.

>- Debug apps which don't opt into debugging, using gdb/lldb, without disabling SIP. It's my computer, I should be root, I should be able to introspect how processes execute on it. Not being able to do so prevented me from debugging https://github.com/samschott/maestral/issues/597, since I had to disable SIP, which required rebooting, which stopped the bug from happening.

Another option is to re-sign the application with the entitlements necessary for debugging.

e.g:

https://gist.github.com/talaviram/1f21e141a137744c89e81b58f7...

there is a native build as beta, but I found Maestral much better :) https://github.com/samschott/maestral

3) No support for extended file attributes (so you cannot sync .app bundles)

[1] https://github.com/SamSchott/maestral/issues/443

If you still haven't found a use for them: they make for good low-power, always-on, headless networked servers for processing-light tasks.

Other commentators mentioned pihole/DNS, WireGuard, and music streaming, but you can also use them for a (slow) NFS server, persistent Syncthing node, Maestral host[1] (third-party Dropbox client written in Python (that can actually run on the Raspberry Pi, unlike the official Dropbox client)), or device that maintains a connection to a distributed network (e.g. Hyporborea/cjdns).

[1] https://github.com/SamSchott/maestral

I'd been reading up on Linux for the last little bit, learning about different distros and what things to look out for - so when this thing arrived I jumped onto the latest Fedora release & am really enjoying it. I've tweaked some Gnome extensions, gotten my favorite writing app downloaded, set up the awesome Maestral open-source Dropbox client, and set up a decent little undervolt using intel-undervolt, mprime, cinebench, and glmark2 :)

Open-source Dropbox client, with multi-account, no-device-limit and M1 support\ (147 comments)

For self-hosting I've found https://k3s.io to be really good from the SUSE people. Works on basically any Linux distro and makes self-hosting k8s not miserable.

Yes it’s going to depend on which k8s distribution you’re using. We have work in-progress for k3s to natively support nix-snapshotter: https://github.com/k3s-io/k3s/pull/9319

For other distributions, nix-snapshotter works with official containerd releases so it’s just a matter of toml configuration and a systemd unit for nix-snapshotter.

We run Kubernetes outside of NixOS, but yes the NixOS modules provided by the nix-snapshotter certainly make it simple.

K3S: is a lightweight distribution of Kubernetes that is designed for resource-constrained environments. It is an excellent option for running Kubernetes on a virtual machine or cloud server.

I recently purchased a used Lenovo M900 Think Centre (i7 with 32GB RAM) from eBay to expand my mini-homelab, which was just a single Synology DS218+ plugged into my ISP's router (yuck!). Since I've been spending a big chunk of time at work playing around with Kubernetes, I figured that I'd put my skills to the test and run a k3s node on the new server. While I was familiar with k3s before starting this project, I'd never actually run it before, opting for tools like kind (and minikube before that) to run small test clusters for my local development work.

Kubernetes - k3s distribution

I’ve created a local cluster with K3S and installing Windmill could not be simpler with just one chart to configure, which already has sane defaults to get started. For this demo we will also configure workers to passthrough environment variables to our scripts so that they have access to the Kubernetes API server for later.

You should be familiar with Kubernetes and have set up a Kubernetes cluster. I recommend k3s.

K3s' go.mod[0] is insane.

[0] https://github.com/k3s-io/k3s/blob/master/go.mod