The App Store

The App Store is a catalog of community-scripts LXC installers, kept in sync with the upstream community-scripts project.

Keeping the catalog current

Each catalog refresh makes exactly one call to resolve the upstream repository’s current commit, then fetches every catalog entry’s container and install scripts from that specific commit, never from the moving default branch. That pin means an install always runs the exact script Proxploy classified and showed you, not whatever the upstream project has since changed to. A refresh that finds the same commit as last time skips re-fetching entirely.

Installable vs. unsupported

Not every community-scripts installer can run unattended, and Proxploy tells you which ones can before you try. Each script is parsed for interactive prompts (a bare input read, or a dialog/whiptail call, that isn’t guarded by an environment-variable default or a fallback), because an unguarded prompt blocks forever on a non-interactive install and aborts it partway through. A script with an unguarded prompt is marked unsupported rather than left to fail on your node. Scripts that build more than one container, or don’t follow the standard single-container build pattern, are marked unsupported too.

When the catalog is stale

The Store page shows a banner when its catalog cache is out of date, a catalog that has never synced counts as stale too. Staleness is a real signal, not decoration: catalog refreshes run on a schedule, so a stale banner means that schedule has stopped or is failing, and every install you make while it’s showing is pinned against scripts upstream may have already moved past.

Installing

Installing an app needs two things: your explicit consent (a checkbox, not an assumption), and a host that already has SSH authorized (see SSH key enrollment). Without both, the install can’t be submitted. Once you confirm, Proxploy runs the pinned install script on the node over SSH, streaming its output into the job log in real time so you watch it happen rather than waiting for a pass/fail at the end.

What Proxploy checks, and what it doesn’t

The App Store tells you whether a script can run unattended; it doesn’t vet what the script actually does once it runs. See the trust model for what that means in practice: an install runs with the same root access you’d have running the script yourself.