| nixos solves private keys and tools switch easy.
for folders, i ended up with overlays.
just follow origin upstream remote locally so that http and file united. i mean if remote is https github com slash dzmitry lahoda slash web3.nix than local is /home/dz/github com slash dzmitry lahoda slash web3.nix navigation is easy. forks easy. no project1 or client 1. just navigation overlay. same works for consumption of knowledge and learning. one may do codespace with nix easy too or many local homes. nix and path overlays is superior and easy to maintain. nix makes remote, local, ci, codespace, user switch, depending on dlmany versions of same repo super easy. even by unix idiots like me. that not full schema so. there are tags and data properties (security, size, files count, uniquiness of copy). so decide if store local or remo only, git and syncthing same time, torrent and syncthing, gdrive and git, keepass and syncthing, what devices, ipfs. any combo. tags when overlays (forced hierarchy fail). when git forks, than many remotes with overlay following most active fork. that approach partially fixes some of my mental issue i guess. oh, i want to install zfs to fix duplication. hardware keys for security i use also. thesd days can mix same key, but held ssh, crypto, aws creds on same device. |