I do understand the logic and the difference between ;, &&, and `||. What was confusing me was the command grouping and my misunderstanding of the curly brace grouping rule that the command list has to END with a semicolon. @SheeEttin@lemmy.zip pointed out to me with the link in the comment they left.
I had read that same link and misunderstood it. On second read I got it, and see now why my script is working, as the newlines serve the same purpose as the semicolon, so the curly braced groups are terminated correctly.
My environment is just my homelab. Ubuntu server on my server, Arch (btw) on my laptop. So I could go with any language , but right now I'm choosing Bash. I know stuff I'm doing would probably be easier in a different language, and maybe I'm a glutton for punishment. I just want to get really good with Bash.
The logic is Bash is gonna be available on just about any computing environment I encounter (linux especially, but even Windows with WSL and zsh on macOS (which I know is different, but still very similar). But really, I am just enjoying the hell out of learning and scripting with Bash. I'll move on to Python or something someday.
Ah! I misinterpreted what I read! I found that exact same reference link when looking into this and I misinterpreted this:
The semicolon (or newline) following list is required
to mean that it required the semicolon as the command separator. That explains why my script works. The newline closes each group, and the other operators are allowed, the list just needs to be closed. Thank you!
I have a full time job and am working poor like many. I'm hosting all this on a decade old PC that I built back in the day. I find the time I spend on deploying and maintainig my services very rewarding, but its not for everyone, and that's fine.
I've been at it for years. It takes time and effort and learning to do, and I'll be the first to help people who post questions here to Lemmy for self hosting.
FOSS is a community like any other with good and bad apples in it. You can learn a ton from the community and take control of your own data if you want to.
I find it very rewarding and fun, but if you expect me to write a full how to every time I mention that I self host that's a little crazy. I'll happily answer anyone's questions and share my knowledge but I'm not just gonna dump six-ish years of my notes in a comment.
Yeah. Web search sucks these days. Here's where I find stuff:
Awesome Self Hosted is a list of all kinds of self hosted options broken down into categories. It's a great resource. I browse this pretty regularly to see if anything catches my eye.
The selfh.st email newsletter is also great. Weekly email with some self hosting news, new projects and projects that have updated.
I'm running it on a nearly decade old PC I used to use for windows and gaming back in the day. Before I ran it on the PC I ran it for several years on a raspberry pi 4 (8GB).
For offsite, I roll my own by keeping an (encrypted) hard drive stashed in my desk at work. I update it every couple weeks or so, which is fine for me.
Edit to add the PC is now running Ubuntu server, and in addition to nextcloud I run like 15 or so other services for myself and my family like
Navidrome (rips of all my old CDs and new ones I buy)
Jellyfin (rips of all our DVDs)
Radicale (caldav for calendar. Could do this with nextcloud but I wasn't running it for a bit there)
Joplin server for my notes
Mealie for our recipes
Forgejo, my private gitforge
Thank you for the link!
I do understand the logic and the difference between
;,&&, and `||. What was confusing me was the command grouping and my misunderstanding of the curly brace grouping rule that the command list has to END with a semicolon. @SheeEttin@lemmy.zip pointed out to me with the link in the comment they left.I had read that same link and misunderstood it. On second read I got it, and see now why my script is working, as the newlines serve the same purpose as the semicolon, so the curly braced groups are terminated correctly.