How nizarcan/ncanrc works
Project type and purpose
• This is a dotfiles/configuration-management repository (“ncanrc”) whose purpose is to centralize, version-control, and automate the setup of development and shell environments.
• Key indicators: a top-level run.sh orchestrator, config/ directory for various tool configurations, scripts/ for operations (install, backup, clean), and utilities/ for standalone helper scripts.
File structure
• Top-level components:
• run.sh – the main entry point and CLI dispatcher
• config/ – subfolders per tool (alacritty, ghostty, git, nvim, tmux, zsh) containing dotfiles
• scripts/ – operation scripts (sym, brew, clean, backup, load_backup, etc.)
• utilities/ – reusable helper scripts, further organized into “personal”, “tmux”, “work”
• Patterns: a layered architecture where run.sh invokes scripts which in turn apply or manipulate files in config/ or utilities/
• External dependencies: Homebrew, Oh My Zsh, tmux, neovim, Alacritty, Ghostty, standard UNIX commands
README for additional insights
• README outlines available commands and maps them to specific scripts
• It describes usage of run.sh as unified interface
Detail
• Script’s purpose (label backups, installs, cleans)
• Backup flow: scripts/backup.sh → config/ → backup directory
• Don’t lump everything together: keep each tool’s config as its own block under the “Config Store”
• Extensibility: call-out how to add a new tool (add config folder + script + run.sh case)