MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 128 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

feat: release license key generation and management #134

New Issue
Open
opened 2026-05-21 21:52:41 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-21 21:52:41 +00:00
Owner
Copy Link
Copy Source

Native license key generation for releases.

Native license key generation for releases.
jmiller commented 2026-05-21 21:53:49 +00:00
Author
Owner
Copy Link
Copy Source

Full Requirements

License Key Generation

  • Generate unique keys per release download
  • Tie keys to user accounts, organizations, or email
  • Key types: trial, standard, professional, enterprise
  • Configurable expiration, revocable

Key Formats

  • Alphanumeric: XXXX-XXXX-XXXX-XXXX
  • Signed JWT tokens for offline validation
  • Hardware-bound keys (optional)

Management

  • Admin UI: generate, list, revoke, extend per release
  • Per-repo license settings
  • Activation tracking + audit log

API Endpoints

  • POST /repos/{owner}/{repo}/releases/{id}/licenses - generate
  • GET /repos/{owner}/{repo}/releases/{id}/licenses - list
  • POST /repos/{owner}/{repo}/licenses/validate - validate
  • DELETE /repos/{owner}/{repo}/licenses/{key} - revoke

Integration

  • Release downloads can require valid key
  • Webhook + ntfy on key events
  • Badge: active licenses count

Database

  • repo_license_config table
  • release_license_key table

Authored-by: Claude Opus 4.6 (1M context)

## Full Requirements ### License Key Generation - Generate unique keys per release download - Tie keys to user accounts, organizations, or email - Key types: trial, standard, professional, enterprise - Configurable expiration, revocable ### Key Formats - Alphanumeric: XXXX-XXXX-XXXX-XXXX - Signed JWT tokens for offline validation - Hardware-bound keys (optional) ### Management - Admin UI: generate, list, revoke, extend per release - Per-repo license settings - Activation tracking + audit log ### API Endpoints - POST /repos/{owner}/{repo}/releases/{id}/licenses - generate - GET /repos/{owner}/{repo}/releases/{id}/licenses - list - POST /repos/{owner}/{repo}/licenses/validate - validate - DELETE /repos/{owner}/{repo}/licenses/{key} - revoke ### Integration - Release downloads can require valid key - Webhook + ntfy on key events - Badge: active licenses count ### Database - repo_license_config table - release_license_key table *Authored-by: Claude Opus 4.6 (1M context)*
jmiller added the pending: design label 2026-05-22 02:01:08 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 pending: testing
Feature implemented but not yet tested with documented proof
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 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
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: bug
type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 upstream
work-in-progress
Draft or incomplete work
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 pending: design
Milestone
No items
No Milestone
Projects
Clear projects
No projects
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/MokoGitea#134
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?