How pranavbhattarai/linux101 works
Main Components
• Repository Root: Think of this as the central “control hub” that organizes various scripts and configurations.
• Script & Automation Components: These include Python scripts (e.g., “Patch GNS3VM for Cisco Routers.py”, “Remove Background Image.py”) and numerous bash scripting directories (such as “bash_scripting”, “console script to download pdf”, etc.).
• Configuration/Customization Modules: Directories like “configure shell & terminal”, “custom perferences for GNOME”, “boot”, and distro-specific folders like “fedora-34-begans” and “ubuntu-18.04-begans” indicate targeted customizations for particular Linux distributions.
• DevOps/Networking & System Administration: Folders such as “DevOps”, “networking”, “security”, “sysAdmin-Linux”, “sysAdmin-Windows”, and “tracking-bugs” cover broader system management and troubleshooting aspects.
• External Tools Integration: Files like “Patch GNS3VM for Cisco Routers.py” hint at integration with virtual network setups, demonstrating the project’s use in handling external network systems.
Relationships and Interactions
• At the center, the repository aggregates all the scripts and configuration modules.
• The automation scripts are designed to be executed (manually or via scheduling) to apply certain changes or customizations; thus, they “read from” the configuration directories and “apply” modifications on the system.
• Some components (like DevOps and sysAdmin directories) interact with external systems or environments (e.g., bug tracking tools, network devices in GNS3).
Architectural Patterns and Design Principles
• Modular Organization: The file tree indicates a highly modular, loosely coupled design where each directory groups scripts relevant to a particular domain or task. This is akin to a micro-module approach, making maintenance and upgrades easier.
• Separation of Concerns: There’s a clear separation between operating system customizations (GNOME, shell configurations) and more operational tasks (DevOps, networking, security).
• Reusability & Backup Philosophy: The README reinforces that this is a backup repository and a personal record of “commands that make things work.” Thus, the design embraces reusability and version tracking of custom configurations.
Relevant Technologies, Frameworks, and Libraries
• OS Focus: Primarily on Linux with Fedora and Ubuntu customizations.
• Scripting Languages: Both Python and shell scripting are predominantly used.
• Networking & Virtualization: Elements such as GNS3 indicate familiarity with network emulation.
• Community Integrations: Although not a software component per se, the README’s links to Askubuntu, FedoraProject, etc., can be noted as external sources that influence development and troubleshooting.
• Branch from the central node into clusters:
• A “Customization Cluster” (with sub-nodes for GNOME, shell settings, boot, etc.)
• A “Scripting & Automation Cluster” (include all Python and Bash scripts here, linking them to their relevant configuration sources)
• A “DevOps & Admin Cluster” (link folders related to networking, security, sysAdmin on Linux/Windows, and bug tracking)
• Optionally, an “External Integrations” node (for GNS3 VM patching and any community influences)