dynnamitt

#!/bin/sh

# ========================================================================
#
#   This is requires since we always assume a ROLE inside Terraform(go-sdk),
#   BUT when we RETURN to shell we have a different IDENTITY.
#   This shell IDENTITY must again assume the same "inside-TF ROLE" to 
#   be successful in using aws-cli 
#
# =========================================================================

dynnamitt

#!/bin/sh

# From intro-video https://www.youtube.com/watch?v=Ng1YPjveaWg&t=1010s

# https://github.com/nvm-sh/nvm#installing-and-updating

nvm install v18.16.1 -- node
nvm install v18.16.1 -- npm

npm install -g purescript purescript-psa spago pscid

dynnamitt

#!/bin/sh

URL=${1:-https://releases.hashicorp.com/terraform-ls/0.32.7/terraform-ls_0.32.7_linux_amd64.zip}
wget -qO- $URL | bsdtar -xvf-

dynnamitt

#!/bin/sh
mkdir -p $HOME/tofuutils/tenv
# wget https://github.com/tofuutils/tenv/releases/download/v1.2.0/tenv_v1.2.0_Linux_x86_64.tar.gz
tar -xvf tenv_v1.2.0* -C $HOME/tofuutils/tenv
for f in $HOME/tofuutils/tenv/{tenv,terraform,tofu,tf}
do 
  ln -s $HOME/$f $HOME/.local/bin/$(basename $f)
done 

dynnamitt

#!/usr/bin/make -f
#  needs jq, terraform, git

SHA = $(shell git rev-parse --short HEAD)
TF_WRKSPC = $(shell terraform workspace show)

SUFF = $(SHA)-$(TF_WRKSPC)

.PHONY: summary

dynnamitt

HTMX vs React: Critical Assessment for Hathor

Context

Hathor is a CRUD admin panel for a national vehicle registry (Sobek). It displays ~2-3 entity types (VehicleTypes, DeckPlans) in data tables with sidebar editing, search, and an XML import wizard. The user dislikes React and wants to know if HTMX could simplify things.

Honest Assessment

What React is doing here (and whether it's earned)

dynnamitt

dynnamitt

# custom repo (contains bevy-ecs, federated-search, netex-opinions)
dynnamitt/skill-sets

# web / frontend
htmx
frontend-design
building-components
web-design-guidelines
vercel-react-best-practices
vercel-composition-patterns