It also knows when you’re home based on the occupancy sensors. I’m also not worried with their data collection so, mine is also not blocked from internet access.

I run my Truenas Scale with 5 mirror vdevs. This is sort of like raid 10 (I don’t need the differences explained to me). This means that I get 50% of the raw storage as usable but, it means that to upgrade space, I only need to upgrade two drives at a time. It also means that replacing a failed drive is fast, much faster than replacing a drive from a raidz* vdev. As you move to Truenas, this is something to consider. Given that you’re going to have 4 drives total, I don’t think you’d be wasting any additional space as you shouldn’t consider raidz safe (same problem as raid 5, high risk of second drive failure during rebuild) which leaves you at raidz2.

I use logseq to record any manual steps as well as any administrative actions that I take on a service. That being said, all of my homelan infrastructure is codified and stored in git in various ways so, it can be recreated as needed. There are very few manual steps in reconfiguring any of my services.

I’m not seeing where it needs aws. It does need an s3 API compatable object store but there are a number of them that are self-hostable. I might have missed it in my brief reading of it.

I really like Authentik after using keycloak for quite a while.

It does appear to work for me.

This is my ingressroute for lemmy:

apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: lemmy
spec:
  entryPoints:
    - web
  routes:
    - kind: Rule
      match: Host(`threads.ruin.io`) && PathPrefix(`/api/`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`) && PathPrefix(`/pictrs/`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`) && PathPrefix(`/feeds/`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`) && PathPrefix(`/nodeinfo/`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`) && PathPrefix(`/.well-known/`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`) && Method(`POST`, `PUT`, `DELETE`, `PATCH`, `CONNECT`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`) && HeadersRegexp(`Accept`, `application\/(?:activity|ld)\+json`)
      services:
        - kind: Service
          name: lemmy
          passHostHeader: true
          port: 80
    - kind: Rule
      match: Host(`threads.ruin.io`)
      services:
        - kind: Service
          name: lemmy-ui
          passHostHeader: true
          port: 80

It seems to work correctly. Given that you’re not using kubernetes, you’ll need to do some translation work.

There are multiple ways to evaluate usage. I’ll go with what I would guess is your desired measurement, things that I use intentionally (as opposed to things like dns, which just happen incidentally to other things or automation based things which are continuously running but not necessarily interacted with):

1. Mastodon
2. An app I’ve written to collect personal data
3. Jellyfin
4. Lemmy
5. Bitwarden (I pay to self-host as opposed to vaultwarden as the latter probably won’t have a security audit)
6. Freshrss
7. Linkding
8. Gitea
9. Archivebox
10. Mailcow

Is there something wrong with the nixpkgs module?