victor on Nostr: verita84 :Debian_logo: :firefox: :bing: :android: They call me Spitfire :pepeOK: ...
verita84 :Debian_logo: :firefox: :bing: :android: (npub1zna…wtpl) They call me Spitfire :pepeOK: (npub1c9k…727g) That's just a discipline thing. Whether you create containers or services directly on the host, you have to document it or you're going to forget (even if you say you won't, I know).
I like to keep a local git repo with Markdown files, and each time I do some infrastructure stuff, I add a new file (or add to a previous one if appropriate, e.g. if modifying or adding to a service) and document it all there.
Then that serves as a starting point for writing Ansible playbooks and/or roles later on if I find myself doing the same thing often.
I like to keep a local git repo with Markdown files, and each time I do some infrastructure stuff, I add a new file (or add to a previous one if appropriate, e.g. if modifying or adding to a service) and document it all there.
Then that serves as a starting point for writing Ansible playbooks and/or roles later on if I find myself doing the same thing often.