This is dumb.
You could do all that stuff with bash scripts but it would be a management nightmare. You’d also be completely reinventing the wheel.
If anyone seriously thinks this is a good idea, please post your LinkedIn so I know to never hire you.
I have a function called up. I do up X where X is the number of directories I want to go up.
up() {
if [[ $# -eq 0 ]]; then
cd ..
return 0
fi
local path i
for (( i=0; i < $1; i++ )); do
path+=../
done
cd "$path"
}
EDIT: Don’t know if it’s just me but if you see < it should be the less than character.
Don’t overthink this. Just start using something.
I set my mom up on slackware like 15+ years ago. She wouldn’t have known how to break it if she tried.
The unix philosophy is about what runs as processes at the system level.
I don’t know what you mean by “system level” (cat is userspace) but I don’t believe there is any clarification about what kind of applications should apply to the unix philosophy or not. It doesn’t say that applications “should do one thing and do it well only if it is a system process or terminal based program built for purely shell environments.”
Also, if the argument was exclusively about OS processes, dbus should be in the firing line of everyone in the anti-systemd camp too. That never gets the same level of hate.
The unix philosophy is old and, while nice to have, is insufficient to fully address the needs of the modern world. It’s not as simple today as it was in the 1960s and 70s and we need to embrace change to progress.
Does too much for one tool (against unix philosophy)
This tired, old argument needs to die already.
Do you use browser extensions? That breaks unix philosophy too.
Yeah I agree. It was rolled out pretty early in its development maturity so it undoubtedly left a bad taste in some people’s mouths. Overall it’s a net positive though. I don’t want to go back to the old way.
Debian and RedHat based distros typically do not bundle them together. The have separate -dev and -devel packages for headers.
If you need the python header files, depending on your distro, you may need to install python3-dev, python3-devel, python3, or some other variation on the name. For a novice, this might not always be obvious and they might not know things like apt-file are helpful for figuring it out.
True. It’s the dependencies of dependencies where the tricky part starts.
Usually the only tricky part of compiling from source is tracking down dependencies. The package manager does that for you normally but you’re not using the package manager when compiling from scratch. The actual building (even compiling a kernel) isn’t all that complicated.
Mostly as kodi/plex front ends. I’ve set them up as a kubernetes cluster in the past but they didn’t have enough ram to run my torrent client. Now I just use an old Thinkpad running talos.
Certbot in cron if you’re still managing servers.
I’m using cert-manager in kube.
I haven’t manually managed a certificate in years… Would never want to do it again either.
Back then, shit was pretty rough though.
Bro no kidding… You’d install and hoped your keyboard worked by the end of it.
I stuck with it though… Well over 20 years for me now.
EDIT: I actually remember digging through dbus configs one time for HOURS because I couldn’t get my mouse working. No joke I realized at like 3am it wasn’t plugged in. Hahah… It was such a pain in the ass back then you just assumed it was something insane.
It auto discovers machines/instances/VMs/containers in the mesh and figures out the secure routing on the fly. If you couldn’t ensure a consistent IP from the home address it wouldn’t matter… The service mesh would work it out.
It is probably overkill for this project though… Something to think about…
With Prometheus I would add a section to the scrap config to rewrite the labels attached to each metric. Does such a thing exist for telegraf? I’ve never used it.
Or could you change the grafana query to just aggregate the values for all pods in that deployment?
Istio is a service mesh. You basically run proxies on the vps and the rpi. The apps make calls to localhost and the proxy layer figures out the communication between each proxy.
Duck dns is just a dynamic dns service. It gives you a stable address even if you don’t have a static ip.
This would be nice because I don’t need a static ip and I don’t have to leak my ip address.
How does the VPS know how to find your rpi?
Could you not just use something like duck dns on a cronjob and give out that url?
I would also need to figure out how to supply ejabberd with the correct certificates for the domain. Since it’s running on a different computer than the reverse proxy, would I have to somehow copy the certificate over every time it has to be renewed?
Since the VPS is doing your TLS termination, you would need an encrypted tunnel of some sort. Have you considered something like Istio? That provides mTLS out of the box really… I’ve never seen it for this kind of use case but I don’t see why it wouldn’t work.
Figured this would be one of the responses. Thanks. I don’t interact with node very often. I assumed there was a better option but wasn’t sure which… This is just the first result.
Yeah I am deep in the kube world as well. Since this industry-wide shift started happening, I feel like I write essentially no code anymore outside of bash scripts to glue things together. It’s essential but it’s not a replacement.
This cartoon seemed to me to be suggesting that you could implement the behavior of kube with bash. That’s obviously absurd.