"Bound" to my hosted services/infrastructure? reddit / selfhosted ---------------------------------------------------------------------- Weirdy19 · 2023-12-08 19:06 Hello Reddit! I am running and hosting some services for my bigger hobby-blog and my voluntary team, which depends on reliable and working infrastructure. This includes a web server, mail server and so on. For me personally, I am also using that infrastructure for my personal mails, cloud, and a lot more. Now, always when travelling or being away, I feel "bound" to that things and keep thinking about taking my laptop, in case anything happens. I also have my phone by me, for checking what monitoring says. A (short) downtime would not be that big issue, but things like important security updates, security breaches and so on. Also, important to say, that I have no second admin which could handle that for me while being away - if I had one, I would feel unwell managing him that, as my personal mails and data are also on that server. How do you handle such things? I really like hosting services for my own, but I am thinking about giving that away. Don't know how to do that instead - do you have tips? I really want to be away again with the feeling "I don't give a \*\*\*\* if anything happens, someone has my back". Thanks! ---------------------------------------------------------------------- shahmeers · 2023-12-08 20:18 > I really want to be away again with the feeling "I don't give a **** if anything happens, someone has my back". Then make your infra fault tolerant (e.g. if you're on Docker Compose move to Docker Swarm or Kubernetes) and pay someone else to manage your hardware (i.e. move to the cloud). ---------------------------------------------------------------------- Weirdy19 · 2023-12-08 20:47 I am already trying to be as fault-tolerant as it can be. The last few months, I had some critical security updates which had to be implemented very fast. What would have happened when I am away ... ---------------------------------------------------------------------- qrokodial · 2023-12-08 20:57 can you give us an idea of what kinds of issues you've had recently, and how frequently these kinds of issues occur? ideally things shouldn't be exploding the second you walk out the door. ---------------------------------------------------------------------- shahmeers · 2023-12-08 21:12 > The last few months, I had some critical security updates which had to be implemented very fast. Can you give an example of this? Even if there are required security updates, your system should've continued to operate normally. Also, theres ways to automate security updates via CI/CD. ---------------------------------------------------------------------- Perpetual_Nuisance · 2023-12-08 21:24 "Ideally" LOLOL ---------------------------------------------------------------------- bgatesIT · 2023-12-08 21:36 Automation is the key here, along with fault tolerance. Just deploying a server or vm, installing some packages and saying yup that works lets expose it isnt enough at all. Look into containerizing youre apps/services, from the short read it could be a great use of a simple Kubernetes cluster, or docker swarm. Deploy all youre services in there, setup proper disruption budgets, replica sets, what have you. You can update youre apps easily without downtime, and if something goes back you can simply just rollback to the previous version. ---------------------------------------------------------------------- user01401 · 2023-12-09 18:20 I automate updates, backups, cleanups, etc. in the middle of the night for minimum downtime. Use a UPS to eliminate brownouts and blackouts that aren't excessive. ---------------------------------------------------------------------- teapot-error-418 · 2023-12-10 02:37 The reality is this is why you pay for professional services. It's not because those professionals are magic. I'm guessing a lot of people in this sub are capable of deploying infrastructure that's on par with what a small company's SaaS product looks like. It's because paying for services comes with an SLA and someone's neck to grab when things go wrong. I have lots of self hosted stuff that I use, but I've avoided deploying it to others outside of media consumption which isn't critical if it dies. So... There is some good advice here about improving to get some fault tolerant infrastructure. But at the end of the day, a docker swarm or k8s cluster isn't going to fully solve your problem. The only thing that really solves your problem is another person watching your stuff while you're gone, who is capable of solving problems. Sometimes paying for Office365 is worth it.