docs: add missing commands and Kick integration

- Add coolify:setup-ci command documentation
- Add coolify:destroy command documentation
- Add Laravel Kick integration documentation
- Update dashboard API docs with Kick endpoints
- Update dashboard overview to mention Kick tab
- Update reference docs with Kick config options
- Update sidebar navigation

Author: StuMason

docs/astro.config.mjs

@@ -58,13 +58,16 @@ export default defineConfig({
 						{ label: 'coolify:logs', slug: 'commands/logs' },
 						{ label: 'coolify:restart', slug: 'commands/restart' },
 						{ label: 'coolify:rollback', slug: 'commands/rollback' },
+						{ label: 'coolify:setup-ci', slug: 'commands/setup-ci' },
+						{ label: 'coolify:destroy', slug: 'commands/destroy' },
 					],
 				},
 				{
 					label: 'Dashboard',
 					items: [
 						{ label: 'Overview', slug: 'dashboard/overview' },
 						{ label: 'Authentication', slug: 'dashboard/authentication' },
+						{ label: 'Kick Integration', slug: 'dashboard/kick' },
 						{ label: 'API', slug: 'dashboard/api' },
 					],
 				},

docs/src/content/docs/commands/destroy.md

@@ -0,0 +1,51 @@
+---
+title: coolify:destroy
+description: Destroy provisioned infrastructure on Coolify
+---
+
+## Usage
+
+```bash
+php artisan coolify:destroy
+```
+
+## Options
+
+```bash
+--force    # Skip confirmation prompts
+```
+
+## What It Does
+
+Removes all resources created by `coolify:provision`:
+
+- Application container
+- PostgreSQL database
+- Dragonfly cache
+- Project (if empty)
+
+## Warning
+
+This is a destructive operation. All data in databases will be permanently deleted.
+
+## Examples
+
+Interactive destruction (with confirmations):
+
+```bash
+php artisan coolify:destroy
+```
+
+Force destruction without prompts:
+
+```bash
+php artisan coolify:destroy --force
+```
+
+## Cleanup
+
+After destruction, you may want to remove the `.env` entries:
+
+```bash
+COOLIFY_PROJECT_UUID=
+```

docs/src/content/docs/commands/setup-ci.md

@@ -0,0 +1,82 @@
+---
+title: coolify:setup-ci
+description: Generate GitHub Actions workflow for CI/CD deployments
+---
+
+## Usage
+
+```bash
+php artisan coolify:setup-ci
+```
+
+## Options
+
+```bash
+--branch=     # Branch to deploy on push (default: main)
+--no-manual   # Disable manual workflow_dispatch trigger
+--force       # Overwrite existing workflow file
+```
+
+## What It Does
+
+Generates `.github/workflows/coolify-deploy.yml` with:
+
+- Automatic deployment on push to specified branch
+- Manual trigger via GitHub Actions UI
+- Proper secrets configuration
+
+## Examples
+
+Basic setup:
+
+```bash
+php artisan coolify:setup-ci
+```
+
+Deploy on push to `production` branch:
+
+```bash
+php artisan coolify:setup-ci --branch=production
+```
+
+Overwrite existing workflow:
+
+```bash
+php artisan coolify:setup-ci --force
+```
+
+## Generated Workflow
+
+```yaml
+name: Deploy to Coolify
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: shivammathur/setup-php@v2
+        with:
+          php-version: '8.4'
+      - run: composer install --no-dev --optimize-autoloader
+      - run: php artisan coolify:deploy --force --wait
+        env:
+          COOLIFY_URL: ${{ secrets.COOLIFY_URL }}
+          COOLIFY_TOKEN: ${{ secrets.COOLIFY_TOKEN }}
+          COOLIFY_PROJECT_UUID: ${{ secrets.COOLIFY_PROJECT_UUID }}
+```
+
+## Required Secrets
+
+Add these to your GitHub repository settings:
+
+| Secret | Description |
+|--------|-------------|
+| `COOLIFY_URL` | Your Coolify instance URL |
+| `COOLIFY_TOKEN` | API token from Coolify |
+| `COOLIFY_PROJECT_UUID` | Project UUID (from `coolify:provision`) |

