For s3 iDrive e2 is cheaper. It costs 4$ per month, if you pay monthly and down to ca 3$, if you pay yearly.

The egress policy is mostly the same as backblaze. You get 3 times the storage you pay for. With backblaze you get 3 times the average amount of data you have stored.

Think they were clapping because the star vessel died yeah. I don’t think they cared who killed the star vessel.

Anyone is welcome to join my instance at endlesstalk.org. Its running on a pretty beefy server, so it can take a decent amount of users.

There are multiple frontends like lemmy.world and I have setup a seeder(lemmony), so the all feed should be pretty filled.

Photoprism

After hosting my own instance with just me for ca. 2 weeks:

1.99Gi pictrs

5.21Gi postgres

The internal path, I’m persisting is /mnt, but I also use an older version of pictrs(0.3.1). Think the newer version uses a different path.

I also needed to add the following for the pictrs container to work correctly.

  securityContext:
    runAsUser: 991
    runAsGroup: 991
    fsGroup: 991

For container orchestration, which is mostly what k8s provides, then you could use docker swarm or nomad. You could use docker-compose with multiple replicas of the wanted container + a load balancer to divide the load.

In general I don’t think k8s/k3s is needed for hosting lemmy yet, but since I have a setup for k3s, it is easier for me to use it.

I have only 1 container of pictrs running(with no scaling) and are using longhorn for storage, so if the pictrs container switches node, then longhorn handles it for me.

You can definitely have high availibillity without kubernetes, but its easier(For me atleast) with kubernetes.

My instance has 2 users. The domain name is endlesstalk.org

I host it on a k3s cluster with 2 nodes.

I have the same issue and I also get the warning for the expired headers. I have tried increasing the federation.worker_count(to 99999) and nginx workers(to 10000), but the issue still occurs for me.

There is also a lot of missing comments for me on my own instance. Have to view this post on lemmy.world to get all the comments, since there are a lot missing on my own instance.

I also thought about using AWE SES, but I decided not to use it, since I was “sandboxed”(See more here).

I decided to use MXRoute, which have worked great for me so far. It is more expensive(50$ per year), than purelymail and Migadu, but for me reliabillity is very important, so I don’t mind paying a bit extra for it.

I don’t think that App-daemon can automations, that homeassistant alone can’t. I just think it is easier and simpler to create more complicated automations in App-daemon, since I can script everything in Python.

Ubuntu server(Xeon CPU E5-2650 v4 with 86 GB Ram) running k3s(My home server):

• App-daemon(Used with home assitant for more complicated automation)
• Bazarr
• Browserless(Currently used for rendering js pages for huginn)
• Dpaste
• Filerun
• Homeassistant
• Homer(My dashboard)
• Huginn
• Jellyfin
• Kaizoku(For downloading manga)
• Nzbget
• Nzbhydra
• Ombi
• Paperless
• Photoprism
• Pihole
• Plex
• Prowlarr
• Radarr
• Scrutiny(For checking my drives)
• Sonarr
• Qbittorrent with vpn
• Wiki.js
• Christmas-Community(Wishlist)
• ZwaveJS(For homeassistant)

2 Ubuntu servers running k3s(VPS used for my infrastructure services)

• Keycloak
• Offical docker registry
• Bitwarden
• Gitea
• Headscale
• Healthchecks(For checking backups)
• Uptime-kuma - Hashicorp vault

Infrastructure services runing on all servers

• ArgoCD(For deploying everything on k3s)
• Longhorn(For storage)
• Vault-secrets-operator(For getting secrets from vault into k3s)
• Traefik(My reverse proxy)

Lastly I’m hosting Lemmy on a leftover VPS, that I hadn’t used in a while. Might move to a bigger server though.