How jygastaud/ubuntu-installer works
Main Components Organization
a) Automation Controller Layer
• Ansible as the central orchestrator
• Run.sh script as the entry point
• To the configuration management (config.yml, ansible.cfg)
b) Role Categories (organize in distinct groups):
• System Roles
• Dev Tools Roles
• Editors Roles
• Others Roles
• Custom Roles
Component Relationships
• Entry point (run.sh) → Ansible Playbook
• Playbook → Role Categories
• Roles → Package Managers (apt, snap)
• Roles → External Sources (repositories, direct downloads)
Specific Implementation Details
• Hexagons for package managers
• Circles for external sources
Detailed Component Breakdown
Create nested groups showing:
a) Dev Tools Section:
• Cloud Tools (Azure, AWS, GCP)
• Container Tools (Docker, Kubernetes)
• Database Tools
• Version Control
• Development Environments
b) System Tools Section:
• Shell Configuration (Zsh)
• System Utilities
• Network Tools
c) Application Section:
• Editors
• Browsers
• Productivity Tools
Flow Representation
Installation flow:
User Input → run.sh → Ansible Playbook → Role Selection → Package Installation → Configuration
Specific elements
a) Configuration Management:
• Config.yml as the central configuration source
• Default.config.yml as the template
• Relationship with ansible.cfg
b) Role Structure (for each role):
• tasks/
• defaults/
• vars/
• handlers/
• meta/
Technical Details
• Tag system for selective installation
• User configuration options
• System requirements
• Version compatibility
• Blue: Core components (Ansible, playbook)
• Green: Successfully tested/stable components
• Yellow: Optional components
• Gray: External dependencies
• Red: Critical paths/requirements
• All symbols used
• Component types
Keep the abstraction level focused on the architectural components while showing the relationship between:
• Configuration management
• Role organization
• Package management
• System integration points
This will create a clear visualization of how the Ubuntu installer automates the setup process while maintaining flexibility through its role-based structure and configuration options.
Remember to indicate the flow of both control and data, showing how user configurations propagate through the system and how different roles interact with the system's package managers and external sources.