• 5 Posts
  • 36 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle
  • Thank you (switched to an lemmy.ml account because I haven’t been able to comment or post on lemmy.world for over a week)

    Not really specific skills, I’m just a hands on learner/tinkerer. I’ve been messing with self hosting for around three years now, so spinning up new docker services is fairly easy (fairly. I still have a lot to learn about docker). In doing so, I’ve used and referred to github a lot, and even used git to clone repositories for self hosting a service, but beyond that, I hadn’t looked into it as it didn’t seem relevant to me at the time.

    And thank you for the Forgejo information! I will look into that and compare to see which one I’d like to use. Coincidentally I just saw today or yesterday that Forgejo has gone for a hard fork.












  • That’s what I’m finding. I’m not certain I need regex for what I want to accomplish with find. I’m reorganizing my media libraries, and I have a mix of mp4 and mkv files. I want to be able to find all mkv and mp4 files and move them using regex like '.+\.(mp4|mkv)'

    I have learned how to use find with -exec and -delete, but I haven’t gotten to -print0 or xargs yet.


  • I’ve never used git to publish/make myself a repo before. That’s something I’ve been meaning to learn but haven’t quite gotten there yet. However, with the amount of tinkering, and breaking I’ve been doing, I think I’ll move it up on my priority list.

    I’ve also got shell scripts I’ve been writing and tinkering with and having proper version control (versus script, script.copy, script.copy.bak…) would also be nice.





    1. Agree. Always was too strong a statement. I’ll edit my post to reflect that.
    2. Thank you! I’m going to read up on string manipulation
    3. True. This has been working for me because I know enough of the directories I’m looking for to insure a single match, but not the necessarily the exact, specific directory name.


  • To insure the script works on the files you want it to work on.

    If you use a relative path in a script (is relative the right word?), with something like:

    mv *.txt /place/to/move/to/

    The script will act on the files in the current working directory, which may not be the files you intend for the script to act on.

    If you put the absolute path to where the files reside in the filesystem, then you can run the script from any location, and know that it will act on the files in the specified directory.

    Maybe always is too strong a statement. For the scripts I was working on, it was a learning moment when I ran the script without the full path and the script errored out because the files were not in the working (home) directory. (I had ssh’d into the machine to run the script)


  • You’re welcome! I stumbled across Multipass when I was looking for virtual machine options for the m1 mac mini I’m working on. I specifically was trying to get away from using the mac coreutils for a consistent syntax experience, and Multipass has been working perfectly for that.

    It was only after I’d been using Multipass already that I stumbled across that script, and planned to take a look at it to possibly implement on my machine. I didn’t realize that Homebrew allowed for replacing the coreutils with the GNU versions. Another thing learned!