$!BASHparaphernalia

💊 Table of Contents

• 🥗 Overview
• 🍺 Scripts Included
  • 🐧 $!NEWbara.sh
  • 🗻 $!MTrclone.sh
  • 🌈 $!LOGme.sh
  • 🤖 $!DONtype.sh
  • 🐮 $!COWcase.sh
• 🚀 Getting Started
• 🌛 Notes
• 🛸 License
• 🪐 Recruiter's Note
• 👽 Contact

🥗 Overview

This repository is a collection of Bash scripts I use to automate and streamline my Linux workflow. Each script is self‑contained, documented, and easy to adapt. Think of it as both a personal toolkit and a demonstration of my ability to write practical, maintainable automation.

🍺 Scripts Included

🐧 $!NEWbara.sh

• Purpose: Comprehensive system bootstrapper for Nobara/Fedora with configuration-driven package management and visual feedback.
• Summary: A powerful script that installs packages via DNF (system packages) and Flatpak (user/system apps). Requires at least one package configuration file, supports dry-run mode for safe testing, automatic logging, and smart cleanup of orphaned packages.
• Key Features:
  • Configuration-driven installation (mandatory package files for explicit intent)
  • Multi-package manager support (DNF + Flatpak)
  • External package list files (config/dnf-packages.txt, config/flatpak-packages.txt)
  • Automatic cowsay/lolcat installation for visual feedback
  • Dry-run mode to preview installations without changes (cleanup skipped)
  • Automatic timestamped logging for troubleshooting
  • User/system Flatpak installation modes
  • Smart cleanup of orphaned packages and runtimes
• Dependencies: dnf, flatpak, sudo (cowsay/lolcat auto-installed).
• Configuration: See scripts/NEWbara/config/README.md for custom package list documentation.
• Use Case: Complete system setup automation with explicit configuration control, perfect for fresh Nobara/Fedora installations or team standardization.

---

🗻 $!MTrclone.sh

• Purpose: Mounts multiple cloud storage accounts locally.
• Summary: Creates directories for OneDrive, Google Drive, and Dropbox, mounts them via rclone, verifies with findmnt, and reports success/failure with xcowsay.
• Dependencies: rclone, xcowsay.
• Use Case: Automates cloud drive access at login with playful feedback.

---

🌲 $!LOGme.sh

• Purpose: Enhances login experience with split-pane terminal display, RGB setup, and system visualization.
• Summary: A sophisticated login script using wezterm split-panes to display OpenRGB setup, cbonsai animation, fortune messages with syntax highlighting, and additional startup task logging.
• Key Features:
  • Wezterm split-pane orchestration for concurrent visual feedback
  • Automatic OpenRGB profile loading for consistent RGB lighting
  • Interactive fortune display with cowsay and bat syntax highlighting
  • System visualization with cbonsai bonsai tree animation
  • Task logging via MTrclone.sh integration
  • Smart autostart detection and setup with user prompts
  • Dependency validation with helpful installation instructions
  • Cross-desktop autostart support (KDE Plasma and GNOME)
  • Graceful error handling that continues execution despite failures
• Dependencies: wezterm, openrgb, fortune, cowsay, bat, cbonsai.
• Use Case: Provides a visually engaging, automated login experience with parallel feedback, RGB consistency, and startup task visibility.

---

🤖 $!DONtype.sh

• Purpose: Automates in-game keybinding setup for Schedule I with enhanced reliability.
• Summary: Uses xdotool to automatically type and bind teleport locations, inventory management, and utility commands to function keys (F1-F12). Includes dependency validation, progress feedback, and robust error handling for reliable execution.
• Key Features:
  • Automated keybinding for teleport locations (motel room, sweatshop, storage unit, etc.)
  • Inventory management commands (clear trash, clear inventory)
  • Balance manipulation commands (change balance)
  • Dependency validation with helpful error messages
  • Real-time progress feedback with countdown timer
  • Error handling and recovery (continues on individual binding failures)
  • Robust execution with cleanup traps and modular code structure
  • Optimized timing for faster setup completion
  • Non-interactive execution for gaming efficiency
• Dependencies: xdotool.
• Use Case: Eliminates manual command typing during gameplay, completing setup in ~20 seconds instead of several minutes of manual input with built-in error recovery and user feedback.

---

🐮 $!COWcase.sh

• Purpose: Batch rename directories and files by converting first character to lowercase.
• Summary: A robust utility script that standardizes file and directory naming by converting the first character to lowercase, featuring flexible filtering options, error handling, and optional visual feedback.
• Key Features:
  • Case conversion modes (lowercase default, uppercase with -u option)
  • Selective processing (directories only with -d, files only with -f)
  • Custom path targeting with -p option (defaults to current directory)
  • Safe renaming (only processes items when new name differs from original)
  • Visual feedback using cowsay/lolcat when available (falls back gracefully)
  • Comprehensive error handling with detailed error messages and logging
  • Verbose output showing all rename operations
  • Non-destructive operations preserving file metadata
• Dependencies: None required (uses built-in Bash tools); optional cowsay and lolcat for enhanced visual feedback.
• Use Case: Quickly standardize naming conventions across file collections, perfect for organizing media libraries, codebases, or any directory structure with inconsistent capitalization.

🚀 Blasting Off

Prerequisites

