MokoConsulting/MokoGIT
1
0
Fork 0
Code Issues 146 Pull Requests Releases 96 Wiki Activity

feat(licenses): full commercial license management system #296

New Issue
Closed
opened 2026-05-31 04:24:14 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-31 04:24:14 +00:00
Owner
Copy Link
Copy Source

Full Commercial License Management System

This is a revenue-generating platform feature — organizations use MokoGitea to distribute and license their commercial Joomla/Dolibarr extensions.

Architecture

License Packages (tiers)

  • Org-level and repo-level packages that stack
  • Duration: lifetime, annual, monthly, custom dates
  • Channels: which update streams the key grants access to
  • Max sites: limit how many domains can use a key
  • Active/inactive toggle
  • Editable by org owner/repo admin, deletable by site admin only
  • Master package auto-created, never deletable

License Keys

  • Purchasable via API (for payment gateway integration)
  • Assignable to: customer name, email, domain(s)
  • Multiple keys per user for multi-site
  • Copyable (not secret) with copy button
  • Revocable but not deletable (except by site admin)
  • Master key auto-regenerates on revoke
  • Expiry editable for non-master keys
  • Domain restriction enforcement on update feeds

Update Server Integration

  • Per-repo platform setting (Joomla/Dolibarr/Both)
  • Require-key toggle per repo
  • Update feeds validate key + check channels + record usage
  • Invalid/missing key = empty response (Joomla compatible)

API Endpoints (for payment integration)

  • POST /api/v1/repos/{owner}/{repo}/license-keys — purchase/create key
  • PATCH /api/v1/repos/{owner}/{repo}/license-keys/{id} — update expiry, domains
  • GET /api/v1/repos/{owner}/{repo}/license-keys/{id}/usage — usage stats
  • POST /api/v1/repos/{owner}/{repo}/license-keys/{id}/validate — validate a key

Remaining work

  • Key expiry editing UI
  • Domain assignment UI and enforcement
  • Multi-site key management
  • Org-level license page improvements
  • Channels as multiselect from org streams
  • Team permissions for license management
  • Payment webhook endpoint (Stripe/PayPal)
  • License validation API endpoint
  • Key usage dashboard/analytics
  • Wiki documentation
  • Convert MokoWaaS to new system

Created by @MokoBot - Claude Opus 4.6

## Full Commercial License Management System This is a revenue-generating platform feature — organizations use MokoGitea to distribute and license their commercial Joomla/Dolibarr extensions. ### Architecture #### License Packages (tiers) - Org-level and repo-level packages that stack - Duration: lifetime, annual, monthly, custom dates - Channels: which update streams the key grants access to - Max sites: limit how many domains can use a key - Active/inactive toggle - Editable by org owner/repo admin, deletable by site admin only - Master package auto-created, never deletable #### License Keys - Purchasable via API (for payment gateway integration) - Assignable to: customer name, email, domain(s) - Multiple keys per user for multi-site - Copyable (not secret) with copy button - Revocable but not deletable (except by site admin) - Master key auto-regenerates on revoke - Expiry editable for non-master keys - Domain restriction enforcement on update feeds #### Update Server Integration - Per-repo platform setting (Joomla/Dolibarr/Both) - Require-key toggle per repo - Update feeds validate key + check channels + record usage - Invalid/missing key = empty response (Joomla compatible) #### API Endpoints (for payment integration) - POST /api/v1/repos/{owner}/{repo}/license-keys — purchase/create key - PATCH /api/v1/repos/{owner}/{repo}/license-keys/{id} — update expiry, domains - GET /api/v1/repos/{owner}/{repo}/license-keys/{id}/usage — usage stats - POST /api/v1/repos/{owner}/{repo}/license-keys/{id}/validate — validate a key #### Remaining work - [ ] Key expiry editing UI - [ ] Domain assignment UI and enforcement - [ ] Multi-site key management - [ ] Org-level license page improvements - [ ] Channels as multiselect from org streams - [ ] Team permissions for license management - [ ] Payment webhook endpoint (Stripe/PayPal) - [ ] License validation API endpoint - [ ] Key usage dashboard/analytics - [ ] Wiki documentation - [ ] Convert MokoWaaS to new system --- *Created by @MokoBot - Claude Opus 4.6*
jmiller commented 2026-06-27 02:21:02 +00:00
Author
Owner
Copy Link
Copy Source

Closing — core licensing system completed in #615-#631 (16 API endpoints, 5 model tables, admin UI, ed25519 signing). Remaining sub-features tracked separately: payment webhooks (#300), channels multiselect (#302), master package protection (#303), payment gateway (#135).

Closing — core licensing system completed in #615-#631 (16 API endpoints, 5 model tables, admin UI, ed25519 signing). Remaining sub-features tracked separately: payment webhooks (#300), channels multiselect (#302), master package protection (#303), payment gateway (#135).
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 feature: wiki
Wiki system enhancements
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#296
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?