506
planned Proton replacement (jlai.lu)
submitted 6 days ago by to c/privacy@lemmy.ml
342 comments fedilink hide all child comments
๐Ÿ™‡ 1
 

I've cancelled my subscription yesterday, conveniently it was about to renew at the end of the week, so I have a few days to migrate from Proton, here's what I'm thinking of, but I'd love to hear what other people are switching to

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 3 points 6 days ago (6 children)

Agreed on all of this. I run docker on one of my PCs and have multiple containers running. But I didn't know you can cluster multiple PCs to run a copy of the containers and I was just wondering about a week ago if that's possible. Would you have a resource on how to set up a 2nd PC to do this and cluster with my server?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [โ€“] 2 points 6 days ago (1 child)

    You need docker swarm for that, it's pretty easy to setup and it works as an extension to docker.

    If you selfhist eg. DNS, or another static app that you want highly available but from a single IP, you can use keepalived directly on the host and this allows you to have two machines that share a third virtual IP, and if server A fails, the IP moves automatically to Server B and you don't even notice that the server failed, because everything failed over to the other server.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [โ€“] 1 point 5 days ago (3 children)

    I don't have a known good resource, but you should look into K3S. https://docs.k3s.io/

    The documentation is very dense, I fear. I would probably go hit youtube search for "k3s cluster" and find a beginner that doesn't annoy you too badly.

    The general path you'll have to do is:

    Translate Configuration: Convert your docker-compose.yml settings into Kubernetes YAML manifests

    Install k3s

    Map Storage and Secrets. Replace local Docker volumes with PersistentVolumeClaims (PVCs) and .env files with Kubernetes Secrets and ConfigMaps.

    Deploy and Verify: Apply your manifests using kubectl apply and verify routing through the built-in Traefik ingress.

    Then you can install and add a new node.

    depending on how you set it up, it'll move the containers around for you automatically.

    Note: all your k3s nodes need to be very close network wise. you can dump one at a friends house and make a cool geo-diverse setup, they need REALLY low latency

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [โ€“] 1 point 5 days ago (2 children)

    Whew, OK that's more involved than I thought it would be. I will try to find time on the weekend to mess with it. Thanks for the info.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 1 point 5 days ago (1 child)

    i'd install k3s on the two boxes and just stand up a super simple container that doesn't need storage, think ntfy or something of the like, you can do that quick. getting shared storage up is a but more difficult :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •