109
how do you manage your server? (lemmy.zip)
submitted 3 weeks ago by to c/selfhosted@lemmy.world
86 comments fedilink hide all child comments
 

I usually connect with my server via ssh in a terminal and run basic commands. What's a better, more efficient and modern way of doing that? Especially considering ai and documentation along the way? I wonder if there's a better approach than "connect from remote and act local". Is there a method to "code local and push to remote"?

I use a fedora server with podman, caddyfile and vi.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 weeks ago (2 children)

Maybe a bit more on the overkill side, but I use Talos Linux (declarative K8s distribution), then Terraform for initial setup and FluxCD for everything else (including VMs via Kubevirt). It's a hell of an initial learning curve, but afterwards I just do my talosctl upgrade and upgrade-k8s from time to time, and don't have to worry about anything else. Upside is, Kubernetes provides a unified, extensible API for everything, for example:

  • reverse proxy via Ingress or Gateway-API
  • firewall via NetworkPolicy
  • even databases like Postgres through an Kubernetes Operator like CNPG, with a similar simplicity as with the big cloud providers (just a single yaml file with the specs like storage capacity, CPU and memory limits, backup target and schedule etc.)
  • it is very scriptable (everything is managed via the API)
  • automated image updates via either FluxCD itself or just dependabot/RenovateBot creating PRs to your GitOps repo

Downsides:

  • you have to figure out persistent storage (CSI), which is slightly more complicated than just a single filesystem and manually specifying volume mounts like with docker, but if done right, you have a simple interface with powerful capabilities via the Kubernetes API
    • there are simple CSI implementations that just expose node local disks via LVM or ZFS, so if you just have a single node, or don't care about replication, it's fairly easy to get started
  • initial learning curve is quite high, especially if you have no prior experience with container orchestration in general
  • definitely overkill if you just want something simple that "just works"
  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 2 points 2 weeks ago (1 child)

    I assume this is on your own physical hardware? What parts do you set up with terraform?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 weeks ago*

    Yes, my own hardware. But before I decided to build my own server last September, I was on a similar setup on a dedicated server at Hetzner, just less powerful (I'm so goddamn glad I bought the memory and storage back then, I probably wouldn't even get the 192GB DDR5 right now for the price I paid for all memory and storage combined).

    Terraform starts at the Talos initial machine config and cluster bootstrap including CNI setup and routing configuration (I have an opnsense in front that handles ingress routing) until FluxCD is fully set up and takes over.

    Ingress traffic works via a small Hetzner VPS, and BGP through Wireguard, so there is no DNAT or SNAT between the open Internet and my Kubernetes load balancers and all services see the actual client IP. This took a shit load of time to get right, because wireguard only has an mtu of 1420, but the regular uplink is usually 1500, so pmtu discovery in my load balancers implementation (Cilium) and mss clamping in opnsense had to all be configured

  • permalink
  • fedilink
  • source
  • parent