2025-10-20 Notes

feedback@janusworx.com (Mario Jason Braganza) — Mon, 20 Oct 2025 07:11:21 +0530

Goals
#

Rejig the day
Get back to starting on the devops project

2025-10-20 07:15
#

Getting back to writing notes after two months.
Lots has happenend in that time.
Need to redo all the work I do and reshuffle them through the day
BIG Idea: Focus hours first thing in the day. Four hours. One half hour break in the middle
So the three Ss in the morning. meditation, back physio, making breakfast, feeding the pups in the morning
Then, start with the focus task of the day
Then, break for lunch and a nap
Then, French, and misc work (calendar/org tasks, system updates) and pottering about the house
Tea, followed by a walk
OSS work
Next self learning / hobby block. (Rustlings or Writing posts or working on Rust projects)
End with planning the day next, before turning in for dinner and bed

2025-10-20 07:45
#

And so we begin! Starting up where I left in the Bootstrapping Microservices Book
2025-10-20 08:55: Going well so far. There are distractions, but not much
Refamiliarised myself and got myself up to speed, much faster than usual
Best to have two separate Dockerfiles according to the book:
We can get away with having a single Docker Compose file that is parameterized by an environment variable, but I generally keep separate versions for testing development and production.
That’s because I like to have my production Docker Compose file mimic the real production environment as much as feasible. In addition, usually my development version will replace various microservices with mock versions for easier and faster testing, but when testing in production mode, it’s better to test the real microservices and not the mock versions.
2025-10-20 09:35: Saw an example of containers communicating directly with http
Learnt how to be dangerous with mongosh
2025-10-20 10:00: Tea break

2025-10-20 10:30
#

Back
2025-10-20 10:58: Got through whole chapter! On to chapter 6!
Updating kind on my machine
Learned that kind lets me have as many “nodes” as I want. This tiny snippet gives me a control plane and two nodes!

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
name: my-humongous-cluster
nodes:
 - role: control-plane
 - role: worker
 - role: worker

Kind has no access to my locally built images. I need to load them in …

kind load docker-image <image-name:n> # n is a version number tag

2025-10-20 12:50: Done for the day. Good progress
Had issues with kind. Will investigate Minikube tomorrow.

2025-10-20 19:00
#

Did Rustling for an hour. Head’s flummoxed with the final enums exercise
Did lots of housework as well
This new state of affairs has gone well for today
Let’s see how the next couple of weeks go

Feedback on this post?
Mail me at feedback at this domain.

2025-01-24 Notes

feedback@janusworx.com (Mario Jason Braganza) — Fri, 24 Jan 2025 07:54:32 +0530

Goal
#

Get Ansible doing things on my intel NUC

2025-01-24 09:15
#

09:15: Starting up and getting into the swing of things is the hardest part of the day. I’m still at a loss as to, what breadcrumb do I leave myself the day before, so that this struggle with stasis gets easier. maybe just leave a clue to myself, of what I was thinking about doing/tackling next
10:14: Got my ansible playbook validated with yamllint. Progress! And also the confidence that splitting my lines with the > does in fact keep it on a single line in practice
Note to Self: Struggling to make progress? Lower the bar. Lower the standards of what progress looks like. Make it easy. But make sure you show up!
Note to Self Deux: Learn about yaml block chompers: https://yaml-multiline.info/ & https://stackoverflow.com/questions/3790454/how-do-i-break-a-string-in-yaml-over-multiple-lines/21699210#21699210
Syncthing Note (for the next machine): Figure out where syncthing stores its config folder and regularly back it up. It’ll help with Ansible restores. You just have to dump the config back after mounting all the paths just as they were before with the same owner (probably before we do the install syncthing play?). The config’s in ~/.config/syncthing currently, but new machines/new installs might have it in $XDG_STATE_HOME/syncthing
Since my brain isn’t quite working, am making sure my playbook is validating with ansible-lint Love the tool. It’s instilling best practices into my muscle memory
Woohoo!
The playbook still executes 😂 On a more serious note, working to a predefined spec, makes life easy
Ok. it executed a little too well and I made a booboo. Now my NUC won’t boot. Be back whenever!

2025-01-24 11:45
#

Moving on the recovery stage.
Downloading a debian iso :)
writing image to a usb flash drive
Done. Now to the hard part. Rummaging in my table and connecting displays and all that jazz
12:17: and we’re back up! wow! This was good, trial by mini-fire
The whole playbook just paid for itself. I fixed my booboo, ran the playbook and the machine came right back to where I was! Hurrah for Ansible! This is amazing!
If it wasn’t for the downloading the iso and burrowing under the table to fix a keyboard and monitor part, I’d be done in 5 minutes actually.
Done for now. Be back later if I can. Or tomorrow.

2025-01-24 12:30
#

Client Meeting

2025-01-24 15:50
#

Back at work.
nginx installed
ok now to install the docker apt repo and install docker-engine
18:13: got it done! hurrah! pleased as punch :)

2025-01-24 20:14
#

Done!

Feedback on this post?
Mail me at feedback at this domain.

P.S. Subscribe to my mailing list!
Forward these posts and letters to your friends and get them to subscribe!
P.P.S. Feed my insatiable reading habit.

Docker-Nm on Janusworx

2025-10-20 Notes

Goals #

2025-10-20 07:15 #

2025-10-20 07:45 #

2025-10-20 10:30 #

2025-10-20 19:00 #

2025-01-24 Notes

Goal #

2025-01-24 09:15 #

2025-01-24 11:45 #

2025-01-24 12:30 #

2025-01-24 15:50 #

2025-01-24 20:14 #