docs/src/content/docs/dashboard/api.md

@@ -76,3 +76,27 @@ GET    /api/projects/{uuid}/environments     # List environments
 ```
 GET    /api/stats                            # Aggregated dashboard data
 ```
+
+## Kick Integration
+
+These endpoints proxy requests to Laravel Kick on your deployed applications.
+
+```
+GET    /api/kick/{appUuid}/status            # Check if Kick is configured
+GET    /api/kick/{appUuid}/health            # Health check results
+GET    /api/kick/{appUuid}/stats             # System stats (CPU, memory, disk)
+GET    /api/kick/{appUuid}/logs              # List log files
+GET    /api/kick/{appUuid}/logs/{file}       # Read log entries
+GET    /api/kick/{appUuid}/queue             # Queue status
+GET    /api/kick/{appUuid}/queue/failed      # Failed jobs list
+GET    /api/kick/{appUuid}/artisan           # List available commands
+POST   /api/kick/{appUuid}/artisan           # Execute artisan command
+```
+
+### Query Parameters
+
+Log reading supports:
+
+- `level` - Filter by log level (DEBUG, INFO, WARNING, ERROR, etc.)
+- `search` - Full-text search
+- `lines` - Number of lines to return (default: 100)

docs/src/content/docs/dashboard/kick.md

