This is the correct answer. Private IPs are less concerning (on noes now someone knows a network in my homelab is 10.0.0.1/24!) - but absolutely change public IPs in logs.
If it’s necessary to reference external users/systems in multiple log files, I’ll change the names to user1, user2, server1, db2, etc
Does it have Discovery as a normal app store? You might be able to use that.
Honestly, give the terminal a shot - it’s not as complicated as you may think.
I would consider using your Synology for what it’s good at - storage.
My homelab has a Synology DS1618 and servers are Lenovo M90q systems. They have enough compute to get the job done, and use the Synology NFS mount for storage.
sudo dpkg -i /path/to/yourde.debNow whether or not all the packages are fubared at this point is unknown, but that’s how to install a deb file.
Yeah, for the integrated CI/CD, give GitLab a shot - it saves on spinning up a Jenkins or ConcourseCI server.
CI/CD can be useful for triggering automation after merge requests are approved, building infrastructure from code, etc.
I’ll come out with an anti-recommendation: Don’t do GitLab.
They used to be quite good, but lately (as in the past two years or so) they’ve been putting things behind a licensing paywall.
Now if your company wants to pay for GitLab, then maybe consider it? But I’d probably look at some of the other options people have mentioned in this thread.
Plus oh-my-zsh and the powerline 10k theme - this is my go-to shell.
Oh snap, are you the developer of Viewtube? If so, first off - great job. I do the infrastructure side of IT for my day job but aside from some basic go, I couldn’t code something like this to save my life.
I wish I had the chops to contribute to the project.
Heck, you could do a pre-stage play where you delegate to localhost an ansible.builtin.get_url to download the compose file before doing the rest.
It’s anonymous bulk text posting - great for sharing logs, but don’t discount the more grey side of the internet. If you browse recent public posts there’s often some fun things like scam links, credentials, etc.
It’s definitely fallen out of favor for password dumps though.
Holy shit, 35 tmux windows?! That’s insane.
Fun fact (that I just took advantage of in a CTF), sudo can also limit command line arguments. If you only want a user to restart a service but not stop it, you can restrict sudo to only
systemctl restart mysvc.service
I agree, but it’s a hard pill to swallow that Meta is the best partner to grow the fediverse. There are real lessons to learn from Embrace, Extend, Extinguish (look at XMPP and Google), not to mention privacy concerns and content moderation issues that seem to be a “feature” for Meta products vs bugs.
I’m not sure what Zuck is up to, but for whatever it’s worth I think the best think the fediverse can do is be somewhat reactive to Meta’s movements.
If instances start getting overwhelmed with content, then block.
If Meta starts showing signs of EEE, then instances can block.
And us users can move to instances that we feel match our personal stances on things - hate Facebook like the plague? Look at one of the defederated/blocking instances. Do you miss interacting with a larger audience? Stay on instances that are embracing (or withholding judgment) the Meta federation.
It’s a complex topic to be sure, and the only way we’ll know the right way to deal with it is with the benefit of hindsight in a few years
Not the OP, but Eternal September references the massive culture impact on Usenet when ISPs started lowering the barrier to joining the then somewhat exclusive forum-esque part of the internet.
I didn’t intend to use it on the chest freezer - it was mostly for the modem, but since I had spare battery capacity and outlets I thought what the heck.
The power load is practically nothing until it cycles, and even then it’s fairly efficient - my current runtime is estimated to be about 18 hours, more than enough to come up with an alternative if we lose power in a storm.
While I appreciate the sentiment, most traditional VMs do not like to have their power killed (especially non-journaling file systems).
Even crash consistent applications can be impacted if the underlying host fs is affected by power loss.
I do think that backup are a valid suggestion here, provided that the backup is an interrupted by a power surge or loss.
I agree that 99.999% uptime is a pipedream for most home labs, but I personally think a UPS is worth it, if only to give yourself the option to gracefully shut down systems in the event of a power outage.
Eventually, I’ll get a working script that checks the battery backup for mains power loss and handle the graceful shutdown for me, but right now that extra 10-15 minutes of battery backup is enough for a manual effort.
This is why I have about five of these bad boys: CyberPower CP1500PFCLCD.
One is in my utility room for my cable modem and our chest freezer, three back up my homelab and wifi AP, and one is for my office.
They’ve been bulletproof through storms, and when we’ve lost power, but not Internet I can’t keep on working.
The big thing to look for is number of battery+surge outlets vs just surge outlets. Typically they top out at 1500VA - the more overhead for what you’re powering, the longer you can go without mains power.
A screen/display is helpful for at-a-glance information like expected runtime, current output, etc.
This is the right answer. I have dockerized Calibre and Calibre-Web for initial intake, then use Calibre-Web’s OPDS feed with my Moon+ Android app for reading on my tablet/phone.
Calibre handles type conversions, metadata sync, and file organization.
Calibre-Web works well for browser reading on my PC.
tmuxand a<ctrl>-<b><d>- done!