Whenever I set up a new Apple device, I can pretty much guarantee that it will end up being completely differently configured from the one it's replacing.

Right now I'm writing this on a 2018 MacBook Pro, which replaced a 2013 MacBook Pro. I also use a 2019 MacBook Pro.
Add to that a couple of iPads (work and home) and an iPhone (11 at the moment) and we've got about 4 devices that are all configured differently from their predecessors.

I'll give you an example based on macOS.
The idea behind the chosen applications on this MacBook Pro is: use Open Source or free software, where possible.

I used Panic's Coda for a long time as my primary editor.
That was replaced by Sublime Text, replaced by Atom, which has now been replaced by Visual Studio Code.
Same tasks/ use, different approach and work flow.

This replacing/ changing procedure is not restricted to applications, I do this with any part of the system/ my work flow. And not because I don't like paying for software, no. I hold valid licenses for the applications I replaced in favour of Open Source/ free software.

The aim is to learn about different apps/ approaches to solve problems.

Some more examples:

• Browser: Safari -> Firefox -> Google Chrome -> Safari -> Vivaldi -> Safari -> Brave -> Safari & Chromium
• git client: Tower -> GitKraken -> Tower -> SourceTree 3/4 & command line
• Email client: Mail -> AirMail -> Mail -> Spark & Mail -> Mail
• Terminal: Terminal -> iTerm [ZSH] -> Hyper [ZSH] -> iTerm [ZSH] & electerm
• Note taking: Evernote -> Apple Notes
• Menubar calendar: Fantastical -> popCalendar -> itsycal
• Window manager: Divvy -> Spectacle -> Rectangle
• App remover: AppZapper -> AppCleaner
• Cloud storage: Dropbox -> iCloud & Nextcloud
• Bulk file rename: Renamer -> NameChanger
• Local Search/ App Loader: Alfred -> Spotlight -> Alfred [Powerpack]

I have a very hard time replacing Adobe applications. They are what I learnt on and am comfortable with. But as I just let my Creative Cloud subscription expire, I don't really have a choice but to find alternatives for all the applications I used out of that!
Let's see how that goes...
Full disclosure: At work I still have an active subscription to fall back on.

The above detailed app swaps are not always 100% feature identical, but they do what I, personally, need them to do on a daily basis.

Homebridge is an utterly brilliant project and I've been relying on it for several years, connecting all the little "smart" things around the house that don't have native Homekit support.

Recently an update to 0.4.49 broke the lot. Not the first time this happened, but this one was different from the times before. It just would not reconnect, not even as a completely empty config.

I'm not going to go into the details of how to set Homebridge up in this post, I'll leave that up to you to explore, if you wish. I'm using oznu/docker-homebridge.

Anyway, after working on it for the better part of the weekend, I came across a post on reddit mentioning the same problem(s) I've been experiencing, but this one had one additional bit of info in it, none of the other posts included:

"mdns": {
   "interface": "[YOUR INTERFACE IP]"
},

Adding this to my config at the very top, with the appropriate IP address, made Homebridge discoverable again!

Thank you very much u/tokeraabjerg!

OK, I hope this post will help someone avoid what I went through the last few weeks.

If you have a Supermicro based server that includes an IPMI BMC and you happen to upload a valid SSL certificate, but the IPMI's web interface does not come back up after a restart ... you can fix it ... relatively easily.

Download the IPMI tools from the Supermicro website, create a DOS (or Linux) based, bootable USB stick and copy the IPMICFG tool onto it.

Boot from the USB and run the following command to reset the IMPI, clear the SSL certificate and generate a new, locally signed one, while you are at it:

ipmicfg -r

That's it.

Funny enough, the -r option is not documented in the IPMICFG User Manual.
I got that from a very helpful Nutanix technician.

Once run, the node reboots and comes back with a functioning web interface, at least it did in my case.

Unfortunately, I can't guarantee the above will work for everyone, but for Nutanix NX 3060-G4 nodes, it does.

At this stage the recommended way of executing the artisan command in a docker environment is to run a container whenever one needs artisan.

The below is my setup on Linux/ macOS.
In ~/.zshrc (or ~/.bashrc or whatever flavour of console you are running) create the following function:

artisan () {
    docker run \
        -t \
        --rm \
        -v $(pwd):/var/www \
        vcarreira/artisan "$@"
}

Then run source ~/.zshrc and you'll be able to execute artisan the same you're used to it.

The first time you execute the artisan command, docker will pull the image vcarreira/artisan.
The container will run, stop and remove itself as needed.

There are options to vcarreira/artisan on Docker Hub.
Pick whichever works for you.