• 1 Post
  • 273 Comments
Joined 1 year ago
cake
Cake day: January 2nd, 2025

help-circle

  • Uggh, feel bad for them.

    I’ve tried for years to get friends and family to have their data sit in a single point in the house and use backup services. That would be a massive improvement.

    Family won’t listen, so I’m building minicomputers for them all that will handle it. Just have to configure their devices to store data there.


  • Onomatopoeia@lemmy.cafetoSelfhosted@lemmy.worldHoliday Upgrade Disasters
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    2 days ago

    I don’t do upgrades (well, not in the sense most people think of them).

    My approach is that upgrades are too risky, things always break. It’s also why I don’t permit auto updates on anything. I’d rather do manual updates than dedicated time. Keeping things working is more important, and I have backups.

    I run everything virtualized (as much as I can), so I can test upgrades by cloning a system and upgrading the clone. If that fails, I simply build a new system based on some templates I keep. Run in parallel, copy config and data as best I can, then migrate. Just migrated my Jellyfin setup this way.

    This is a common methodology in enterprise, which virtualization makes a lot easier for us self hosters.

    I haven’t had a disruption from updates/upgrades in 5 years.



  • They didn’t make Publisher, it had been around for a few years before they acquired it.

    At the time (early 90’s), DTP was growing, fast. Publisher was stupid cheap compared to Aldus and Quark and could do all the day-to-day stuff for a fraction of the cost (and faster).

    I was using all 3 at the time, and my go-to was Publisher as it was easier, and way faster on the hardware then.

    I’d use PageMaker for multi-page, ongoing docs, but a single page? Publisher.

    MS acquired Pub around 1995. (They’d deny it, like they do with OneNote, but I was using Pub before they owned it).