• 0 posts
  • 141 comments
Joined 3 years ago
Cake day: June 15th, 2023
  • I want to swap to this but also want to do a few PRs but haven’t had the time.

    • Dockerfile exposes port 80 and runs as root
    • Less concerning, but dislike it, the scripts and CSS use remote cdns rather than being bundled locally

    Otherwise I am excited for this. Stirling doesn’t really support replicating even with license and its fat image takes up a bit of my disk space for images.

  • If public key is denied forgejo is setup, but you have an old connection in your authorized_keys file probably form using gitea. Remove the line, it should prompt you to accept public key on next ssh session. This is a basic ssh functionality probably why you were downvoted I guess.

    Gitea and forgejo configs were 100% same at some point, check forgejo news for when the last version that supported gitea migrations. That said it should still be pretty close.

  • I have tried quite a few and found blocky to be very easy and reliable.

    I use multiple DoH servers upstream, it sorts out which ones better response times and uses it more often, but splits them still. I have over 20 devices using it and its been running well.

    It also can prefetch common domains and caches them per config. I got A 40% cache rate with running 3 of them for redundancy.

  • Yeah operators are extremely nice. I used bitnami images before operator in HA setup and it would fail all the time. Using operators I have like 12 postgres DBs and 0 issues for well over a year.

    Btw, self hosting communities tend to shy away from k8s due to complexity and generally enterprises use it so less selfhosters use it. I wanted redundancy and to keep me learning tech, less crazy people tend to go with proxmox for clustering in these communities.