[Script request]: Initiative native server (adoption exception request)

[Dunky13]

Application Name

Initiative, native server package.

Official Website

https://beyonders-studio.github.io/initiative/

Source Repository

https://github.com/beyonders-studio/initiative (AGPL-3.0)

Repository Stars and Minimum Adoption Requirement

191 GitHub stars, verified on 2026-10-30.

• The official source repository has at least 1,000 stars.

This is an explicit exception request. The current discussion form requires 1,000 stars and the DevScripts PR template requires 600. Initiative meets neither threshold. I have not found a verifiable public adoption metric that substitutes for those requirements. Successful testing of one homelab installation does not establish broad adoption.

The repository was created on 2025-11-22, so it is over six months old. Its latest release is v0.77.1, published 2026-10-24, with recent upstream commits and official native server packages and checksums for amd64 and arm64.

Description

Initiative is a self-hosted shared workspace for communities, households and teams, with projects, tasks, documents, calendars and dashboards. It offers live document collaboration and configurable permissions.

Why should this be considered despite the star count?

• It fits the existing LXC use case: a persistent, self-hosted collaboration service with a browser interface.
• The new official initiative-server packages bundle the backend, browser app and editor dependencies. The installer uses those artifacts directly, rather than building the app or using Docker. This reduces the integration work, although the young package path still needs broader testing.
• There is a working candidate and concrete testing evidence: a real amd64 Proxmox installation and a 0.76.0 to 0.77.1 package upgrade, plus a separate native Debian 13 arm64 guest exercise. A readiness false failure found during that upgrade is now covered by regression cases.
• The candidate includes checksum and package-identity verification, generated secrets, an unprivileged container, loopback-only backend behind HTTPS, and an offline PostgreSQL backup before updates. It follows the shared framework helpers.

These are reasons to consider a limited DevScripts trial, not a claim that technical quality replaces the adoption policy. Please decide whether an exception is appropriate or whether the request should wait for more adoption. I understand it may be declined under the current rules.

Installation Notes

Debian 13 unprivileged LXC; defaults: 2 cores, 2 GiB RAM, 8 GiB disk. PostgreSQL 17, package-owned non-root initiative-server.service, nginx HTTPS on port 443, HTTP redirect on port 80, backend on 127.0.0.1:8173. The self-signed certificate must be accepted or replaced. The first account becomes owner; subsequent public registration is disabled. Claim that account immediately on a private network.

Updates preserve /etc/initiative and /var/lib/initiative, stop PostgreSQL for a private backup of the local cluster/configuration, install the verified server package, reload systemd, then require healthy database checks. Optional readiness degradation is reported as a warning. External storage/databases need separately arranged backups; database migrations require restoring a matching backup for rollback.

The full corrected updater, browser flows, reboot persistence and real data preservation still need fresh Proxmox acceptance. Native arm64 guest testing does not establish arm64 Proxmox LXC coverage. Incus has not been tested or claimed.

Contribution and feedback

Draft implementation PR: community-scripts/DevScripts#2484

Testing tracker: community-scripts/DevScripts#2483

The PR targets DevScripts main, as required for new scripts, rather than submitting directly against ProxmoxVE. It links back to this discussion. Candidate: 046900c6b28f0602f712215a465d3d71bb7a6097, one signed, DCO-signed-off feature commit rebased onto upstream main (acbbae06cf9e7d135fa48e58f516f71c96f5c3ab). Initial testing history: personal acceptance issue.

Hosted CI has now passed all 35 Initiative regressions. The PR remains draft: its adoption check flags the unmet 600-star requirement, and an unrelated pre-existing ct/jumpserver.sh base check also fails. These are recorded in the PR/testing tracker; no exception is presumed.

The PR leaves its 600-star checkbox unchecked. I expect the eligibility automation to flag it; I am not asking to bypass that check or claiming an approved exception. The supplemental regression harness, CI step and operator guide also go beyond the agent template's three-file output and are disclosed for review. No HTML report is included.

@jordandrako @LeeJMorel, tagging you as Initiative's published code owners for feedback on the native-package integration, bootstrap requirements and maintenance expectations. This proposal is independent; your endorsement or commitment to maintain a Community Script is not assumed.

AI disclosure: OpenAI gpt-6.1-sol with xhigh reasoning was used substantially for implementation, investigation, tests and submission text, with independent same-provider Standards and Spec reviews. The operator supplied the real Proxmox testing evidence.

Due Diligence

• I have searched existing scripts and found no duplicate.
• I have searched existing discussions and found no duplicate request.
• The application has an official public source repository.
• The application is self-hosted and suitable for Proxmox VE Helper-Scripts.
• The application appears to be actively maintained and provides official releases, tags, or release tarballs.
• I understand that requests outside the project scope may be closed without an extensive explanation.