initiative.sh #2483

Name of the Script

Initiative (initiative.sh)

Script Type

CT (LXC Container)

Script path

ct/initiative.sh, install/initiative-install.sh, json/initiative.json

Where does it run?

Proxmox VE, unprivileged Debian 13 LXC. Incus is untested.

Does this script support arm64?

arm64 supported by the official package and tested in a native Debian 13 arm64 VM with real services/core helpers; arm64 Proxmox LXC provisioning has not been tested. The host wizard/provisioning steps were mocked in that guest test.

Tested on

• Proxmox VE (amd64, operator-reported installation and package upgrade)
• Incus

📋 Script Details

Testing tracker for the Initiative native-server installer. Draft implementation PR: #2484

Adoption exception discussion: community-scripts/ProxmoxVE#18319

Candidate: 046900c6b28f0602f712215a465d3d71bb7a6097, based on upstream main (acbbae06cf9e7d135fa48e58f516f71c96f5c3ab). Eligibility exception pending: 191 stars as of 2026-10-30, below DevScripts' 600-star and ProxmoxVE's 1,000-star script-request thresholds. Neither requirement is claimed to be met.

The installer verifies the official server .deb and architecture-specific checksum, configures PostgreSQL 17 and nginx HTTPS, and creates generated secrets. Updates make a private offline backup of the default local data/config paths before installing and migrating. See the operator guide.

Testing from the Proxmox host shell:

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Dunky13/ProxmoxVED/refs/heads/feat/initiative
dev_mode=keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/initiative.sh")"

Retain the export so the framework uses the fork's matching install script. Test on a disposable container and private network; claim the first owner account immediately. Do not include credentials or server.env in feedback. Container resources and networking use the standard wizard defaults; no personal MAC, VLAN or address is embedded.

Evidence already available:

• Real amd64 Proxmox installation of v0.76.0 and package upgrade to v0.77.1, followed by independently verified HTTPS version/readiness. The old updater falsely rejected a valid degraded response with only notify_bus:error.
• The corrected readiness predicate accepts that exact response with a warning while requiring all three database checks; regression cases cover transport/JSON/database failures and systemd reload ordering.
• Separate Debian 13 arm64 VM: real package/services, first-owner/login/closed second registration, project/task creation, same-release updater exercise with an older version marker, offline backup, unchanged config/upload hashes, preserved login/task, current-version no-op. This does not establish arm64 LXC coverage.
• 35 rootless/offline regression cases, Bash syntax, ShellCheck, JSON validation and actionlint. CI wiring is included in the contribution.

Remaining acceptance:

• Fresh real Proxmox creation using the current corrected branch.
• Browser first-owner/login, task, file upload and live editor flows; second public registration rejected.
• Reboot with task/upload/login persistence.
• Corrected updater on a real published-version upgrade, verifying real user data/config/upload preservation and backup recovery planning.
• Current-version update after version-marker recovery does not restart services.
• arm64 Proxmox LXC coverage, if available.

Historical observations and readiness response: personal acceptance issue. This tracker collects upstream testing; it is not approval or production promotion.

Published CI status for 046900c6b28f0602f712215a465d3d71bb7a6097

• Bash Syntax Check passed: syntax checked 236 scripts and all 35 Initiative regression scenarios passed in hosted CI. VM metadata also passed.
• PR requirements check failed for exactly one missing requirement: 600+ GitHub stars. This is the disclosed exception request. The bot applied requirements missing and stale; without maintainer action, its comment warns of closure after seven days. No bypass label was applied by the author.
• ct scripts base failed because existing upstream ct/jumpserver.sh lacks _CS_DEFAULT_URL. Initiative's script has the required line. The same upstream workflow already failed on main's Jumpserver merge. This unrelated script is not modified here; its repair remains a separate maintainer follow-up.
• No maintainer approval or exception has been granted. Runtime acceptance gaps remain as listed above. This draft is not ready to merge.
• Optional Jev advisory (jev-1.14.0): readiness 0.01 on its 0–3 scale, 99% probability of blocked, confidence 99%; description-match 0.73 and untested-logic 0.43. It did not identify a source-verified additional finding. Highest estimated risk was durable data/migrations, already covered by the backup/rollback limitations. This advisory is separate from code review and CI.

Follow-up ownership: Community Scripts maintainers decide the adoption exception and the unrelated Jumpserver base repair. The operator/test volunteers can complete the unchecked runtime acceptance items on a disposable instance using the command above; report version, architecture, host/container outcome and sanitized readiness/service output here.