Khamel83

#!/bin/bash
# BULLETPROOF HYPERDUCK PARALLEL SETUP
# Sends URLs to BOTH Downie AND Atlas simultaneously
# October 2025 Configuration

echo "🔫 BULLETPROOF HYPERDUCK → DOWNIE + ATLAS SETUP"
echo "=============================================="

# Create the parallel processing script
cat > ~/hyperduck-parallel-handler.sh << 'EOF'

Khamel83

#!/bin/bash
# AppleScript-based Downie → Atlas Bridge
# Uses AppleScript to try Downie first, then Atlas

cat > ~/downie_atlas_applescript.scpt << 'EOF'
on run argv
    set targetURL to item 1 of argv
    set atlasServer to "https://atlas.khamel.com"

    tell application "System Events"

Khamel83

#!/bin/bash
# Downie History Database Bridge
# Monitors Downie's actual database for failed URLs
# Based on real monitoring data showing History.db usage

ATLAS_SERVER="https://atlas.khamel.com"
HISTORY_DB="/Users/macmini/Library/Containers/com.charliemonroe.Downie-4/Data/Library/Application Support/com.charliemonroe.Downie-4/History.db"
SENT_URLS_FILE="$HOME/.atlas_sent_urls.txt"
LAST_CHECK_FILE="$HOME/.atlas_last_check.txt"

Khamel83

#!/bin/bash
# Real-time Downie Activity Monitor
# Run this BEFORE triggering a Downie failure

echo "🔍 REAL-TIME DOWNIE MONITORING"
echo "=============================="

# Create timestamp for new file detection
touch /tmp/before_downie_test

Khamel83

#!/bin/bash
# Check Downie Container Logs - Based on diagnostic results

echo "🔍 CHECKING DOWNIE CONTAINERS"
echo "============================="

# From the diagnostic, we found these Downie containers:
CONTAINERS=(
    "$HOME/Library/Containers/com.charliemonroe.Downie-4"
    "$HOME/Library/Containers/com.charliemonroe.Downie-4-Downie-Extension"

Khamel83

#!/bin/bash
# Downie Diagnostic Script
# Run this on Mac Mini to find all Downie-related files and logs

echo "🔍 DOWNIE DIAGNOSTIC SCRIPT"
echo "=========================="

# Find all Downie-related directories
echo "📁 Searching for Downie directories..."
find ~ -name "*downie*" -type d 2>/dev/null | head -10

Khamel83

#!/bin/bash
# MAC MINI BRIDGE V2 - Enhanced Downie failure detection
# More comprehensive patterns for detecting Downie failures

ATLAS_SERVER="https://atlas.khamel.com"
LOG_FILE="$HOME/Library/Logs/Downie.log"
SENT_URLS_FILE="$HOME/.atlas_sent_urls.txt"
DEBUG_LOG="$HOME/bridge_debug.log"

# Create tracking files

Khamel83

#!/bin/bash
# MAC MINI BRIDGE SETUP - Simple version
# Run this on your Mac Mini to connect to Atlas

echo "🔧 Setting up Hyperduck → Downie → Atlas pipeline..."

# Atlas server domain
ATLAS_SERVER="https://atlas.khamel.com"

# Test connection

Khamel83

#!/bin/bash
# MAC MINI BRIDGE SETUP - Updated for IP-based connection
# Run this on your Mac Mini to connect to Atlas via IP

echo "🔧 Setting up Hyperduck → Downie → Atlas pipeline..."
echo ""

# Get Atlas server IP (replace with your actual server IP)
ATLAS_SERVER="http://54.210.133.145:35555"  # Update this IP if needed

Khamel83

#!/bin/bash
# HYPERDUCK → DOWNIE → ATLAS COMPLETE SETUP
# Run this on your Mac Mini to connect everything
# Usage: bash HYPERDUCK_DOWNIE_ATLAS_SETUP.sh

echo "🔧 Setting up Hyperduck → Downie → Atlas pipeline..."
echo "📍 Atlas Server: atlas.khamel.com:35555"

# Step 1: Create Downie failure monitor
cat > ~/downie-atlas-bridge.sh << 'EOF'