xcjs

If it does include a VPN provider, then you're correct - it would work for other applications.

I don't think it's common knowledge for people who don't have the app, so you may want to include information about that in your original post.

Just so you're aware why people are disagreeing with you - an installed browser does not change the behavior of HTTP calls made in other applications.

I wonder the same thing, to be honest.

It doesn't quite say that, but I think the meaning is essentially the same: "Don't choose a name after a project unique to that machine." - RFC 1178

For my homelab, I think that's fine to do. I'm unlikely to have multiple Plex servers locally, for example, and if so, numerically naming them is fine - I provision with Ansible, and if I'm at the point where I'm having sequentially numbered hosts, they'll be configured as cattle anyway. Also, having the names reflect the services a host provides makes it easier to match in my playbooks.

I think it's a better scheme than turning to mythology, fiction, or animal species, which oddly enough RFC 1178 does encourage you to do.

I use significant hardware component or model:

• Z390
• AERO15

...or sometimes intended purpose:

• USERV - Ubuntu SERVer
• PlexBox - Plex Server
• NAS - NAS
• Runner - GitLab Runner
• MDEV - Mobile DEVelopment
• MDEV2 - Mobile DEVelopment, Version 2

I also have a Kubernetes cluster that ranges from K8S_0 to K8S_5.

It's very impressive! I try to write legible code first, and if my shell scripts get too complex, I move on to another tool typically:

• C# scripting
• Python
• PowerShell
• Node.js

That might be why I don't have many cryptic examples.

That's certainly a script! 😅

It's not bash itself that was the complex part exactly, but I have a CI/CD pipeline that generates epub files from markdown. In some cases I have custom designed covers, but where a cover doesn't exist I have a bash script generate one using Imagemagick.

I wanted to generate the cover in one command to lessen performance impacts and disk I/O, but it took me a few weeks to figure out how to do it all in a single Imagemagick command:

convert \
    -size 960x1536 \
    -background "${backgroundColor}" \
    -fill "${textColor}" \
    -font "Liberation-Serif" \
    -pointsize 96 \
    -gravity north \
    caption:"${title}" \
    -bordercolor "rgb(0, 0, 0)" \
    -border 2 \
    -bordercolor "${borderColor}" \
    -border 40 \
    -background none \
    -fill "${textColor}" \
    -font "Liberation-Serif" \
    -pointsize 48 \
    -gravity south \
    -geometry +0-800 \
    -annotate +0+40 "${author}" \
    "${destination}cover.jpg"

Eventually it made an abstract sense to me, and I was able to bring it down to two commands and then finally one. This generates a cover with a selected background color (based on content type) and contains title text that will wrap to an inner border.

I think I had to give up on the author being wrapped, but it's much smaller than the title anyway.

Our midwest company just lost three large clients in one month and had to lay 10% of our workforce off, so we're not on the upswing yet.

Always has been.

Same story here, and Connect seems to be the furthest along.

I'll probably switch to Sync for Lemmy when it makes it's debut, but Connect is almost a good enough replacement.

I'm still using the old docker-compose executable - my Docker role is still installing it until the Ansible module catches up.