Skip to content

Upload Plugins ​

Learn how to package and publish your plugins to the Motanamy marketplace.

Quick Upload Process ​

1. Build Your Plugin ​

bash
mot build

2. Test Locally ​

bash
mot run

3. Upload to Store ​

bash
mot upload

Package Requirements ​

Your plugin package must include:

  • setting.json - Plugin manifest with metadata and configuration
  • main.js - Main backend logic file
  • script.js - Frontend script file
  • README-AR.md & README-EN.md - Documentation in Arabic and English
  • Version folder structure (e.g., 1.0.0/) with all necessary files

setting.json (Manifest) ​

json
{
  "versionNumber": "0",           // Version counter (increments with updates)
  "version": "1.0.0",             // Semantic version string
  "name": "my-plugin",            // Plugin/app name
  "init": true,                   // Whether plugin is initialized
  "user": 1,                      // User ID who owns/created the plugin
  "type": "EA",                   // Platform type: EA (Enterprise), SA (Standalone), OS (Operating System)
  "main": "main.js",              // Main entry point file (EA only)
  "assets": "assets",             // Assets directory path
  "script": "script.js",          // Frontend script file
  "packages": [                   // npm deps your main.js needs (EA only)
    { "name": "nodemailer", "version": "6.9.2" }
  ],
  "id": "unique-plugin-id"        // Unique plugin identifier
}

Upload Options ​

Public Marketplace ​

  • Available to all Motanamy users
  • Requires review process
  • Supports monetization
  • Listed in Motanamy Store

Private Repositories ​

  • Share with specific teams or organizations
  • No public review required
  • Enterprise deployment options
  • Controlled distribution

Review Process ​

Submission Steps ​

  1. Prepare Package: Ensure all required files are present
  2. Run Tests: Verify plugin works on target platform
  3. Submit: Use mot upload command
  4. Wait for Review: Our team reviews within 2-3 business days

Review Criteria ​

  • Security: No malicious code or vulnerabilities
  • Compatibility: Works on specified platform(s)
  • Quality: Well-documented and tested
  • Compliance: Follows Motanamy guidelines

Best Practices ​

  • Test thoroughly on all target platforms before uploading
  • Include comprehensive documentation in both Arabic and English
  • Use only necessary permissions in your manifest
  • Keep package size reasonable (< 50MB recommended)
  • Follow semantic versioning for updates
  • Provide clear change logs for new versions

Troubleshooting ​

Common Issues ​

  • Upload fails: Check setting.json syntax and required fields
  • Build errors: Ensure all dependencies are properly configured
  • Review rejected: Address security or compatibility issues
  • Plugin not working: Test on correct platform type (EA/SA/OS)

Error Messages ​

  • "Invalid manifest": Check setting.json structure and required fields
  • "Permission denied": Verify your developer account and upload permissions
  • "Platform mismatch": Ensure plugin type matches target platform

Get Help ​