Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TH
Posts
3
Comments
115
Joined
2 yr. ago

  • I'm extremely anti-gatekeeping any hobby, and I've never gotten any bad vibes off him. He nearly always addresses the fact that many of the minutae that he focuses on are for the extreme nerds with extra money/time to spare. He even regularly talks about how many of the ideal processes he talks about, he doesn't do because it's a PITA.

    He's very slow to recommend expensive/time consuming products, and he's quick to offer more reasonable alternatives.

    That said, he's a coffee nerd with money to spare, so he definitely gets excited and involved with things that are a bit beyond your average bear.

  • Yes, you should never use sudo inside a users crontab. If you want to run as root then use the system crontab.

    I appreciate the advice! I had never really heard about the distinction between the system crontab and user crontabs. While it makes sense in retrospect, I am entirely self-taught about this stuff, and nowhere I had looked had ever mentioned that there were two separate crontabs.

    I would also encourage looking at systemd timers

    Do you happen to know of a good resource to learn about those off the top of your head? I appreciate the suggestion!

  • So, right now I'm trying the system crontab instead of my user crontab.

    Just to reiterate from my post, however, I have tried the full path. I was giving example paths. I should have been more explicit that by just "using dot" I meant using relative and absolute paths.

    All paths have been full paths from the get go, though I did try cd-ing into the folder and running it with a relative path. My hope at this point is that it's somehow a permissions issue as my storage setup is a bit odd with TrueNAS Scale running as a VM on ProxMox. Permissions with docker are usually hell, and I have to run literally everything that touches my NAS as root to get the permissions to play nicely, so it would make sense here that it's just the permissions being upset and preventing access to the files.

    I set a backup to run on the hour, so I'll report back with whatever happens.