Tutorial

Nuevas actualizaciones y mejoras para Macfleet.

Aviso importante

Los ejemplos de código y scripts proporcionados en estos tutoriales son solo para propósitos educativos. Macfleet no es responsable de ningún problema, daño o vulnerabilidad de seguridad que pueda surgir del uso, modificación o implementación de estos ejemplos. Siempre revisa y prueba el código en un entorno seguro antes de usarlo en sistemas de producción.

Managing Spotlight Indexing on macOS Devices

Spotlight is macOS's powerful system-wide search feature that helps users quickly locate files, documents, applications, emails, and more across their system. While Spotlight provides excellent search capabilities, its continuous background indexing can sometimes impact system performance, particularly on older hardware or resource-constrained environments. This comprehensive guide provides methods to manage Spotlight indexing effectively.

Understanding Spotlight and Its Impact

Spotlight uses a sophisticated indexing system that continuously scans and catalogs content on your Mac to provide instant search results. This indexing process involves:

  • File content analysis: Reading and indexing text within documents
  • Metadata extraction: Cataloging file properties, creation dates, and tags
  • Application indexing: Tracking installed applications and their data
  • Email and message indexing: Indexing Mail, Messages, and other communication apps
  • Real-time updates: Monitoring file system changes to keep the index current

Why Manage Spotlight Indexing?

There are several scenarios where managing Spotlight indexing becomes necessary:

  • Performance optimization: Reducing CPU and disk usage on resource-limited systems
  • Privacy concerns: Preventing indexing of sensitive files and directories
  • Storage management: Saving disk space used by index files
  • Troubleshooting: Resolving search issues or corrupted indexes
  • Enterprise deployment: Standardizing search behavior across managed devices
  • Development environments: Preventing indexing of build directories and temporary files

Prerequisites

Before managing Spotlight indexing, ensure you have:

  • Administrative privileges on the Mac
  • Terminal or SSH access
  • Understanding of the impact on search functionality
  • Backup of important data (recommended)

Basic Spotlight Management Commands

Understanding mdutil

The mdutil command is the primary tool for managing Spotlight indexing:

# Check indexing status
mdutil -s /

# Enable indexing for a volume
mdutil -i on /

# Disable indexing for a volume
mdutil -i off /

# Erase and rebuild index
mdutil -E /

# Get help
mdutil -h

Checking Current Indexing Status

Before making changes, check the current indexing status:

#!/bin/bash

# Check Spotlight indexing status for all volumes
echo "Spotlight Indexing Status Report"
echo "==============================="
echo "Date: $(date)"
echo ""

# Get all mounted volumes
volumes=$(df -h | grep "^/dev" | awk '{print $9}')

echo "Volume Indexing Status:"
echo "----------------------"

for volume in $volumes; do
    if [ -d "$volume" ]; then
        status=$(mdutil -s "$volume" 2>/dev/null | grep "Indexing enabled")
        echo "$volume: $status"
    fi
done

echo ""
echo "Active indexing processes:"
ps aux | grep -i mds | grep -v grep

Disabling Spotlight Indexing

Basic Disable Script

Simple script to disable Spotlight indexing on the main volume:

#!/bin/bash

# Disable Spotlight indexing on the root volume
echo "Disabling Spotlight indexing..."

if sudo mdutil -i off /; then
    echo "✓ Spotlight indexing disabled successfully"
    
    # Verify the change
    status=$(mdutil -s / | grep "Indexing enabled")
    echo "Current status: $status"
else
    echo "✗ Failed to disable Spotlight indexing"
    exit 1
fi

echo "Note: Search functionality will be limited until indexing is re-enabled"

Advanced Disable Script with Logging

More comprehensive script with logging and verification:

#!/bin/bash

# Advanced Spotlight disable script with logging
LOG_FILE="/var/log/spotlight_management.log"
TIMESTAMP=$(date '+%Y-%m-%d %H:%M:%S')

# Function to log messages
log_message() {
    echo "[$TIMESTAMP] $1" | tee -a "$LOG_FILE"
}

