Scripts

These are some non-secret scripts/configs I use locally to develop. Since I tend to break things, or redo my local setup I place them in version control

Fair warning

I highly recommend not running other people commands blindly on your machine. So I don't expect others to do the same with mine. Which is why the only documentation included; is meant for myself.

Setup

Run the install script. It adds bin/ and bin/local/ (gitignored, machine-local scripts) to PATH and sources every file under profile/ and aliases/ from your shell rc file (~/.zshrc for Zsh, ~/.bashrc for Bash), see ./install --help:

./install

Packages

packages/ holds the packages I installed by hand, one list per machine, so I don't have to remember them when I redo a setup. Dependencies and whatever the base image shipped with are left out.

Regenerate a list on the machine it belongs to:

create_brewfile     # macOS, writes packages/Brewfile
create_apt_packages # Debian based, writes packages/apt-packages-<flavor>.txt

create_apt_packages names the file after the machine it detects (wsl, pi, or the distribution ID); pass a flavor to write a different one. It reads the apt history log, so installs older than the oldest log are missed.

Install a list on a new machine:

brew bundle install --file=packages/Brewfile
xargs sudo apt install -y < packages/apt-packages-wsl.txt

Podman instead of Docker

WSL runs rootless podman, not Docker. Docker Desktop is installed on the Windows side with its WSL integration off, so the docker and docker-compose shims that PATH picks up from /mnt/c cannot run here.

podman-docker puts podman behind /usr/bin/docker, which comes first in PATH, so projects that call docker and docker compose work unchanged. Two settings are needed on top of that, and setup_podman writes both, see setup_podman --help:

xargs sudo apt install -y < packages/apt-packages-wsl.txt
setup_podman

Podman is not a drop-in in every respect. The host is host.containers.internal, where Docker calls it host.docker.internal.