stopcoffee77

hace 11 mesesdiscuss

I am trying to contextualize git-based dotfiles.

  $ context set universe://work/customer-a/devops --update-dotfiles

will "render" and apply one set of dotfiles

  $ context set unvierse://work/customer-b --update-dotfiles

another set

  $ canvas dot apply [email protected]:workspace-foo

Will apply all dotfiles of a workspace-foo (git clone repo, symlink)

  $ canvas dot apply [email protected]:workspace-bar/shell/bashrc

will apply dotfiles of workspace-bar/shell/bashrc

yes, complicated, probably hard to comprehend/reason about, work in progress

stopcoffee77

hace 11 mesesdiscuss

I can no longer edit my original dot manager comment so to add some context: I developed an allergy for the term "vibe-coding" (and made a joke on the selection of OPs words), AI won't turn a lazy unskilled inexperienced person into John Carmack, lazy person + AI still equals to a lazy person. With that being said, most of you may have already experienced a divide between the above empirical truth and management decisions across your favorite corporate environments. So, the race is on, AGI-level agentic frameworks may be here soon enough to mitigate the above, then again, in the end isnt the enduser of most of our economic production directly or indirectly a human? Can a synthetic immortal system really cater for human needs? There is a reason why big deals are always negotiated in-person

stopcoffee77

hace 11 mesesdiscuss

Not exactly but almost https://containertoolbx.org/

stopcoffee77

hace 11 mesesdiscuss

Here you go

  # Roaming bashrc profile
  function sshrc() {
      BASHRC=$(cat ${HOME}/.bashrc_roaming | base64 -w 0)
      ssh -t $@ "echo \"${BASHRC}\" | base64 --decode >   ~/.bashrc_roaming; \
      bash --rcfile ~/.bashrc_roaming; \
      rm ~/.bashrc_roaming";
  }

stopcoffee77

hace 11 mesesdiscuss

[dead]

comments