# Function to disable indexing for a volume
disable_indexing() {
    local volume=$1
    
    log_message "Attempting to disable indexing for volume: $volume"
    
    # Check if volume exists
    if [ ! -d "$volume" ]; then
        log_message "ERROR: Volume $volume does not exist"
        return 1
    fi
    
    # Check current status
    current_status=$(mdutil -s "$volume" 2>/dev/null)
    log_message "Current status for $volume: $current_status"
    
    # Disable indexing
    if sudo mdutil -i off "$volume"; then
        log_message "SUCCESS: Indexing disabled for $volume"
        
        # Verify the change
        new_status=$(mdutil -s "$volume" 2>/dev/null)
        log_message "New status for $volume: $new_status"
        
        return 0
    else
        log_message "ERROR: Failed to disable indexing for $volume"
        return 1
    fi
}

# Main execution
log_message "Starting Spotlight indexing disable process"

# Disable for root volume
if disable_indexing "/"; then
    log_message "Root volume indexing disabled successfully"
else
    log_message "Failed to disable root volume indexing"
    exit 1
fi

# Optional: Disable for other volumes
# Uncomment the following lines to disable for additional volumes
# disable_indexing "/Volumes/ExternalDrive"
# disable_indexing "/Users"

log_message "Spotlight indexing disable process completed"
echo "Process completed. Check log at: $LOG_FILE"

Batch Disable for Multiple Volumes

Script to disable indexing on multiple volumes:

#!/bin/bash

# Batch disable Spotlight indexing for multiple volumes
VOLUMES=(
    "/"
    "/Users"
    "/Applications"
    # Add more volumes as needed
)

echo "Batch Spotlight Indexing Disable"
echo "================================"
echo "Date: $(date)"
echo ""

successful=0
failed=0

for volume in "${VOLUMES[@]}"; do
    echo "Processing volume: $volume"
    
    if [ -d "$volume" ]; then
        if sudo mdutil -i off "$volume" 2>/dev/null; then
            echo "  ✓ Successfully disabled indexing for $volume"
            ((successful++))
        else
            echo "  ✗ Failed to disable indexing for $volume"
            ((failed++))
        fi
    else
        echo "  ⚠ Volume $volume does not exist, skipping"
    fi
done

echo ""
echo "Summary:"
echo "--------"
echo "Successfully disabled: $successful volumes"
echo "Failed: $failed volumes"

if [ $failed -gt 0 ]; then
    echo "Some operations failed. Check individual volume status manually."
    exit 1
fi

Removing Spotlight Index Files

Basic Cleanup Script

After disabling indexing, remove existing index files to free up space:

#!/bin/bash

# Remove Spotlight index files
echo "Removing Spotlight index files..."

# Remove .Spotlight-V100 directories (modern macOS)
if sudo rm -rf /.Spotlight-V100; then
    echo "✓ Removed .Spotlight-V100 directory"
else
    echo "⚠ No .Spotlight-V100 directory found or removal failed"
fi

# Remove legacy .Spotlight directories
if sudo rm -rf /.Spotlight*; then
    echo "✓ Removed legacy Spotlight directories"
else
    echo "⚠ No legacy Spotlight directories found"
fi

# Calculate space freed
echo "Spotlight index cleanup completed"

Advanced Cleanup with Size Calculation

More detailed cleanup script that shows space savings:

#!/bin/bash

# Advanced Spotlight index cleanup with size reporting
echo "Spotlight Index Cleanup Utility"
echo "==============================="
echo "Date: $(date)"
echo ""

# Function to get directory size
get_size() {
    local dir=$1
    if [ -d "$dir" ]; then
        du -sh "$dir" 2>/dev/null | cut -f1
    else
        echo "0B"
    fi
}

