How chickensoft-games/godotenv works
Project type and purpose
• Project: GodotEnv – a cross-platform .NET command-line tool
• Purpose:
– Manage Godot versions (download, extract, install, switch via symlink, set environment variable)
– Manage Godot addons (install from remote git, local repos, symlink, zip, resolve dependencies)
– Configure settings via commands (config list, set)
• Not a web app or microservice – it is a monolithic CLI application with well-defined internal modules and external dependencies (file system, network, OS environment, git).
File structure
• Top-level directories:
– GodotEnv/ : production code
– GodotEnv.Tests/ : unit and integration tests
– TestPackage/ : example package demonstrating addon usage (secondary example)
• GodotEnv/src common modules:
– common/clients (EnvVar, File, Network, Zip, ZipClientTerminal)
– common/models (Config, ExecutionContext, Asset, CLI command interface, OS types)
– common/utilities (Computer, Log, ProcessRunner, Shell, SystemInfo)
• GodotEnv/src features: three feature areas, each with Commands, Domain, Models, Serializers (for godot management and addons), plus Config commands
• Configuration & build: .csproj, solution files, GitHub workflows, omnisharp.json
README for insights
• Architecture isn’t drawn explicitly but command structure is clear—commands map to feature modules
• External interactions: git, HTTP downloads, file system, OS environment variables
• Caching layers: Godot zip cache, addons cache
• Dependency resolution: flat graph, domain classes handle graphs
Detail without overcomplicating
• Core modules and their responsibilities
• How commands flow through layers to external systems
• Avoid splitting into absurd microservices—this is a single CLI binary