configuration files ├── pipelines/ # Automation and workflow repositories └── vaults/ # Secure storage and tribal knowledge ``` The P.P.V system helps maintain separation of concerns while providing a consistent structure across all projects and environments. It reflects systems thinking and the interconnectedness of different components in your workflow. Key aspects: - **Interconnected references**: Tools in `tools.md` can link to tribal knowledge in Vaults using URI schemes - **Company separation**: Each company gets its own folder under pillars for clear separation - **Principles first**: Core principles document guides all other decisions ## Repository Design Patterns This repository follows specific organizational patterns to maintain consistency and clarity: ### Platform-Based Organization (Top Level) At the root level, configurations are organized by platform or environment: - `arch-linux/` - Configurations specific to Arch Linux systems - `raspberry-pi/` - Configurations for Raspberry Pi devices - `nvim/` - Neovim-specific configurations - etc. This structural organization makes it clear which files apply to which environments. ### Hybrid Organization (Within Platforms) Within each platform directory, we use a hybrid approach combining categories and specific use cases: ``` raspberry-pi/ ├── home/ # Home use cases │ ├── home-assistant/ # Smart home hub │ └── media-server/ # Media streaming ├── development/ # Development use cases │ └── ci-runner/ # Self-hosted CI/CD └── networking/ # Networking use cases └── network-monitor/ # Traffic analysis ``` This approach: - Organizes by general categories for maintainability - Provides concrete examples for clarity - Allows users to find configurations based on their intended use case ### Feature-Based Implementation The actual implementation of features follows these principles: 1. **Detection over Assumption**: Scripts detect hardware capabilities rather than assuming specific use cases 2. **Composability**: Features can be mixed and matched based on user needs 3. **Automatic Optimization**: Hardware-specific optimizations are applied automatically 4. **Clear Documentation**: Each feature documents its purpose and requirements This multi-level organizational approach allows us to maintain a clean repository structure while providing flexibility for different use cases. ## Quick Setup ### Set Up Your Dotfiles Get started with your personalized environment: ```bash # Clone the repository and run setup git clone https://github.com/atxtechbro/dotfiles.git ~/ppv/pillars/dotfiles cd ~/ppv/pillars/dotfiles ./setup.sh ``` The setup script will: - Create all necessary symlinks - Set up your secrets file from the template - Apply configurations immediately The script will NOT install packages for you or make assumptions about your package manager. > **Note:** The setup script requires `git` and `curl`. Most systems have these installed by default, but if you encounter errors, see the package installation section below. ### Recommended Packages These packages enhance your development experience but are not required for the dotfiles setup:

Ubuntu/Debian

```bash sudo apt update sudo apt install -y git gh jq tmux curl wget ```

Arch Linux

```bash sudo pacman -Syu sudo pacman -S --needed git github-cli jq tmux curl wget ```

macOS

```bash # Install Homebrew if not already installed /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" # Install essential packages brew install git gh jq tmux curl wget ```

## Applications ### Google Chrome Install Google Chrome with automatic updates via the official Google repository: ```bash # Add Google Chrome repository key wget -q -O - https://dl.google.com/linux/linux_signing_key.pub

#dotfiles

AI Configuration Setup

Dotfiles