@@ -0,0 +1,138 @@
+---
+title: Laravel Kick Integration
+description: Enhanced application introspection with Laravel Kick
+---
+
+The dashboard integrates with [Laravel Kick](https://github.com/StuMason/laravel-kick) to provide deep introspection into your running applications.
+
+## What is Laravel Kick?
+
+Laravel Kick is a package you install on your **deployed application** that exposes secure endpoints for:
+
+- Health checks (database, cache, storage, redis)
+- System stats (CPU, memory, disk, uptime)
+- Log file viewing with filtering
+- Queue status and failed jobs
+- Artisan command execution
+
+## Setup
+
+### 1. Install Kick on Your Deployed App
+
+```bash
+composer require stumason/laravel-kick
+```
+
+### 2. Configure Environment Variables
+
+Add to your application's Coolify environment variables:
+
+```bash
+KICK_ENABLED=true
+KICK_TOKEN=your-secure-random-token
+```
+
+Generate a secure token:
+
+```bash
+openssl rand -base64 32
+```
+
+### 3. Deploy
+
+After deployment, a **Kick** tab appears in the dashboard for that application.
+
+## Dashboard Features
+
+### Overview Tab
+
+- **Health Checks** - Real-time status of database, cache, storage, and redis connections
+- **System Stats** - CPU load, memory usage, disk space, and uptime
+- **Queue Status** - Quick view of pending jobs and failed count
+
+### Logs Tab
+
+- **File Selection** - Browse all Laravel log files
+- **Level Filtering** - Filter by DEBUG, INFO, WARNING, ERROR, etc.
+- **Search** - Full-text search across log entries
+- **Line Limits** - Control how many lines to display
+
+### Queue Tab
+
+- **Connection Info** - Current queue driver and status
+- **Queue Sizes** - Pending jobs per queue (default, high, low)
+- **Failed Jobs** - List of failed jobs with exception details
+
+### Artisan Tab
+
+- **Command List** - All whitelisted artisan commands
+- **Execution** - Run commands directly from the dashboard
+- **Output** - View command output and exit codes
+
+## Security
+
+### Token Authentication
+
+All Kick endpoints require the `KICK_TOKEN` for authentication. The token is:
+
+- Sent as a Bearer token in the Authorization header
+- Never exposed in the dashboard UI
+- Required for every request
+
+### Command Whitelisting
+
+Artisan commands must be explicitly whitelisted in your Kick configuration. By default, only safe read-only commands are allowed.
+
+### Rate Limiting
+
+The artisan execution endpoint is rate-limited to 10 requests per minute to prevent abuse.
+
+## Configuration
+
+In your **Laravel Coolify** config (`config/coolify.php`):
+
+```php
+'kick' => [
+    // Enable/disable kick integration globally
+    'enabled' => env('COOLIFY_KICK_ENABLED', true),
+
+    // Cache TTL for kick config lookups (seconds)
+    'cache_ttl' => env('COOLIFY_KICK_CACHE_TTL', 60),
+
+    // Timeout for kick API requests (seconds)
+    'timeout' => env('COOLIFY_KICK_TIMEOUT', 10),
+],
+```
+
+In your **deployed app's** Coolify environment:
+
+```bash
+KICK_ENABLED=true
+KICK_TOKEN=your-secure-token
+KICK_PREFIX=kick              # Optional, defaults to 'kick'
+```
+
+## Troubleshooting
+
+### "Kick Service Unavailable" Error
+
+This usually means:
+
+1. **Route cache needs rebuilding** - Run `php artisan route:cache` on the server
+2. **Application is restarting** - Wait for deployment to complete
+3. **Kick package not installed** - Verify with `composer show stumason/laravel-kick`
+
+### Tab Not Appearing
+
+The Kick tab only appears when:
+
+1. `KICK_ENABLED=true` is set in the app's environment
+2. `KICK_TOKEN` is configured
+3. The Kick endpoints are reachable
+
+### Authentication Errors
+
+Verify your `KICK_TOKEN` matches between:
+
+- The app's Coolify environment variables
+- What Laravel Kick expects on the deployed app

docs/src/content/docs/dashboard/overview.md

@@ -88,6 +88,19 @@ The dashboard includes multiple pages accessible from the sidebar:
 | **Resources** | All databases and services in your environment |
 | **Configuration** | Environment variables, settings, backup schedules |
 | **Logs** | Real-time application logs |
+| **Kick** | Laravel Kick introspection (when configured) |
+
+### Kick Tab
+
+When your deployed application has [Laravel Kick](https://github.com/StuMason/laravel-kick) installed and configured, a **Kick** tab appears with:
+
+- Health checks (database, cache, storage, redis)
+- System stats (CPU, memory, disk, uptime)
+- Log viewer with filtering and search
+- Queue status and failed jobs
+- Artisan command execution
+
+See [Kick Integration](/dashboard/kick) for setup details.
 
 ## Quick Actions
 

docs/src/content/docs/reference/config.md

@@ -67,6 +67,13 @@ return [
             'max_execution_time' => env('COOLIFY_PHP_MAX_EXECUTION_TIME', 60),
         ],
     ],
+
+    // Laravel Kick integration
+    'kick' => [
+        'enabled' => env('COOLIFY_KICK_ENABLED', true),
+        'cache_ttl' => env('COOLIFY_KICK_CACHE_TTL', 60),
+        'timeout' => env('COOLIFY_KICK_TIMEOUT', 10),
+    ],
 ];
 ```
 

docs/src/content/docs/reference/env-vars.md

@@ -57,6 +57,26 @@ When `COOLIFY_USE_BASE_IMAGE=false`:
 - Build time: ~12 minutes
 - Use this if you need custom PHP extensions
 
+## Kick Integration
+
+These control how Laravel Coolify connects to Laravel Kick on your deployed apps.
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `COOLIFY_KICK_ENABLED` | `true` | Enable Kick integration |
+| `COOLIFY_KICK_CACHE_TTL` | `60` | Cache Kick config lookups (seconds) |
+| `COOLIFY_KICK_TIMEOUT` | `10` | Kick API timeout (seconds) |
+
+### On Your Deployed App
+
+These are set in your **application's Coolify environment** (not your local `.env`):
+
+| Variable | Description |
+|----------|-------------|
+| `KICK_ENABLED` | Set to `true` to enable Kick endpoints |
+| `KICK_TOKEN` | Authentication token for Kick API |
+| `KICK_PREFIX` | Optional, defaults to `kick` |
+
 ## How Application Lookup Works
 
 Only `COOLIFY_PROJECT_UUID` is stored in your `.env`. All other resource UUIDs (applications, databases, etc.) are fetched from the Coolify API.