How yaravind/dev-tools works
Main Components
a. Installation Flow:
• To the main "setup_env.sh" orchestrator
• Branch out to various installation categories
b. Tool Categories (group components by purpose):
• Development Tools (JDK, Maven, Python, Node.js)
• Shell Utilities (htop, tree, jq, etc.)
• IDEs (IntelliJ, PyCharm, VS Code)
• Package Managers (Homebrew, Conda, Micromamba)
• Version Managers (jenv)
c. Configuration Components:
• Shell RC Files (.zshrc, .bashrc)
• Git Configuration
• Environment Variables
• Font Configuration
[User Input] -> [Prerequisites Check] -> [Main Orchestrator (setup_env.sh)]
• [Package Managers] [Development Tools] [Shell Configuration]
• [Tool Installation] [Version Managers] [RC Files Setup]
Important Relationships
• Dependencies between components (e.g., Homebrew required for other installations)
• Configuration flow (how .zshrc/.bashrc are updated)
• Tool version management (jenv's relationship with Java installations)
• Verification steps and success indicators
Additional Elements
• Version information for critical components
• System requirement checks
• Points where user interaction might be required