This article explains how I solved a couple of challenges of getting my initial environment and configs into Git — the first steps to GitOps.
I’ve been wanting to embrace GitOps for quite some time, but it’s always tricky to know where to start. Do I use Jenkins Jobs — I know Jenkins well? It’s a bit old school though, maybe I should be using Ansible Tower. I’ve heard things about ArgoCD, and lots of others. The truth is, I can’t do anything until I actually have my environment and configuration stored in Git.
Knowing a few key shortcuts can have a surprising impact. As someone who sits frequently with others over a command line to help debug code and navigate servers, it’s easy to become frustrated on their behalf at how cumbersome things can be when you may not know time-saving shortcuts.
Here are some essential shortcuts and key tips to help you speed up your command line usage.
We’ve all been there, you just want to hack up a quick Ansible playbook to do a quick task, and then you find yourself fighting with syntax, chopping and changing things around, wondering why this simple Ansible playbook isn’t working. Let me give you a few hints to make your life easier.
This is especially useful if you’re on a new machine that doesn’t come with all your personal configuration, dotfiles and preferred editors! This happens to me quite a lot when setting up new environments.
James is a "full stack" Open Source enthusiast, who enjoys creating no-nonsense open source software.