Screw it, I’ll host it myself
421–430 of 495 posts
Re: Screw it, I’ll host it myself
#422Earlier quoted context omitted.
Long term platform stability seems to be moving from relying on the OS to higher up in the stack with the advent of Docker. It feels like Docker is being used more and more in cases where I would have considered something like CentOS.
Docker feels like the equivalent of the teenager that doesn't want to clean his room so he just pushes all his mess under the bed. The complexity is still under the bed. We're all going to have to dig under that bed one day. Or we're just going to end up buying new hockey sticks, football pads, etc. Which is to say, we're going to end up with Linux on top of Docker on top of Linux.
That's just my opinion of course. It's possible to write confusing Dockerfiles but really they're mostly just shell scripts. And the idea of "Linux on top of Docker" seems a bit odd - there's only ever one Linux kernel no matter how many containers you have running. Docker is built on Linux.
Re: Screw it, I’ll host it myself
#423Regarding sever hosting: Hetzner has a very attractive server auction on their website [0]. For about 30€ you can get several terrabytes with a fast cpu and plenty of RAM. No set-up fee either. These are unmanaged dedicated root servers. Basically cancelled sever subscriptions are first offered here again before they take apart the server. So the offerings vary and are time-limited. However, if you pull the trigger t…
Seconding this – Hetzner also has pretty decent technical support considering the price. If you get one of their servers, make sure to check the manufacturer and type of hard drives and compare to Backblaze's Hard Drive Stats[1]. Also keep an eye on the S.M.A.R.T. status of your disks. In the past Hetzner has shipped servers with less-than-ideal hard disks (e.g. Seagate ST3000DM001). While their staff is pretty fast…
"2x HDD SATA 2,0 TB Enterprise"
Which is too bad.
Re: Screw it, I’ll host it myself
#424Then I have two home 1Gb fibers (when my summer house gets fiber this summer hopefully).
I wrote my own distributed database so all data is everywhere at all times = no extra work. (after the initial 3 years of making it robust :D)
I would say go for the opposite of "use as much standard as possible" and make everything yourself, from scratch (except OS and language);
that way you can slowly but surely make it perfect = 100% read uptime even if one home fiber blows up.
People that describe this as meaningless don't understand what responsibility is!
Own (as in nobody can take something away), understand and change; in that order, on repeat, forever...
(until you die and your children pick up the slack because you thought them what responsability is)...
People will learn to respect responsability when it's too late.
Re: Screw it, I’ll host it myself
#425Earlier quoted context omitted.
"Don't use such a browser then!" Never said that I did! :) I use a text-only browser for reading HTML. Many times I do even use a browser for making HTTP requests. Truly one can use all these strategies, application-based, router-based, gateway-based, if they are available. They are not mutually exclusive. Personally I just would not feel like I can rely on extensions or other solutions tied to some software I do not…
> I use a text-only browser for reading HTML. Is that getting more difficult with the prevelance of JavaScript driven websites?
Re: Screw it, I’ll host it myself
#426The problem I have always had when building elaborate home server setups is the "set it and forget it" nature of the systems I've installed bites me in the ass. Since it's not my full-time job to manage these systems, I'm really not familiar with them the way I might be with the systems I manage at work. These systems cruise along for years, and when something finally does go belly-up, I can't remember how I set it u…
I encounter this every 6-12 months when I go back to an old project that is 'working' and want to add something/update something and it all just looks foreign to me. The worst thing is that I have often gone through a lot of effort around making it easy to set up and deploy (docker and whatnot) but even that I have forgotten about. (I came across a docker file in an old project and couldn't get it to work properly un…
For my VPS, I have a Notion page where each project (name, url, mapped ports) is a row in a table. Then the project page contains a copy of my docker config and various informations I might need for maintenance/reinstallation.
Re: Screw it, I’ll host it myself
#427(* Links to Vultr contain my referral code, which means that if you choose to subscribe to Vultr after you clicked on that link, it will earn me a small commission.)
host yourself means - running on your own hardware
Re: Screw it, I’ll host it myself
#428I tried to have a setup similar to this during covid but ended up with a bit of a mess. What I wanted was a home server that used X forwarding to forward services to my VPS, which also had some images running in a docker-compose stack that I wanted to have more robust uptime than my home server. I ended up being unable to get traefik to pick up on the x-forwarded ports, and ran into SSL certification issues that seem…
Re: Screw it, I’ll host it myself
#429Earlier quoted context omitted.
> self-host anything important like mail Email is basically pointless to host yourself from a privacy perspective. Every email has one or more people on the other end that also get a copy. Privacy and email are mutually exclusive. That said, the alternative doesn't have to be something like gmail, where they can do whatever they want with your data. I use Fastmail and that's "sufficiently private" for my needs.
I use Fastmail + a custom domain. Because fastmail is the provider, I am not on any spam lists. My emails make it through. My service is very reliable, so I always get my emails. If fastmail decides to hate me, I can just point my domain MX records somewhere else. TODO: need a non-fastmail backup of my email
Re: Screw it, I’ll host it myself
#430Earlier quoted context omitted.
After reading through it all, I think this is more a condemnation of the author's diagram (or at least their decision to put that particular one up-front), than of their process in general, nor the challenge. Breakdown of (my) issues with the diagram: - author's interaction with each device is explicitly included, adding unnecessary noise - "partial" and "full" real-time sync are shown as separate processes, whereas…
That is great ASCII viz ! Did you do it purely by hand ? I often need to but give up...