It's been a while since I had the muse to write here, but this has indeed been fruitful.
Since creating the package concept, using my scripting environment truly became comfortable.
I've started using it, modifying my docker helper commands a bit more, adding some additional concepts, and just plain using it without felling alienated in any way.
PowerShell has become my native Linux command line.
I still have a grasp of c-shell or bash, but for the most part, I'm comfortable remaining in PowerShell.
This effort to make PowerShell my home in Linux, made PowerShell a lot more usable for me everywhere. Could be because it was not a first class citizen on any of the platforms originally, could be just because of the resolution to commit for a while.
Bottom line, I'm sticking with it, but there is still much work to be done.
A sucker for abstraction
One thing I'm usually striving to is 'uniformity of abstraction', what I mean by that is that regardless of which environment I am working in, I want that environment to react in as similar a way as possible to any other environment.
It's tough, and being a senior procrastinator, it takes a long time to get things to that state. But that's another aspect PowerShell makes it easy (for me) to deal with it.
The (core) .net Framework surrounding PowerShell is such a versatile one, that makes most of my efforts worthwhile and the results enjoyable.
Cut the crap! What do you do with it?
OK, so what do I do with the shell?
Mostly I manage my media server, which is docker container based, so a lot of docker commands and scripts. Those are all part of the docker package.
Since I help a few of my friends with their Linux-docker based media servers, I run manual maintenance via Ansible - this allows me to stay on top of system state, and control upgrades of packages manually.
As I mentioned before, I keep my scripts updated in a git repo, so when I edit a script on one machine, I can commit it to the repo, and using Ansible have all the servers pull the change at once.
I think going forward, there isn't going to be a whole lot of development to report on, so it might be a good time to dive deep into the package from the beginning, this time taking a guided tour into the script dir, installing it, and using it.
Evolving from usage to maintenance, and then detailed analysis of the structure, should be a good guide to whoever (including myself) chooses to review the code in the future.
Until the next update.