Jugg Backend
Jugg can connect to an HTTP backend for plugin updates, hot updates, project defaults, diagnostics, and optional remote server provisioning. The backend is not required for local compile, deploy, CLI, or MCP usage.
These pages are for teams that want to self-host the backend surface. They describe the user-visible capabilities and integration boundaries, not server internals.
Capabilities
| Capability | Purpose | Required when self-hosting |
|---|---|---|
| Update check | Tell the plugin whether a full plugin package is available and optionally show a notification | Recommended |
| Project configuration | Return project-specific server rules, compile rules, module settings, and custom compilers | As needed |
| Event reporting | Store compile, deploy, update check, and other action results | Optional |
| Issue log upload | Receive zipped Jugg logs when users submit issues | Recommended |
| Hot update | Deliver jar-level plugin updates with md5 checks | Optional |
| Custom compiler delivery | Host team-specific custom compiler jars | As needed |
| Remote server apply | Guide users through remote build machine provisioning from the IDE | Optional, usually platform-specific |