Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 4 Posts
  • 701 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle







  • dan@upvote.autoSelfhosted@lemmy.worldExpanding storage on simple home server
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    8 days ago

    Add a second SSD, if the motherboard has a SATA port (I assume your current one is an NVMe drive). A SATA SSD is still more than fast enough as a second drive.

    Moving to a bigger SSD also isn’t too difficult, as long as you have a system where you can have both the old and new SSD connected at the same time. It can be a different system if needed. Download Clonezilla onto a USB stick with Ventoy on it, and boot into it. Just make sure you have backups and do the clone in the correct direction (don’t clone the blank new drive onto the old one!!)




  • In addition to this, a lot of movies and TV shows are going to use the same DRM mechanisms, whereas with games it’s different for every game. The developers (both of the DRM systems and of the game) learn what works and what doesn’t work and adjust the system for their next game.

    Edit: Also, games often have anti-piracy measures hidden throughout the game, so whoever is cracking the game likely has to play the game quite a bit to ensure they’ve caught them all.


  • This is how I handle it for most software: Read (or at least skim) the changelogs for all minor and major versions between your current version and the latest version.

    If you’re using Docker, diff your current docker-compose to the latest one for the project. See if any third-party dependencies (like PostgreSQL, Redis, etc) have breaking changes.

    If there’s any versions with major breaking changes, upgrade to each one separately (eg. 1.0 to 2.0, then 2.0 to 3.0, etc) rather than jumping immediately to the latest one, as a lot of developers don’t sufficiently test upgrading across multiple versions.

    Take a snapshot before each upgrade (or if your file system doesn’t support snapshots, manually take a backup before each upgrade).

    …or just don’t read anything, YOLO it, and restore a snapshot if that fails. A lot of software is simple enough that all you need to do is change the version number in docker-compose (if you’re using Docker).


  • In addition to backups, consider using snapshots if your file system supports it (ZFS, Btrfs, or LVM).

    I use ZFS and have each of my Docker volumes in a separate ZFS dataset (similar to a Btrfs subvolume). This lets me snapshot each container independently. I take a snapshot before an upgrade. If the upgrade goes badly, I can instantly revert back to the point before I performed the upgrade.







  • I haven’t watched the video yet, but it’s generally not worth the hassle of setting up mutual TLS if you’re already using a peer-to-peer VPN like Tailscale, as the VPN software is already doing mutual authentication.

    Edit: A peer-to-peer VPN (or mesh VPN) is one where two systems that are connected to the VPN can directly communicate with each other, instead of needing to go through a central server as with something like OpenVPN. With Tailscale or Wireguard, the peers need each other’s public keys to communicate.