x3i

Second this. Did it a few weeks ago, works perfectly fine. Paid 50€ for a four year old Acer Chromebook 11 and followed the matching guide here: https://mrchromebox.tech/#devices
(Don’t buy my model, the keyboard is crap)

I don’t see anyone mentioning sth power efficient yet, so I will throw my two cents in here; I just ordered an Odroid M1S to take over some jobs from my RPi4 (8GB). Has not yet arrived so I cannot praise it yet but might be worth a look!

Update: seems like the persistence section is sufficient; I have

persistence:
  enabled: true
  existingClaim: nextcloud-config-claim

at the end of my values file which references a volume claim (and volume) that I created manually upfront. The importand file is config.php. Back that thing up immediately and three times, print it if you have to. The secret in there is unrecoverable otherwise and needed for any repair actions.
I also use the postgresql sub-chart (by simply enabling postgresql as database) and provide a claim there:

postgresql:
  enabled: true
global:
    postgresql:
      auth:
        username: XX
        password: YY
        database: nextcloud
  image:
    repository: postgres
    tag: "14"
    postgresqlDataDir: /bitnami/pgdata
  primary:
    persistence:
      enabled: true
      existingClaim: nextcloud-db-claim

Hope it helps!

I think it was literally called “config”. I will check my setup and provide the mount points I used here later today, if you back these up, it should work. Put some disposable data on it once you finished setup and then upgrade to a newer version to see if everything works. You can specify the image tag to use manually (or you install an older chart version).
I also pinned the postgres version to 14, not sure if I can recommend that but I had issues with DB upgrades in a docker installation, so I tend to be careful there.

True. Have a setup running on Kubernetes with their helm chart but the documentation is (or at least was) insufficient on what is important to back up, so I had to start over once, learning the hard way that the config file contains the one string you always need for recovering data. Since then, it is pretty stable and I had almost no problems.

Thank you and sorry at the same time for not phrasing my question properly; I know what it is, I am just very baffled on how it should be a bad thing if they strengthen the enforcement net neutrality. Imo, this is always a pure win for the consumer as it prevents a lot of malicious business models. So basically: no idea what the initial commenter is complaining about.

Can you elaborate? 'cause I sure as hell ain’t gonna look it up

My thoughts exactly. Also, these are a lot of words for very little content, feels like an attempt to obscure the actual intention.

Unified Push.

Unbelievable that we have to rely on Google and co for sth as essential as push messages! Even among the open source community, the adoption is surprisingly limited.

Sorry to hear that! Can confirm that I experience none of these issues on Arch with my 5900X and an Aorus pro wifi (mini ITX), so definitely specific to your combination.

Same problem here, this is my solution:

exec-once = bash -c 'until waybar; do echo "Waybar crashed with exit code $?.  Respawning..." >&2; done'

I used it in a motorbike trip last year and had some trouble but not in the way you describe. I used offline maps, finding my location was a matter of seconds. It would however sometimes not register some “waypoints” and try to lead me back to a point I already passed until I restarted navigation. Annoying when you have a route with several intermediate destinations.

I use organic maps for everyday navigation, never had such issues with that one.

Does anyone know if this is applicable to any ARM64 devices? I’d like to test NixOS on a cheap device and I did not find anything on usable ARM64 devices