It takes a bunch of time to config everything (and I change it pretty often), so
I versioned the config files to git clone and get up and running easily.
In addition, I developed a series of scritps to install in a barebones OS
(Windows and Debian Linux) so I can break everything that the worse case scenario
is to run a script and have a new machine in less than half an hour.
Copy and paste any content as much as you like!
Windows and Linux are for exclusive scripts (installation and some apps). I
generally want to develop as much as I can in the .config and nushell
folders. Those can be symlinked into every OS and usually are crossplatform apps.
In windows almost everything is managed by scoop, but I still have some CLI
apps that are isolated in its own managers:
-
For npm packages, list all the globals with:
npm list -g --depth=0 -
cargo has its own packages, so list them with:
cargo install --list -
For python packages, I use
pipx(black, mypy, flake8, all-repos & pipenv) you can get the currentpipxpackages withpipx listTip: If you don't find
pipxon PowerShell, try to add manually to PATH. SourceProbably it will be that this is not in PATH.
C:\Users\aucac\AppData\Roaming\Python\Python311\Scripts
I like to have everything in its own little isolated box. So the boys don't play
hard on each other. I use pyenv and
pyenv-win to manage Python.
fnm to manage NodeJS.
Follow this tutorial to start backing up your dotfiles and to install them on a new system
On windows, in PowerShell with admin priviledges:
New-Item -Type SymbolicLink -path ~/.gitconfig -Target ~\repos\dotfiles\.gitconfig