It’s literally all I wanted to do when I saw the .bond TLD came up for registration.
It’s literally all I wanted to do when I saw the .bond TLD came up for registration.
You can take stronk.bond from my cold dead hands.
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.deb
Now 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.
Adding to the Nazi comment - substack is basically a long form blog format, very similar (AFAICT) to Medium.
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
How are we supposed to opt out? By deleting our accounts?
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.
Seriously, make an effort. These took me 30 seconds and only a slight reprompt tweak.
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.
Ah, I wonder if it’s something with the Wasabi S3 hosting. I’ll check into it.