Community Scripts documentation
Current documentation for applications, Core, Proxmox VE, and Incus.
Community Scripts separates application scripts from their shared engine. Core is the engine; ProxmoxVE, DevScripts, and Incus supply application and platform-specific content.
Start here
| If you want to… | Read |
|---|---|
| Understand the repositories and execution path | Architecture |
| Use or troubleshoot a container script | Guides and Dev mode |
| Run scripts on an Incus host | Incus host guide |
| Write a CT/install pair | CT scripts and Installation scripts |
| Work with a VM script | Virtual machine scripts |
| Look up a helper function | Function reference |
| Run a host tool or an add-on | Tools |
| Set every option without the menu | Configuration reference |
| Contribute an application or Core change | Contributing |
Current structure
| Repository | Scope |
|---|---|
| Core | Shared loading, runtime, UI, container bootstrap, helpers, backends, telemetry |
| ProxmoxVE | Canonical application scripts and Proxmox VE-specific tools/VMs |
| DevScripts | New applications before promotion |
| Incus | Mirrored CT/install scripts, Incus VMs, host tooling, and Incus-only metadata |
The Core engine reference documents the loader boundaries, and the function reference documents every helper a script can call. Core's CI-checked API.txt inventories remain the authority when a page and the code disagree.