# Function to remove spotlight directories
cleanup_spotlight_dirs() {
    local base_path=$1
    local total_size=0
    
    echo "Cleaning up Spotlight directories in: $base_path"
    
    # Find all Spotlight directories
    spotlight_dirs=$(find "$base_path" -name ".Spotlight*" -type d 2>/dev/null)
    
    if [ -z "$spotlight_dirs" ]; then
        echo "  No Spotlight directories found"
        return 0
    fi
    
    for dir in $spotlight_dirs; do
        size=$(get_size "$dir")
        echo "  Found: $dir ($size)"
        
        if sudo rm -rf "$dir"; then
            echo "    ✓ Removed successfully"
        else
            echo "    ✗ Failed to remove"
        fi
    done
}

# Clean up common locations
cleanup_spotlight_dirs "/"
cleanup_spotlight_dirs "/Users"

# Clean up on external volumes if any
for volume in /Volumes/*; do
    if [ -d "$volume" ]; then
        echo ""
        cleanup_spotlight_dirs "$volume"
    fi
done

echo ""
echo "Spotlight index cleanup completed"
echo "Run 'df -h' to see updated disk usage"

Enabling Spotlight Indexing

Basic Enable Script

Simple script to re-enable Spotlight indexing:

#!/bin/bash

# Enable Spotlight indexing on the root volume
echo "Enabling Spotlight indexing..."

if sudo mdutil -i on /; then
    echo "✓ Spotlight indexing enabled successfully"
    
    # Verify the change
    status=$(mdutil -s / | grep "Indexing enabled")
    echo "Current status: $status"
    
    echo ""
    echo "Note: Indexing will begin automatically and may take some time to complete"
    echo "You can monitor progress using Spotlight search"
else
    echo "✗ Failed to enable Spotlight indexing"
    exit 1
fi

Advanced Enable with Progress Monitoring

Script that enables indexing and provides progress monitoring:

#!/bin/bash

# Advanced Spotlight enable script with progress monitoring
LOG_FILE="/var/log/spotlight_management.log"
TIMESTAMP=$(date '+%Y-%m-%d %H:%M:%S')

# Function to log messages
log_message() {
    echo "[$TIMESTAMP] $1" | tee -a "$LOG_FILE"
}

# Function to monitor indexing progress
monitor_indexing() {
    local volume=$1
    local timeout=60  # Monitor for 60 seconds
    local elapsed=0
    
    echo "Monitoring indexing progress for $volume..."
    
    while [ $elapsed -lt $timeout ]; do
        # Check if indexing is in progress
        if ps aux | grep -v grep | grep -q "mds_stores\|mdworker"; then
            echo "  Indexing in progress... (${elapsed}s elapsed)"
        else
            echo "  Indexing may have completed or paused"
            break
        fi
        
        sleep 5
        elapsed=$((elapsed + 5))
    done
    
    if [ $elapsed -ge $timeout ]; then
        echo "  Monitoring timeout reached. Indexing may still be in progress."
    fi
}

# Function to enable indexing for a volume
enable_indexing() {
    local volume=$1
    
    log_message "Attempting to enable indexing for volume: $volume"
    
    # Check if volume exists
    if [ ! -d "$volume" ]; then
        log_message "ERROR: Volume $volume does not exist"
        return 1
    fi
    
    # Check current status
    current_status=$(mdutil -s "$volume" 2>/dev/null)
    log_message "Current status for $volume: $current_status"
    
    # Enable indexing
    if sudo mdutil -i on "$volume"; then
        log_message "SUCCESS: Indexing enabled for $volume"
        
        # Verify the change
        new_status=$(mdutil -s "$volume" 2>/dev/null)
        log_message "New status for $volume: $new_status"
        
        # Monitor initial progress
        monitor_indexing "$volume"
        
        return 0
    else
        log_message "ERROR: Failed to enable indexing for $volume"
        return 1
    fi
}

# Main execution
log_message "Starting Spotlight indexing enable process"

# Enable for root volume
if enable_indexing "/"; then
    log_message "Root volume indexing enabled successfully"
else
    log_message "Failed to enable root volume indexing"
    exit 1
fi

log_message "Spotlight indexing enable process completed"
echo "Process completed. Check log at: $LOG_FILE"

Rebuilding Spotlight Index

Basic Rebuild Script

Script to completely rebuild the Spotlight index:

#!/bin/bash

# Rebuild Spotlight index
echo "Rebuilding Spotlight index..."
echo "Warning: This will erase the current index and rebuild from scratch"
echo ""

read -p "Continue? (y/N): " confirm
if [[ ! $confirm =~ ^[Yy]$ ]]; then
    echo "Operation cancelled"
    exit 0
fi

echo "Starting index rebuild..."

if sudo mdutil -E /; then
    echo "✓ Index rebuild initiated successfully"
    
    # Show status
    status=$(mdutil -s /)
    echo "Current status: $status"
    
    echo ""
    echo "The index rebuild process has started and will continue in the background"
    echo "This may take several hours depending on the amount of data"
    echo "You can monitor progress using Activity Monitor (look for mds_stores and mdworker processes)"
else
    echo "✗ Failed to initiate index rebuild"
    exit 1
fi

Advanced Rebuild with Selective Volumes

Script to rebuild indexes for specific volumes:

#!/bin/bash

# Advanced Spotlight index rebuild script
VOLUMES=(
    "/"
    "/Users"
    # Add specific volumes or use discovery
)

AUTO_DISCOVER=${1:-false}

echo "Spotlight Index Rebuild Utility"
echo "==============================="
echo "Date: $(date)"
echo ""

# Function to discover mounted volumes
discover_volumes() {
    echo "Discovering mounted volumes..."
    
    # Get all mounted HFS+/APFS volumes
    local discovered_volumes=()
    while IFS= read -r line; do
        volume=$(echo "$line" | awk '{print $9}')
        if [ -d "$volume" ] && [ "$volume" != "/dev" ]; then
            discovered_volumes+=("$volume")
        fi
    done < <(df -h | grep "^/dev")
    
    echo "Discovered volumes:"
    for vol in "${discovered_volumes[@]}"; do
        echo "  - $vol"
    done
    
    VOLUMES=("${discovered_volumes[@]}")
}

# Function to rebuild index for a volume
rebuild_index() {
    local volume=$1
    
    echo "Rebuilding index for: $volume"
    
    # Check if volume exists and is mounted
    if [ ! -d "$volume" ]; then
        echo "  ✗ Volume $volume does not exist or is not mounted"
        return 1
    fi
    
    # Show current status
    current_status=$(mdutil -s "$volume" 2>/dev/null)
    echo "  Current status: $current_status"
    
    # Rebuild index
    if sudo mdutil -E "$volume"; then
        echo "  ✓ Index rebuild initiated for $volume"
        
        # Show new status
        new_status=$(mdutil -s "$volume" 2>/dev/null)
        echo "  New status: $new_status"
        
        return 0
    else
        echo "  ✗ Failed to rebuild index for $volume"
        return 1
    fi
}

# Auto-discover volumes if requested
if [ "$AUTO_DISCOVER" = "true" ]; then
    discover_volumes
fi

echo "Volumes to rebuild:"
for volume in "${VOLUMES[@]}"; do
    echo "  - $volume"
done

echo ""
read -p "Proceed with rebuilding indexes? (y/N): " confirm
if [[ ! $confirm =~ ^[Yy]$ ]]; then
    echo "Operation cancelled"
    exit 0
fi

echo ""
echo "Starting index rebuild process..."
echo ""

successful=0
failed=0

for volume in "${VOLUMES[@]}"; do
    if rebuild_index "$volume"; then
        ((successful++))
    else
        ((failed++))
    fi
    echo ""
done

echo "Rebuild Summary:"
echo "---------------"
echo "Successfully initiated: $successful volumes"
echo "Failed: $failed volumes"
echo ""
echo "Note: Index rebuilding will continue in the background"
echo "Monitor progress with: ps aux | grep mds"

Advanced Spotlight Management

Selective Directory Exclusion

Script to exclude specific directories from indexing:

#!/bin/bash

# Exclude specific directories from Spotlight indexing
EXCLUDE_DIRS=(
    "/tmp"
    "/var/tmp"
    "/private/tmp"
    "/Users/Shared/Build"
    # Add more directories as needed
)

echo "Spotlight Directory Exclusion Manager"
echo "===================================="
echo ""

# Function to add directory to exclusion list
exclude_directory() {
    local dir_path=$1
    
    echo "Excluding directory: $dir_path"
    
    # Check if directory exists
    if [ ! -d "$dir_path" ]; then
        echo "  ⚠ Directory does not exist: $dir_path"
        return 1
    fi
    
    # Add to Spotlight privacy list using defaults
    if sudo defaults write /System/Library/CoreServices/Search.bundle/Contents/Resources/SpotlightExclusions.plist Exclusions -array-add "$dir_path"; then
        echo "  ✓ Added to exclusion list"
        return 0
    else
        echo "  ✗ Failed to add to exclusion list"
        return 1
    fi
}

# Function to show current exclusions
show_exclusions() {
    echo "Current Spotlight exclusions:"
    echo "----------------------------"
    
    # Read from system preferences
    if defaults read /System/Library/CoreServices/Search.bundle/Contents/Resources/SpotlightExclusions.plist Exclusions 2>/dev/null; then
        echo ""
    else
        echo "No exclusions found or unable to read exclusions list"
    fi
}

# Show current exclusions
show_exclusions

echo ""
echo "Adding new exclusions..."

for dir in "${EXCLUDE_DIRS[@]}"; do
    exclude_directory "$dir"
done

echo ""
echo "Exclusion process completed"
echo "Restart Spotlight for changes to take effect:"
echo "sudo killall mds && sudo mdutil -E /"

Performance Monitoring Script

Script to monitor Spotlight's impact on system performance:

#!/bin/bash

# Spotlight Performance Monitor
DURATION=${1:-60}  # Monitor for 60 seconds by default
INTERVAL=5

echo "Spotlight Performance Monitor"
echo "============================"
echo "Monitoring duration: ${DURATION} seconds"
echo "Sample interval: ${INTERVAL} seconds"
echo ""

# Function to get Spotlight process stats
get_spotlight_stats() {
    local timestamp=$(date '+%H:%M:%S')
    
    # Get mds processes
    mds_stats=$(ps aux | grep -E "mds|mdworker" | grep -v grep | awk '{
        cpu += $3; 
        mem += $4; 
        count++
    } END {
        printf "Processes: %d, CPU: %.1f%%, Memory: %.1f%%", count, cpu, mem
    }')
    
    # Get disk activity (if available)
    disk_activity=$(iostat -c 1 2>/dev/null | tail -1 | awk '{print "Disk: " $4 "% utilization"}' || echo "Disk: N/A")
    
    echo "[$timestamp] $mds_stats, $disk_activity"
}

# Header
echo "Time     | Spotlight Stats"
echo "---------|------------------------------------------------"

# Monitor loop
elapsed=0
while [ $elapsed -lt $DURATION ]; do
    get_spotlight_stats
    sleep $INTERVAL
    elapsed=$((elapsed + INTERVAL))
done

echo ""
echo "Monitoring completed"

# Show summary
echo ""
echo "Final Process Summary:"
echo "---------------------"
ps aux | grep -E "mds|mdworker" | grep -v grep | head -10

Automation and Scheduling

Automated Maintenance Script

Script for scheduled Spotlight maintenance:

#!/bin/bash

# Automated Spotlight maintenance script
# Can be run via cron or launchd

CONFIG_FILE="/etc/spotlight_maintenance.conf"
LOG_FILE="/var/log/spotlight_maintenance.log"

# Default configuration
REBUILD_INTERVAL=30  # days
CLEANUP_TEMP=true
MONITOR_PERFORMANCE=true

# Function to log with timestamp
log_message() {
    echo "$(date '+%Y-%m-%d %H:%M:%S') - $1" | tee -a "$LOG_FILE"
}

# Load configuration if exists
if [ -f "$CONFIG_FILE" ]; then
    source "$CONFIG_FILE"
    log_message "Configuration loaded from $CONFIG_FILE"
fi

# Function to check if rebuild is needed
needs_rebuild() {
    local index_age_file="/var/db/.spotlight_last_rebuild"
    
    if [ ! -f "$index_age_file" ]; then
        return 0  # No record, assume rebuild needed
    fi
    
    local last_rebuild=$(cat "$index_age_file")
    local current_time=$(date +%s)
    local age_days=$(( (current_time - last_rebuild) / 86400 ))
    
    if [ $age_days -gt $REBUILD_INTERVAL ]; then
        log_message "Index age: $age_days days, rebuild needed"
        return 0
    else
        log_message "Index age: $age_days days, rebuild not needed"
        return 1
    fi
}

# Function to perform rebuild
perform_rebuild() {
    log_message "Starting scheduled index rebuild"
    
    if sudo mdutil -E /; then
        log_message "Index rebuild initiated successfully"
        echo "$(date +%s)" | sudo tee /var/db/.spotlight_last_rebuild > /dev/null
        return 0
    else
        log_message "Index rebuild failed"
        return 1
    fi
}

# Function to cleanup temporary files
cleanup_temp_files() {
    if [ "$CLEANUP_TEMP" = true ]; then
        log_message "Cleaning up temporary Spotlight files"
        
        # Remove temporary index files
        sudo find /tmp -name ".Spotlight*" -exec rm -rf {} \; 2>/dev/null
        sudo find /var/tmp -name ".Spotlight*" -exec rm -rf {} \; 2>/dev/null
        
        log_message "Temporary file cleanup completed"
    fi
}

# Function to check performance
check_performance() {
    if [ "$MONITOR_PERFORMANCE" = true ]; then
        local mds_cpu=$(ps aux | grep mds | grep -v grep | awk '{sum += $3} END {print sum}')
        
        if [ -n "$mds_cpu" ] && [ "$mds_cpu" -gt 50 ]; then
            log_message "WARNING: High Spotlight CPU usage detected: ${mds_cpu}%"
        else
            log_message "Spotlight performance normal: ${mds_cpu:-0}% CPU"
        fi
    fi
}

# Main maintenance routine
log_message "Starting automated Spotlight maintenance"

check_performance
cleanup_temp_files

if needs_rebuild; then
    perform_rebuild
fi

log_message "Automated Spotlight maintenance completed"

Best Practices and Recommendations

1. Performance Considerations

  • Monitor system resources before disabling indexing
  • Consider partial exclusions instead of complete disable
  • Schedule maintenance during off-hours
  • Test changes on non-production systems first

2. Security and Privacy

  • Exclude sensitive directories from indexing
  • Regularly review and update exclusion lists
  • Consider the security implications of search functionality
  • Document all changes for compliance purposes

3. Enterprise Management

  • Standardize Spotlight policies across devices
  • Use configuration management tools for deployment
  • Implement monitoring and alerting for index issues
  • Maintain documentation of all customizations

4. Troubleshooting Guidelines

  • Always check system logs when issues occur
  • Test individual commands before running complex scripts
  • Keep backups of important data before major changes
  • Document the steps taken for future reference

Troubleshooting Common Issues

Index Corruption

#!/bin/bash

# Fix corrupted Spotlight index
echo "Fixing corrupted Spotlight index..."

# Stop indexing
sudo mdutil -i off /

# Remove corrupted index
sudo rm -rf /.Spotlight-V100

# Re-enable and rebuild
sudo mdutil -i on /
sudo mdutil -E /

echo "Index repair initiated"

High CPU Usage

#!/bin/bash

# Address high Spotlight CPU usage
echo "Addressing high Spotlight CPU usage..."

# Check current processes
echo "Current Spotlight processes:"
ps aux | grep -E "mds|mdworker" | grep -v grep

# Temporarily throttle indexing
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
sleep 5
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist

echo "Spotlight services restarted"

Conclusion

Effective Spotlight management is crucial for maintaining optimal macOS performance while preserving search functionality where needed. The scripts and techniques provided in this guide offer comprehensive solutions for various Spotlight management scenarios.

Key takeaways:

  • Understand the impact of indexing on system performance
  • Use appropriate scripts for your specific use case
  • Implement proper monitoring and maintenance procedures
  • Always test changes in a controlled environment
  • Document all modifications for future reference

Remember that disabling Spotlight indexing will significantly impact search functionality, so carefully consider the trade-offs before implementing these changes across your Mac fleet.

Tutorial

Nuevas actualizaciones y mejoras para Macfleet.

Configurando un Runner de GitHub Actions en un Mac Mini (Apple Silicon)

Runner de GitHub Actions

GitHub Actions es una plataforma poderosa de CI/CD que te permite automatizar tus flujos de trabajo de desarrollo de software. Aunque GitHub ofrece runners hospedados, los runners auto-hospedados proporcionan mayor control y personalización para tu configuración de CI/CD. Este tutorial te guía a través de la configuración y conexión de un runner auto-hospedado en un Mac mini para ejecutar pipelines de macOS.

Prerrequisitos

Antes de comenzar, asegúrate de tener:

  • Un Mac mini (regístrate en Macfleet)
  • Un repositorio de GitHub con derechos de administrador
  • Un gestor de paquetes instalado (preferiblemente Homebrew)
  • Git instalado en tu sistema

Paso 1: Crear una Cuenta de Usuario Dedicada

Primero, crea una cuenta de usuario dedicada para el runner de GitHub Actions:

# Crear la cuenta de usuario 'gh-runner'
sudo dscl . -create /Users/gh-runner
sudo dscl . -create /Users/gh-runner UserShell /bin/bash
sudo dscl . -create /Users/gh-runner RealName "GitHub runner"
sudo dscl . -create /Users/gh-runner UniqueID "1001"
sudo dscl . -create /Users/gh-runner PrimaryGroupID 20
sudo dscl . -create /Users/gh-runner NFSHomeDirectory /Users/gh-runner

# Establecer la contraseña para el usuario
sudo dscl . -passwd /Users/gh-runner tu_contraseña

# Agregar 'gh-runner' al grupo 'admin'
sudo dscl . -append /Groups/admin GroupMembership gh-runner

Cambia a la nueva cuenta de usuario:

su gh-runner

Paso 2: Instalar Software Requerido

Instala Git y Rosetta 2 (si usas Apple Silicon):

# Instalar Git si no está ya instalado
brew install git

# Instalar Rosetta 2 para Macs Apple Silicon
softwareupdate --install-rosetta

Paso 3: Configurar el Runner de GitHub Actions

  1. Ve a tu repositorio de GitHub
  2. Navega a Configuración > Actions > Runners

Runner de GitHub Actions

  1. Haz clic en "New self-hosted runner" (https://github.com/<username>/<repository>/settings/actions/runners/new)
  2. Selecciona macOS como imagen del runner y ARM64 como arquitectura
  3. Sigue los comandos proporcionados para descargar y configurar el runner

Runner de GitHub Actions

Crea un archivo .env en el directorio _work del runner:

# archivo _work/.env
ImageOS=macos15
XCODE_15_DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer
  1. Ejecuta el script run.sh en tu directorio del runner para completar la configuración.
  2. Verifica que el runner esté activo y escuchando trabajos en la terminal y revisa la configuración del repositorio de GitHub para la asociación del runner y el estado Idle.

Runner de GitHub Actions

Paso 4: Configurar Sudoers (Opcional)

Si tus acciones requieren privilegios de root, configura el archivo sudoers:

sudo visudo

Agrega la siguiente línea:

gh-runner ALL=(ALL) NOPASSWD: ALL

Paso 5: Usar el Runner en Flujos de Trabajo

Configura tu flujo de trabajo de GitHub Actions para usar el runner auto-hospedado:

name: Flujo de trabajo de muestra

on:
  workflow_dispatch:

jobs:
  build:
    runs-on: [self-hosted, macOS, ARM64]
    steps:
      - name: Instalar NodeJS
        run: brew install node

El runner está autenticado en tu repositorio y etiquetado con self-hosted, macOS, y ARM64. Úsalo en tus flujos de trabajo especificando estas etiquetas en el campo runs-on:

runs-on: [self-hosted, macOS, ARM64]

Mejores Prácticas

  • Mantén tu software del runner actualizado
  • Monitorea regularmente los logs del runner para problemas
  • Usa etiquetas específicas para diferentes tipos de runners
  • Implementa medidas de seguridad apropiadas
  • Considera usar múltiples runners para balanceo de carga

Solución de Problemas

Problemas comunes y soluciones:

  1. Runner no conectando:

    • Verifica conectividad de red
    • Verifica validez del token de GitHub
    • Asegúrate de permisos apropiados
  2. Fallas de construcción:

    • Verifica instalación de Xcode
    • Verifica dependencias requeridas
    • Revisa logs del flujo de trabajo
  3. Problemas de permisos:

    • Verifica permisos de usuario
    • Verifica configuración de sudoers
    • Revisa permisos del sistema de archivos

Conclusión

Ahora tienes un runner auto-hospedado de GitHub Actions configurado en tu Mac mini. Esta configuración te proporciona más control sobre tu entorno de CI/CD y te permite ejecutar flujos de trabajo específicos de macOS de manera eficiente.

Recuerda mantener regularmente tu runner y mantenerlo actualizado con los últimos parches de seguridad y versiones de software.

Aplicación Nativa

Aplicación nativa de Macfleet

Guía de Instalación de Macfleet

Macfleet es una solución poderosa de gestión de flota diseñada específicamente para entornos de Mac Mini alojados en la nube. Como proveedor de hosting en la nube de Mac Mini, puedes usar Macfleet para monitorear, gestionar y optimizar toda tu flota de instancias Mac virtualizadas.

Esta guía de instalación te llevará a través de la configuración del monitoreo de Macfleet en sistemas macOS, Windows y Linux para asegurar una supervisión integral de tu infraestructura en la nube.

🍎 macOS

  • Descarga el archivo .dmg para Mac aquí
  • Haz doble clic en el archivo .dmg descargado
  • Arrastra la aplicación Macfleet a la carpeta Aplicaciones
  • Expulsa el archivo .dmg
  • Abre Preferencias del Sistema > Seguridad y Privacidad
    • Pestaña Privacidad > Accesibilidad
    • Marca Macfleet para permitir el monitoreo
  • Inicia Macfleet desde Aplicaciones
  • El seguimiento comienza automáticamente

🪟 Windows

  • Descarga el archivo .exe para Windows aquí
  • Haz clic derecho en el archivo .exe > "Ejecutar como administrador"
  • Sigue el asistente de instalación
  • Acepta los términos y condiciones
  • Permite en Windows Defender si se solicita
  • Concede permisos de monitoreo de aplicaciones
  • Inicia Macfleet desde el Menú Inicio
  • La aplicación comienza el seguimiento automáticamente

🐧 Linux

  • Descarga el paquete .deb (Ubuntu/Debian) o .rpm (CentOS/RHEL) aquí
  • Instala usando tu gestor de paquetes
    • Ubuntu/Debian: sudo dpkg -i Macfleet-linux.deb
    • CentOS/RHEL: sudo rpm -ivh Macfleet-linux.rpm
  • Permite permisos de acceso X11 si se solicita
  • Agrega el usuario a los grupos apropiados si es necesario
  • Inicia Macfleet desde el menú de Aplicaciones
  • La aplicación comienza el seguimiento automáticamente

Nota: Después de la instalación en todos los sistemas, inicia sesión con tus credenciales de Macfleet para sincronizar datos con tu panel de control.