Posts

Showing posts from April, 2021

Scaffolding PowerShell Modules with Plaster

Plaster is a very novel idea, but in practice I can see why it's gone mostly untouched for a while. There is a rather steep leaning curve for what it does. These are the goals Plaster is trying to achieve: Scaffold a base PowerShell Module project based on prompted parameters Allow for flexibility in the above process by incorporating custom scaffolding processes The former is indeed desperately needed. It's a good, solid, repeatable and consistent way for module to be created. The latter thou, makes the process needlessly complex, because: Who Generates the Generators? There are lot of good docs on the process, but even their own examples are either outdated or just wrong. In the end, I wound up creating a template based on the mega example that asks for options such as: Pester test, Psake building,  PlatyPS doc gen, and Git with editor VS Code. First time running the project from the template, Psake puked a bit - trying to find the name of the module, so I updated the Plaster

WSL - Installing Fresh on Win10 in 2021

Installed with: choco install wsl -y Continued install with: https://docs.microsoft.com/en-us/windows/wsl/install-manual While moving from WSL 1 to 2, had this pop-up: Virtual hard disk files must be uncompressed and unencrypted and must not be sparse ... and after a quick Google-Foo: https://simplernerd.com/wsl2-uncompressed/ cd ~\AppData\Local\Package\CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc ii . Go to the properties on the directory: LocalState Uncheck: "Compress contents to save disk space" and "Encrypt contents to secure data" Apply Then: wsl --set-version Ubuntu-20.04 2 wsl --set-default-version 2

Fine-Tuning Skills with PowerShell Modules

 I resumed work on a project to dive deep into Plaster - a tool for auto-generating Modules with custom configurations built-in, instead of having to remember how to create a module each time. In the past, I had just copied one module and changed the GUID info. It was tedious, but it worked. This time around, I'm focusing on making it easily repeatable. Using: Plaster to gen the new module. psake for code build process. Pester tests PlatyPS for dynamic help markdown gen

Fallout 3 (2008) on Windows 10 in 2021

Preface I'm adding a log of things I'm working on (both professional and fun), as a way to both document experiences and remember what the hell I did. Otherwise, it's lost to the ages just like the very early web cam sessions I did with both of my sons, which were lost to a hard drive failure. For the last 10 years or so, I had shifted my attention to family & work. I avoided large game titles. Now, it's time to play again. Fallout 3 : Post Install from Steam in 2021 Just finished Fallout 4, at least to the point of finishing every main quest and last DLC with Nuka-World Open Season. Prior to that Fallout: New Vegas. Wasn't sure if I wanted to try 76 or 3 next. Opted for the latter. In retrospect, I should have both consulted Reddit, Steam Community and/or Nexus Mods before trying to run the 13 year-old game. https://steamcommunity.com/app/22370/discussions/0/828937546147175081/ GFWL Fix: https://www.nexusmods.com/fallout3/mods/22591 Intel Fix: https://www.nexus

DevOps: My Perspective

Several will say that the key to implementing DevOps in an organization is collaboration.  While true, the idea and willingness to collaborate is imperative, in the real world, people hate change, talking to people in different groups and generally going outside of their realm of comfort.  The most effective way to accomplish this sense of collaboration is to start with baby-steps: Little things that stretch beyond comfort levels and the willingness to do so.  So, if I were to use one word to describe DevOps: Initiative. It may sound strange, but a little initiative goes a long way to show what can be done.  Unlike traditional change, introducing DevOps into an organization does not have to come from the "top down." Everyone has it in them to make that first baby-step.  That first step is to take an inventory of systems, services, applications, processes and practices. This analysis step is the vital foundation stone for everything to come. If documentation doesn't exist,