mirrors/Mole

mirror of https://github.com/tw93/Mole.git synced 2026-02-04 16:49:41 +00:00

Files

History

Bhadra 6e0d850d6a feat(windows): add Windows support Phase 2 - cleanup features

Add cleanup modules and command scripts for Windows:
- lib/clean: user, caches, dev, apps, system cleanup modules
- bin/clean: deep cleanup orchestrator with dry-run and whitelist
- bin/uninstall: interactive app uninstaller
- bin/optimize: system optimization and health checks
- bin/purge: project artifact cleanup

All scripts support dry-run mode and follow safe deletion practices.

2026-01-08 15:46:45 +05:30

..

feat(windows): add Windows support Phase 2 - cleanup features

2026-01-08 15:46:45 +05:30

feat(windows): add Windows support Phase 2 - cleanup features

2026-01-08 15:46:45 +05:30

go.mod

feat(windows): add Windows support Phase 1 - core infrastructure

2026-01-08 14:24:11 +05:30

go.sum

feat(windows): add Windows support Phase 1 - core infrastructure

2026-01-08 14:24:11 +05:30

install.ps1

fix(windows): fix encoding issues in PowerShell scripts

2026-01-08 14:46:05 +05:30

mole.ps1

feat(windows): add Windows support Phase 1 - core infrastructure

2026-01-08 14:24:11 +05:30

README.md

feat(windows): add Windows support Phase 1 - core infrastructure

2026-01-08 14:24:11 +05:30

README.md

Mole for Windows

Windows support for Mole - A system maintenance toolkit.

Requirements

Windows 10/11
PowerShell 5.1 or later (pre-installed on Windows 10/11)
Optional: Go 1.24+ (for building TUI tools)

Installation

Quick Install

# Clone the repository
git clone https://github.com/tw93/Mole.git
cd Mole/windows

# Run the installer
.\install.ps1 -AddToPath

Manual Installation

# Install to custom location
.\install.ps1 -InstallDir C:\Tools\Mole -AddToPath

# Create Start Menu shortcut
.\install.ps1 -AddToPath -CreateShortcut

Uninstall

.\install.ps1 -Uninstall

Usage

# Interactive menu
mole

# Show help
mole -ShowHelp

# Show version
mole -Version

Environment Variables

Variable	Description
`MOLE_DRY_RUN=1`	Preview changes without making them
`MOLE_DEBUG=1`	Enable debug output

Directory Structure

windows/
├── mole.ps1          # Main CLI entry point
├── install.ps1       # Windows installer
├── go.mod            # Go module definition
├── go.sum            # Go dependencies
└── lib/
    └── core/
        ├── base.ps1      # Core definitions and utilities
        ├── common.ps1    # Common functions loader
        ├── file_ops.ps1  # Safe file operations
        ├── log.ps1       # Logging functions
        └── ui.ps1        # Interactive UI components

Configuration

Mole stores its configuration in:

Config: ~\.config\mole\
Cache: ~\.cache\mole\
Whitelist: ~\.config\mole\whitelist.txt

Development

Phase 1: Core Infrastructure (Current)

install.ps1 - Windows installer
mole.ps1 - Main CLI entry point
lib/core/* - Core utility libraries

Phase 2: Cleanup Features (Planned)

bin/clean.ps1 - Deep cleanup orchestrator
bin/uninstall.ps1 - App removal with leftover detection
bin/optimize.ps1 - Cache rebuild and service refresh
bin/purge.ps1 - Aggressive cleanup mode
lib/clean/* - Cleanup modules

Phase 3: TUI Tools (Planned)

cmd/analyze/ - Disk usage analyzer (Go)
cmd/status/ - Real-time system monitor (Go)
bin/analyze.ps1 - Analyzer wrapper
bin/status.ps1 - Status wrapper

Phase 4: Testing & CI (Planned)

tests/ - Pester tests
GitHub Actions workflows
scripts/build.ps1 - Build automation

License

Same license as the main Mole project.