3

workflows-rs-deployment

Jonathan Miller edited this page 2026-05-20 01:26:28 +00:00

Table of Contents

• Release Staging (RS) Server Deployment
• Current Release Pipeline
• See Also

← Home

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

• Dev Deployment — development server (still active)
• Demo Deployment — demo server (still active)
• Auto Release — release pipeline that replaced RS deployment
• Release System — end-to-end release lifecycle

---

Repo: moko-platform · moko-platform wiki

Field	Value
Minimum Version	04.07.00
Platform	all
Applies To	All repositories

Revision	Date	Author	Description
1.0	2026-05-08	Moko Consulting	Initial version