Public Access
Jonathan Miller
bd5f676e0a
Platform: moko-platform CI / Gate 2: Unit Tests (8.1) (push) Has been cancelled
Platform: moko-platform CI / Gate 2: Unit Tests (8.2) (push) Has been cancelled
Platform: moko-platform CI / Gate 2: Unit Tests (8.3) (push) Has been cancelled
Platform: moko-platform CI / Gate 3: Self-Health Check (push) Has been cancelled
Platform: moko-platform CI / Gate 4: Governance (push) Has been cancelled
Platform: moko-platform CI / Gate 5: Template Integrity (push) Has been cancelled
Platform: moko-platform CI / CI Summary (push) Has been cancelled
Generic: Repo Health / Scripts governance (push) Has been cancelled
Generic: Repo Health / Repository health (push) Has been cancelled
Generic: Repo Health / Report Issues (push) Has been cancelled
Generic: Repo Health / Site Health (push) Has been cancelled
Generic: Repo Health / Access control (push) Has been cancelled
Platform: moko-platform CI / Gate 1: Code Quality (push) Has been cancelled
# Conflicts: # cli/manifest_licensing.php
SSH Manager Profiles
Profiles allow you to configure command aliases and hooks for specific project types.
Available Profiles
default.json- Basic SSH operations (minimal setup)frappe.json- Frappe/ERPNext specific commands and hooksdocker.json- Docker container managementkubernetes.json- Kubernetes cluster operationsnodejs.json- Node.js application deploymentpython.json- Python application deployment
Creating Custom Profiles
Create a JSON file in this directory with your custom configuration:
{
"name": "my-project",
"description": "Custom profile for my project",
"commandAliases": {
"deploy": "git pull && npm install && npm run build",
"restart": "pm2 restart all"
},
"hooks": {
"pre-deploy": {
"enabled": true,
"actions": [...]
}
}
}
Loading Profiles
Profiles can be loaded via:
- Environment variable:
SSH_MANAGER_PROFILE=frappe - Configuration file:
.ssh-manager-profilein project root - Default: Uses
default.jsonif no profile specified