Repositories are intended to live under:
$HOME/Source/github.com/<owner>/<repo>$HOME/Source/gitlab.com/<group>/<repo>$HOME/Source/github.com/<owner>/<repo>--<alias>for additional local clones$HOME/Source/gitlab.com/<group>/<repo>--<alias>for additional local clones
This is created automatically during Home Manager activation.
If you want a different workspace root, set ORIGIN_WORKSPACE_ROOT in machine/local.env.
This setup rewrites these protocols to SSH:
https://github.com/...->git@github.com:...https://gitlab.com/...->git@gitlab.com:...
With clone:
clone github your-user/origin
clone github your-user/origin sandbox
clone gitlab my-group/platform/api
clone git@gitlab.com:my-group/platform/api.git qaWith ghq:
ghq get git@github.com:<owner>/<repo>.git
ghq get git@gitlab.com:<group>/<repo>.gitDirect:
git clone git@github.com:<owner>/<repo>.git "$HOME/Source/github.com/<owner>/<repo>"
git clone git@gitlab.com:<group>/<repo>.git "$HOME/Source/gitlab.com/<group>/<repo>"- primary editor:
Vide, the IDE developed by ubugeeei. It is the editor used day to day, but it is not open-source, so it sits outside this repository's reproducible setup. - secondary editor:
Zed - verification editors:
VS CodeandNeovimare not daily drivers here; they are mainly kept around to verify editor integrations and LSP behavior for tools developed by ubugeeei - frequently used languages:
Rust,TypeScriptwithVue,tnix, andHaskell - shell:
ushmeans "ubugeeei sh", the modernshdeveloped by ubugeeei; it is the default login shell here, with zsh still available - typed Nix:
tnixmeans "type nix", the Nix type system developed by ubugeeei; repo ambient declarations live undersrc/tnix/types/, runtime source-of-truth lives undersrc/tnix/src/,./src/tnix/sync.shcompiles gitignored outputs intogenerated/,flake.nixreads machine config, packages, and darwin modules from there,src/nix/home/default.nixis the remaining handwritten Home Manager entrypoint, the checked-in workspace entrypoint issrc/tnix/workspace.tnix, upstreamtnixdeclaration packs are read from$HOME/Source/github.com/ubugeeei/tnix/registry, Zed enables thetnixextension, and Neovim auto-attachestnix-lspwhen it is on PATH for verification work src/ush/is source-only and now holds the.ushimplementation for every repo command, while_legacy/*.shkeeps shell entrypoints and compatibility wrappers; bootstrap-oriented entrypoints stay POSIXsh, and operational helpers such asapply,clone,doctor,init-repo,remove-unused-apple-apps,set-default-browser, andfetch-github-profile-iconrun throughush- prompt: starship
- runtime manager: Vite+ (
vp env) - secondary runtime manager: mise (installed, but not auto-activated)
- container runtime: Colima + Docker CLI
Start Colima before using Docker:
colima start
docker version- Use
vp env doctorto confirm the shims are first in PATH. - Use
vp env pin ltsorvp env pin 22inside a project to create.node-version. - Use
vp env installto download the pinned or default Node.js runtime. - Use
vp install,vp dev,vp check,vp test, andvp buildin JS projects instead of managingpnpmornodefrom Nix. ushis the default shell here. For project pins, use.node-versionorvp env exec ....- If you want session-local
vp env use <version>behavior, open a zsh session for that workflow. - Standard user-managed toolchain bins such as
~/.moon/bin,~/.cargo/bin,~/go/bin,~/.bun/bin, and~/Library/pnpmare also on PATH when those directories exist. miseis available too, and~/.local/share/mise/shimsis kept on PATH for shell and GUI sessions.- Auto-activation is intentionally off so
vp envremains the default Node.js flow. If you wantmise activatebehavior in a shell, opt into it manually for that shell session.