• 7 Posts
  • 173 Comments
Joined 2 years ago
cake
Cake day: February 17th, 2024

help-circle
  • edit: jfc, typos. I hate typing on phone keyboards.

    Secondary to that is that getting bluray to work on a computer is a pain. It’s not impossible, but its not natively supported on macos or Linux (I dont know about windows, haven’t used it in ages now).

    Whereas if you do use the alternative methods, you don’t have to fight with trying to get the os you’re using to work with bluray



  • I got a test box set up with nixos and a config that runs all of my services. I wanted to test the declarative rebuild promise of it, so I:

    1. Filled the services with my some of my backed up data (a copy of the data, not the actual backup)
    2. Ran it for a few days using some of the services
    3. Backed up the data of the nixos test server, as well as the nixos config
    4. Reinstalled nixos on the test box, brought in the config, and rebuilt it.

    And it worked!!! All serviced came back with the data, all configuration was correct.

    I’m going to keep testing, and depending on how that goes I may switch my prod server and nas to nixos.



  • I agree with the other folks recommending Pangolin on a VPS for this. It’s great. It combines a reverse proxy and a wireguard tunnel together for you. You don’t have to open any ports on your home network, and Pangolin allows you to set access levels for each individual service.

    So you can have some fully open for those who aren’t going to mess with VPNs and tunneling, and you can put other things behind Pangolin auth to add additional protection.








  • find /path/to/starting/dir -type f -regextype egrep -regex 'some[[:space:]]*regex[[:space:]]*(goes|here)' -exec mv {} /path/to/new/directory/ \;
    

    I routinely have to find a bunch of files that match a particular pattern and then do something with those files, and as a result, find with -exec is one of my top commands.

    If you’re someone who doesn’t know wtf that above command does, here’s a breakdown piece by piece:

    • find - cli tool to find files based on lots of different parameters
    • /path/to/starting/dir - the directory at which find will start looking for files recursively moving down the file tree
    • -type f - specifies I only want find to find files.
    • -regextype egrep - In this example I’m using regex to pattern match filenames, and this tells find what flavor of regex to use
    • -regex 'regex.here' - The regex to be used to pattern match against the filenames
    • -exec - exec is a way to redirect output in bash and use that output as a parameter in the subsequent command.
    • mv {} /path/to/new/directory/ - mv is just an example, you can use almost any command here. The important bit is {}, which is the placeholder for the parameter coming from find, in this case, a full file path. So this would read when expanded, mv /full/path/of/file/that/matches/the/regex.file /path/to/new/directory/
    • \; - This terminates the command. The semi-colon is the actual termination, but it must be escaped so that the current shell doesn’t see it and try to use it as a command separator.