MokoConsulting/mokoplatform
1
0
Fork 0
Code Issues 9 Pull Requests Releases 8 Wiki Activity

feat(cli): register deploy/ tools in COMMAND_MAP #232

New Issue
Closed
opened 2026-05-31 14:18:08 +00:00 by jmiller · 2 comments
jmiller commented 2026-05-31 14:18:08 +00:00
Owner
Copy Link
Copy Source

Problem

The entire deploy/ directory (7 tools) is inaccessible via bin/moko. Deployment workflows can only be triggered via CI/CD or direct PHP invocation.

Proposed Commands

  • deploy/deploy-joomla.php -> deploy:joomla
  • deploy/deploy-dolibarr.php -> deploy:dolibarr
  • deploy/deploy-sftp.php -> deploy:sftp
  • deploy/backup-before-deploy.php -> deploy:backup
  • deploy/health-check.php -> deploy:health-check
  • deploy/rollback-joomla.php -> deploy:rollback
  • deploy/sync-joomla.php -> deploy:sync

Acceptance Criteria

  • All 7 deploy tools registered in bin/moko COMMAND_MAP
  • php bin/moko list shows Deploy group
  • Each tool responds to --help
  • Update COMMANDS section in bin/moko header docblock
## Problem The entire deploy/ directory (7 tools) is inaccessible via bin/moko. Deployment workflows can only be triggered via CI/CD or direct PHP invocation. ## Proposed Commands - deploy/deploy-joomla.php -> deploy:joomla - deploy/deploy-dolibarr.php -> deploy:dolibarr - deploy/deploy-sftp.php -> deploy:sftp - deploy/backup-before-deploy.php -> deploy:backup - deploy/health-check.php -> deploy:health-check - deploy/rollback-joomla.php -> deploy:rollback - deploy/sync-joomla.php -> deploy:sync ## Acceptance Criteria - [ ] All 7 deploy tools registered in bin/moko COMMAND_MAP - [ ] php bin/moko list shows Deploy group - [ ] Each tool responds to --help - [ ] Update COMMANDS section in bin/moko header docblock
jmiller added the build label 2026-05-31 14:18:08 +00:00
jmiller commented 2026-05-31 14:18:10 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/232-feat-cli-register-deploy-tools-in-comman

git fetch origin
git checkout feature/232-feat-cli-register-deploy-tools-in-comman
Branch created: [`feature/232-feat-cli-register-deploy-tools-in-comman`](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/src/branch/feature/232-feat-cli-register-deploy-tools-in-comman) ```bash git fetch origin git checkout feature/232-feat-cli-register-deploy-tools-in-comman ```
jmiller commented 2026-05-31 14:34:46 +00:00
Author
Owner
Copy Link
Copy Source

All 7 deploy tools registered in COMMAND_MAP as deploy:* group. Also fixed ../../vendor/autoload.php path bug in release/ scripts discovered during smoke testing. cli/deploy_joomla.php registered as deploy:joomla (primary), deploy/deploy-joomla.php as deploy:joomla-legacy.

All 7 deploy tools registered in COMMAND_MAP as `deploy:*` group. Also fixed `../../vendor/autoload.php` path bug in `release/` scripts discovered during smoke testing. `cli/deploy_joomla.php` registered as `deploy:joomla` (primary), `deploy/deploy-joomla.php` as `deploy:joomla-legacy`.
Sign in to join this conversation.
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels build
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/mokoplatform#232
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?