https://chrisworth.dev/skill-tag/devops/Recent content in DevOps on Chris WorthHugoen-usWed, 10 Dec 2025 16:57:31 -0600https://chrisworth.dev/posts/power-platform-cli-alm-solution-extraction/Wed, 10 Dec 2025 16:57:31 -0600https://chrisworth.dev/posts/power-platform-cli-alm-solution-extraction/<p>Manual Power Platform deployments create unnecessary risk. Exporting solutions through the UI produces opaque .zip files with no visibility into what changed. Canvas apps remain binary .msapp files that source control can&rsquo;t diff. Teams work blind, with no code review process and no way to track who changed what or why.</p> <p>The Power Platform CLI solves this by extracting solutions and canvas apps into source-controllable files. Once unpacked, you can version components in Git, review changes in pull requests, and automate deployments through CI/CD pipelines. The workflow transforms Power Platform development from manual exports to proper application lifecycle management.</p>https://chrisworth.dev/posts/arch-linux-development-environment-guide/Sun, 23 Mar 2025 18:00:00 -0600https://chrisworth.dev/posts/arch-linux-development-environment-guide/<p>Development environments often accumulate bloat over time. Hidden services consume resources, background processes you didn&rsquo;t authorize run constantly, and update mechanisms interrupt workflow at the worst possible moments. After years of managing enterprise systems and implementing automation solutions, I found that traditional distributions introduced unnecessary complexity that directly impacted development efficiency.</p> <p>The problem became clear when I noticed development machines taking 30+ seconds to boot, consuming gigabytes of RAM before opening a single application, and running dozens of services irrelevant to actual development work. The solution: a lean, transparent system where every component serves a clear purpose.</p>