MokoConsulting/MokoWaaS
1
1
Fork 0
Code Issues 1 Pull Requests Actions Packages Licenses 2 Releases 5 Wiki Activity

feat: integrate MokoGitea license system for update checks #107

Merged
jmiller merged 1 commits from dev into main 2026-05-31 15:43:00 +00:00
Conversation 0 Commits 1 Files Changed 8
+82 -59
jmiller commented 2026-05-31 15:40:29 +00:00
Owner
Copy Link
Copy Source

Summary

  • Update server now points to MokoGitea's dynamic updates.xml endpoint instead of static file in repo
  • License keys (dlid) are managed via Joomla's native System ? Update Sites download key UI
  • Legacy static update site URLs auto-migrated to dynamic endpoint on install/update
  • Static updates.xml removed from repo and added to .gitignore
  • Includes prior fix: remove secondary master user enforcement (02.29.04)

Test plan

  • Fresh install registers update site pointing to dynamic endpoint
  • Existing installs with old static URL get migrated on update
  • Download key entered in System ? Update Sites is sent as ?dlid= to MokoGitea
  • Valid key returns update XML with available versions
  • Invalid/missing key returns empty <updates></updates>

?? Generated with Claude Code

## Summary - Update server now points to MokoGitea's dynamic `updates.xml` endpoint instead of static file in repo - License keys (dlid) are managed via Joomla's native **System ? Update Sites** download key UI - Legacy static update site URLs auto-migrated to dynamic endpoint on install/update - Static `updates.xml` removed from repo and added to `.gitignore` - Includes prior fix: remove secondary master user enforcement (02.29.04) ## Test plan - [ ] Fresh install registers update site pointing to dynamic endpoint - [ ] Existing installs with old static URL get migrated on update - [ ] Download key entered in System ? Update Sites is sent as `?dlid=` to MokoGitea - [ ] Valid key returns update XML with available versions - [ ] Invalid/missing key returns empty `<updates></updates>` ?? Generated with [Claude Code](https://claude.com/claude-code)
jmiller added 1 commit 2026-05-31 15:40:29 +00:00
feat: integrate MokoGitea license system for update checks 1b6747d9f9 
Update server now points to MokoGitea's dynamic endpoint which
validates license keys (dlid) and generates update XML from git
releases. Users enter the download key via Joomla's native
System → Update Sites interface. Legacy static URLs are auto-migrated
on install/update.

Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit ceb6b8de3d into main 2026-05-31 15:43:00 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
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
 major-release
Major version release (breaking changes)
 minor-release
Minor version release (XX.YY.00)
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 needs-testing
Requires manual or automated testing
 patch-release
Patch version release (XX.YY.ZZ)
 php
PHP code changes
 priority: critical
Critical priority, must be addressed immediately
 priority: high
High priority
 priority: low
Low priority
 priority: medium
Medium priority
 push-failure
File push failure requiring attention
 python
Python code changes
 regression
Regression from a previous working state
 release-candidate
Release candidate build
 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
 standards-violation
Standards compliance failure
 status: blocked
Blocked by another issue or dependency
 status: in-progress
Currently being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Temporarily on hold
 status: pending
Pending action or decision
 status: wontfix
This will not be worked on
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 test-failure
Automated test 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: release
Release preparation or tracking
 type: test
Test suite additions or changes
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-branch
Version branch related
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
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/MokoWaaS#107
Delete Branch "dev"

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?