Super-Productivity

[push-app-to-main]

Name of the Script

Super-Productivity

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 not tested

📋 Script Details

Super Productivity is an advanced to-do list, time-tracking and project-management app. Self-hosted as the Angular web/PWA build served statically by nginx on :80 (built from source via npm run buildFrontend:prodWeb). Data is stored browser-side (IndexedDB) with optional WebDAV/Dropbox sync; no server backend or database.

---

Automated migration from ProxmoxVED (community-scripts/ProxmoxVED#2095).

[github-actions]

Try this branch

The engine and the scripts resolve independently, so this runs the changed
ct/ and install/ scripts against the production engine:

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/community-scripts/ProxmoxVE/add-script-super-productivity-1788042906
bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/super-productivity.sh")"

Both lines are needed. Each script pins _CS_DEFAULT_URL to main, and that
pin is what fills COMMUNITY_SCRIPTS_URL when the variable is unset — so
curling the branch URL on its own gives you the ct/ script from this PR and
the install/ script from main. Frequently the one you meant to test.

The same command works on an Incus host: the engine detects the platform and
loads the matching backend, while the scripts still come from this branch.

Useful while testing

dev_mode=net logs every fetch with status and URL, which is the quickest way
to confirm the branch is really being used. dev_mode=keep stops a failed
build from deleting the container along with the evidence.

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/community-scripts/ProxmoxVE/add-script-super-productivity-1788042906
dev_mode=net,keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/super-productivity.sh")"