brettkolodny / dev-setup

Files and scripts for me to run when setting up a new system

dev-setup

Files and scripts for me to run when setting up a new system

Setup Fleek

1. Install fleek and Nix
2. Copy ./fleek.yml to ~/.fleek.yml
3. Run fleek apply
4. Add the following to ~/.zshrc to stop nix from breaking on OS updates:

if [ -e '/nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh' ]; 
then
  . '/nix/var/nix/profiles/default/etc/profile.d/nix-daemon.sh'
fi

If all went well all of the fleek packages should now be available!

Setup Helix

1. Copy the ./helix directory to ~/.config/helix

Global NPM packages

Because fleek packages are deterministic it will get mad if you try to install global NPM packages by default.

To fix this add the following:

1. Create/edit the file ~/.npmrc.
2. Add the line prefix = ${HOME}/.npm-packages.
3. In ~/.zshrc add the following:
   • export PATH=~/.npm-packages/bin:$PATH
   • export NODE_PATH=~/.npm-packages/lib/node_modules
4. Look at ./npm-global.txt and install the current binaries.
   • Note some of them are generated from others (i.e. pnpx from pnpm) so use your best judegement!

Faster Keys

Run the following to increase key repeat speed:

defaults write -g InitialKeyRepeat -int 10 # normal minimum is 15 (225 ms)
defaults write -g KeyRepeat -int 1 # normal minimum is 2 (30 ms)

Trouble Shooting

Below are some common issues I ran into and how to solve them.

Trouble Shooting Tmux

If the delete key in tmux isn't working do the following:

1. Create/edit the file ~/.tmux.conf
2. Add the line set -g default-terminal "xterm-256color".
3. Run tmux kill-server to restart the server.

Trouble Shooting Fleek

At the moment hostnames seem kind of wonky and will just change. I suspect this is partly to do with changing networks (i.e. WiFi, ethernet, hotspot).

If this happens fleek apply will fail. The fix at the moment is as follows:

1. Get your current hostname by running hostname.
2. Rename the hostname line in .fleek.yml to this new hostname.
   • Pay attention to the old hostname, we'll need it later!
3. Run fleeks to navigate to your fleek setup.
4. Copy the directory named after the previous hostname to a directory named after the current hostname.
5. Run fleek apply.

Updating

Whenever a change is made to ~/.fleek.yml, ~/.config/helix/*, or a glogal NPM package is installed run ./update.sh.