mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

12K
active users

#bash

36 posts35 participants7 posts today
Continued thread

It's possible you've not heard of #boxyBSD

I was lucky to get a TIL moment when @stefano boosted it's existence into my feed.

However you should know about it, learn something about the user perspective from proxmox in the process, while working with a boxyBSD VM.

Here are some nice screencaps of the boxyBSD site so you can ask nicely for a VM and learn to play with one of the *BSD flavours from a distance.

I'm sure you can duckduckgo the address of boxyBSD when you analyze the screencaps, right?

🖋️ #bash #proxyLB #freeBSD #boxyBSD #sh #zsh #ksh #csh #netBSD #openBSD #POSIX #proxmox #loadbalancer

I am a fan of #golang. I don't say it enough. My love of #python, #bash, and #BASIC, I wear on my sleeve, but among the many other languages I code in, I almost always appreciate an opportunity to use Go. It just clicked for me in a way rust never did.

(Obligatory disclaimer upon realizing the date that this is not an April Fools post.)

Continued thread

It has arrived. proxyLB v1.1.0 the loadbalancer for proxmox clusters. Instead of telling you the features of this major version I invite you to read about it yourself, download proxyLB then play with it.

As with any great Open Source project, this has grown out of a necessity that @gyptazy has for his other amazing project boxyBSD, which just needs a versatile tool like this.

Now go and play.

gyptazy.com/introducing-proxlb

🖋️ #bash #proxyLB #freeBSD #boxyBSD #sh #zsh #ksh #csh  #netBSD #openBSD #POSIX #proxmox #loadbalancer

Hay there fediverse. Do we have any #bash #cron experts that can help me figure out how to fix things?

TL;DR - I need to reference the `$USER` variable as a parameter in a shell script that forms part of a dynamic path in a backup routine (the location varies by host so trying to automate as much as possible). Running the script as a logged in user over SSH works perfectly but when I add a crontab entry under the same user to run the same script is fails to parse the `$USER` part so the destination is incorrect and it throws an error.

I should also note that if I specify the path manually in the script it also works, but then it's a pain to automate across different hosts so I'm trying to avoid that if possible.

I now been going round in circles trying to figure this out for a couple of days so it's time to ask for help.