add ssh connection

.claude/settings.local.json

@@ -0,0 +1,8 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(grep:*)"
+    ],
+    "deny": []
+  }
+}

CLAUDE.md

@@ -0,0 +1,112 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+Larabase is an Electron desktop application specifically designed for Laravel developers. It's an opinionated database GUI tool with seamless Laravel integration, providing specialized features for Laravel project development workflows.
+
+## Key Commands
+
+### Development
+
+```bash
+# Start development server
+npm run dev
+
+# Build for current platform
+npm run build
+
+# Platform-specific builds
+npm run build:mac-apple   # macOS (Apple Silicon)
+npm run build:mac-intel   # macOS (Intel)
+npm run build:win         # Windows
+npm run build:linux       # Linux
+
+# Code Quality
+npm run lint              # Run ESLint with auto-fix
+npm run format            # Run Prettier formatter
+```
+
+## Architecture Overview
+
+Larabase follows the standard Electron architecture with main and renderer processes:
+
+### Main Process (`electron/`)
+
+- **Main Entry:** `electron/main/index.ts` - Application initialization, window management
+- **Modules:** `electron/modules/` - Backend functionality implemented as service modules
+    - Database operations (`mysql.ts`, `tables.ts`, `sql-executor.ts`)
+    - SSH tunneling (`ssh.ts`)
+    - Redis integration (`redis.ts`)
+    - Project management (`projects.ts`)
+    - Terminal emulation (`terminal.ts`)
+- **Helpers:** `electron/helpers/` - Utility functions for various operations
+
+### Renderer Process (`src/`)
+
+- **Components:** `src/components/` - Vue.js UI components organized by functionality
+- **State Management:** `src/store/` - Pinia stores for application state
+- **Services:** `src/services/` - API communication and frontend services
+- **Types:** `src/types/` - TypeScript interfaces and type definitions
+
+### Communication Pattern
+
+The application follows a communication pattern using Electron's IPC:
+
+1. Front-end requests through `window.electron.ipcRenderer.invoke(channel, ...args)`
+2. Backend handles via IPC handlers registered in modules
+3. Results returned to front-end asynchronously
+
+## Key Features & Implementation
+
+### Database Connections
+
+- Supports direct MySQL connections and SSH tunneling
+- Connection details stored securely via electron-store
+- SSH tunneling implemented using ssh2 library and dynamic port forwarding
+
+### Query Management
+
+- Monaco editor for SQL editing with syntax highlighting
+- SQL execution handled through mysql2 library
+- Results displayed in Vue data table components with sorting/filtering
+
+### Laravel Integration
+
+- Specialized views for Laravel-specific database operations
+- Migration management interface
+- .env file editor
+- Terminal integration for running Artisan commands
+
+### Redis Support
+
+- Redis database browsing and management
+- Key-value storage interaction
+- Cache management operations
+
+## Data Flow
+
+1. User interacts with Vue UI components
+2. Actions trigger state changes in Pinia stores
+3. Stores dispatch IPC calls to Electron backend
+4. Backend modules execute operations and return results
+5. UI updates based on returned data
+6. Always use preload file to expose necessary APIs to the renderer process
+7. Do not comment on the code unless extremely necessary to avoid polluting the codebase
+8. Always create a module in the electron/modules for grouped functionality (e.g., database, SSH, Redis) to maintain organization
+
+## Technology Stack
+
+- **Electron**: Cross-platform desktop framework
+- **Vue.js 3**: Frontend framework with TypeScript
+- **Pinia**: State management
+- **Tailwind CSS & DaisyUI**: Styling
+- **Monaco Editor**: Code editor component
+- **MySQL2**: Database connectivity
+- **SSH2**: SSH tunneling support
+- **IoRedis**: Redis client functionality
+
+## Code Tips and Tricks
+
+- Always use toRaw for reactive objects to avoid errors like "An object could not be cloned."

README.md

@@ -75,6 +75,48 @@ npm run build:win         # Windows
 npm run build:linux       # Linux
 ```
 
+## SSH Tunneling Support
+
+Larabase now supports connecting to MySQL databases through SSH tunnels. This feature allows you to:
+
+1. Connect to remote database servers securely via SSH
+2. Work with databases that are not directly accessible from your machine
+3. Maintain the same workflow and functionality as with local database connections
+
+### How SSH Tunneling Works
+
+SSH tunneling creates a secure encrypted channel between your local machine and the remote server:
+
+1. An SSH connection is established to the remote server
+2. A local port is forwarded to the remote database server port
+3. Your connection uses this local port, which securely tunnels traffic to the remote server
+4. All database operations work transparently through this tunnel
+
+### Implementation Details
+
+The SSH tunneling implementation uses:
+
+- The `ssh2` library for SSH connections and port forwarding
+- The `portfinder` library to dynamically find available local ports
+- The existing MySQL connection module, modified to work through SSH tunnels
+
+### Setup
+
+To use SSH tunneling, you need:
+
+1. SSH access to the remote server (user/password or key-based authentication)
+2. The remote server needs access to the MySQL database
+3. Create a connection in Larabase with SSH tunneling enabled
+
+### Usage
+
+When creating a new connection, select the SSH option and provide:
+
+1. SSH server details (host, port, user, password/private key)
+2. Remote database details (host, port, user, password, database name)
+
+Once connected, you can use all Larabase features as you would with a local database.
+
 ## License
 
 This project is licensed under the MIT License - see the LICENSE file for details.