After migrating home user data to a new installation, I saw that kbfs won't start because there are hardcoded paths in the config file (Linux) which refer to the numeric UID of the user. It is best practice that programs do not rely on that UID being static (see migration issue). Instead, the paths should be determined at run-time.
Specifically, in $HOME/.config/keybase/config.json, "mountdir": "/run/user/1000/keybase/kbfs" should be something like "mountdir": "/run/user/$UID/keybase/kbfs".
After migrating home user data to a new installation, I saw that kbfs won't start because there are hardcoded paths in the config file (Linux) which refer to the numeric UID of the user. It is best practice that programs do not rely on that UID being static (see migration issue). Instead, the paths should be determined at run-time.
Specifically, in
$HOME/.config/keybase/config.json
,"mountdir": "/run/user/1000/keybase/kbfs"
should be something like"mountdir": "/run/user/$UID/keybase/kbfs"
.Keep on creating great software!