Files
moko-platform/docs/workflows/rs-deployment.md
T
Jonathan Miller 96c7bd9e46 docs: update all references to MokoConsulting org and Gitea URLs
- mokoconsulting-tech → MokoConsulting across all docs
- github.com → git.mokoconsulting.tech
- CLI examples updated with new org name

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-16 22:21:59 -05:00

1.8 KiB

MokoStandards

Release Staging (RS) Server Deployment

DEPRECATED (v04.06.00): The deploy-rs.yml workflow has been retired. RS deployment is now handled exclusively through the release pipeline. Release artifacts are published via GitHub Releases (auto-release.yml) and distributed through platform-specific channels (Joomla updates.xml, Dolibarr update.txt). The RS_FTP_* variables and secrets are no longer used.

Current Release Pipeline

dev → [alpha] → [beta] → rc → version/XX → main → dev
       optional   optional

Production/RS deployment is achieved by:

  1. Joomla — GitHub Release ZIP + SHA-256 + updates.xml with 5 stability entries (development, alpha, beta, release-candidate, vXX)
  2. Dolibarr — GitHub Release + update.txt
  3. Generic — GitHub Release

There is no longer a separate SFTP deployment step to a release staging server.

See Also