• Operating System: Linux distribution (tested on Nobara/Fedora)
• Shell: Bash (most Linux distributions include this by default)
• Permissions: Ability to run sudo for system-level operations

Installation

1. Clone the repository:

   git clone https://github.com/TheOnliestMattastic/BASHparaphernalia.git
   cd BASHparaphernalia

2. Make scripts executable:

   # For all scripts at once
   chmod +x scripts/*/*.sh
   
   # Or for individual scripts
   chmod +x scripts/NEWbara/NEWbara.sh
   chmod +x scripts/MTrclone/MTrclone.sh
   # ... etc

3. Run any script:

   ./scripts/scriptName/scriptName.sh [options]

Script-Specific Setup

Each script includes detailed setup instructions in its README and header comments. Here are the key requirements:

• $!NEWbara.sh: Requires dnf, flatpak, sudo access, and one or more package configuration files (-d or -f); auto-installs cowsay and lolcat
• $!MTrclone.sh: Requires rclone configured with cloud remotes
• $!LOGme.sh: Requires wezterm, openrgb, fortune, cowsay, bat, cbonsai
• $!DONtype.sh: Requires xdotool for automation
• $!COWcase.sh: No external dependencies (uses built-in tools); optional cowsay and lolcat for visual feedback

Configuration

Most scripts support customization through:

• Command-line options (see --help for each script)
• Configuration files (NEWbara.sh requires external package list files in config/)
• Environment variables
• Direct script editing for personal preferences

NEWbara.sh Configuration:

• Create or edit config/dnf-packages.txt for DNF packages (one per line)
• Create or edit config/flatpak-packages.txt for Flatpak apps (one ID per line)
• Run with at least one file: ./NEWbara.sh -d config/dnf-packages.txt or -f config/flatpak-packages.txt
• See scripts/NEWbara/config/README.md for detailed documentation

🌛 Notes

Compatibility & Customization

• Personal Setup: These scripts were written for my personal Nobara workflow, so you may need to adjust paths, package lists, or configurations for your environment.
• Linux Focus: Designed primarily for Linux systems with systemd, DNF, and common package managers. May require adaptation for other distributions.
• Version Dependencies: Some scripts depend on specific tool versions (e.g., rclone remotes, OpenRGB profiles).

Script Architecture

• Self-Contained: Each script is designed to be standalone with minimal external dependencies.
• Well-Documented: All scripts follow WHAT/WHY/HOW/NOTE comment patterns with professional section headers.
• Error Handling: Scripts include comprehensive error checking and user feedback mechanisms.
• Logging: Most scripts create timestamped log files for troubleshooting and auditability.
• Conditional Execution: Scripts gracefully handle missing tools and skip components as needed.
• Non-Destructive: Scripts avoid overwriting existing configurations without confirmation.

Security Considerations

• Sudo Usage: Some scripts require sudo access - review what they're doing before running.
• Network Operations: Scripts like NEWbara.sh download packages from repositories.
• File Permissions: Scripts may create directories and modify file permissions.

Contributing

• Welcome Contributions: Issues, feature requests, and pull requests are encouraged.
• Fork Friendly: Feel free to fork and adapt for your own needs.
• Documentation: All scripts include comprehensive header documentation.

Future Development

• Modular Design: Scripts are built to be easily extended or modified.
• Configuration Files: Moving toward external configuration files for easier customization.
• Cross-Platform: Potential for adaptation to other Unix-like systems.

🛸 License

This project is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. This means you are free to use, modify, and distribute these scripts as long as you provide attribution and apply the same license to your derivative works.

🪐 Recruiter’s Note

This repository serves as a comprehensive portfolio piece demonstrating practical software development and system administration skills. While not a commercial product, it showcases:

Technical Skills Demonstrated

• Bash Scripting Expertise: Advanced shell scripting with error handling, logging, user interaction, and configuration management
• Linux System Administration: Package management (DNF, Flatpak), service configuration, terminal orchestration, and system automation
• Cross-Tool Integration: Coordinating multiple utilities (rclone, OpenRGB, wezterm, xdotool) into cohesive workflows
• Documentation Practices: Professional WHAT/WHY/HOW/NOTE comment patterns, comprehensive READMEs, and user-friendly interfaces
• Configuration Design: External configuration files for flexibility and reusability, supporting both individual and team use cases
• Problem-Solving Approach: Identifying repetitive tasks and creating automated, maintainable solutions

Professional Qualities

• Self-Directed Learning: Researching and implementing tools like rclone, OpenRGB, and various package managers
• Attention to Detail: Comprehensive error handling, user feedback, and safety checks
• User Experience Focus: Creating scripts that are both powerful and easy to use
• Maintainability: Clean, commented code that can be easily modified and extended
• Adaptability: Scripts designed to work across different configurations and use cases

Development Process

• Iterative Improvement: Scripts evolved from simple solutions to robust, feature-rich tools
• Testing & Debugging: Real-world testing leading to improved error handling
• User-Centered Design: Scripts include help systems, validation, and clear success/failure indicators
• Version Control: Proper Git usage with meaningful commit messages and repository organization

This toolkit reflects the same methodical, user-focused approach I bring to IT support, system administration, and software development roles.

👽 Contact

Curious about my projects? Want to collaborate or hire for entry-level IT/support/dev roles? Shoot me an email or connect on GitHub—I reply quickly and love new challenges.

“Sometimes the questions are complicated and the answers are simple.” — Dr. Seuss