Repository navigation
Conversation
…and mount activation
Try this branchThe engine and the scripts resolve independently, so this runs the changed export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/jmoredev/DevScripts/feat-gentle-shell
bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/gentle-shell.sh")"Both lines are needed. Without The same command works on an Incus host: the engine detects the platform and Useful while testing
export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/jmoredev/DevScripts/feat-gentle-shell
dev_mode=net,keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/gentle-shell.sh")"Against a core branch as wellAdd |
Proxmox script test@jmoredev ❌ 0/2 passed at
ARM64 (information only, not counted): 0/1 passed; failures there do not block this PR. ❌ ct/gentle-shell.sh (pve) — build log❌ ct/gentle-shell.sh (incus) — build log❌ ct/gentle-shell.sh (arm64) — build logFull logs: workflow run (artifacts |
There was a problem hiding this comment.
Proxmox script test failed at 354a8ce:
ct/gentle-shell.sh(pve): build exited 1: var_authorized_key must be a public key (contents of ~/.ssh/id_ed25519.pub), not a private key!ct/gentle-shell.sh(incus): build exited 1: var_authorized_key must be a public key (contents of ~/.ssh/id_ed25519.pub), not a private key!
Logs and details: test result. Push a fix, then ask for /test again.
|
Nah, i wont add that. Sorry but that scipt is so of Standards and dose so much work in the /ct part, that this is bound to break. If you can do it in the install script and only do the update in the /ct script we might take a second look. Also the whole storage selection part is just messy. Our scripts are here to get a "One-Click" installer feel for our users. This one needs so much setup work that we are for sure getting one issue after another. |
|
Fair points, thanks for the quick look. We'll rework it: the CT script goes back to the standard shape (defaults and update_script only), the SSH key setup moves into the install script, and the storage selection menus are dropped entirely (projects live in /root/projects, anyone wanting a host directory can add an mp0 bind mount from the Proxmox UI). Will push the rework to this branch for another lab run. |
✍️ Description
gentle-shell is a coding-agent workspace and TUI harness built for Pi (agent orchestration, ODD task tracking, Git diffs and persistent memory, driven from the terminal); this CT creates an LXC development server with Node 22, gentle-shell (npm
gentle-pi), git and the GitHub CLI preinstalled, meant to be driven remotely from the Gentle Shell desktop app via Herdr. It deviates from the standard pattern by being SSH-first: since the base template clears the root password, the install optionally acceptsvar_authorized_key(an SSH public key) and installs it as the root user's authorized key, leaving the container immediately connectable as a remote machine. Its prompts are gated to the PVE/Incus host so the in-container update path stays non-interactive, and the bundled Engram TUI is exposed on PATH. Steps from the upstream npm package (Node 22,npm install -g gentle-pi). Tested on a real Proxmox VE 9.2.26 host: interactive and unattended install, bind-mount projects mode, in-container update and a full Herdr remote session with remote login.AI-assisted (GLM-5.3 via the Gentle Shell / Pi harness, high reasoning) following
AGENTS.mdand the script-creator agent guidance, then reviewed and corrected against the project conventions.🔗 Related PR / Issue
Link: Refs #2687
✅ Prerequisites (X in brackets)
🧩 Script
Name: gentle-shell
Tool: AI coding-agent workspace and TUI harness for Pi: parallel coding agents, task tracking, Git diffs and persistent memory in one terminal. This CT provisions a ready-to-use LXC development server for it.
🗂️ Category (X in brackets)
ct/+install/)vm/)tools/addon/tools/pve/🖥️ Platform – tested on (X in brackets)
🏗️ Architecture (X in brackets)
🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.🔍 Code & Security Review (X in brackets)
CODE-AUDIT.md&CONTRIBUTING.mdguidelinesAppName.sh,AppName-install.sh,AppName.json)fetch_and_deploy_gh_release,fetch_and_deploy_codeberg_release,fetch_and_deploy_gl_release, orfetch_and_deploy_from_urlinstead ofgit pull.📋 Additional Information (optional)
The update path refreshes
gentle-pithrough npm (npm view gentle-pi version+npm install -g gentle-pi@<version>), which is upstream's own distribution channel. Testing feedback is collected in #2687 (var_testurlpoints there).📦 Application Requirements (for new scripts)
🌐 Source
npm install -g gentle-pi) and the repo's published releases.🤖 AI Assistance (X in brackets)
AGENTS.mdand.github/agents/pve-script-creator.agent.mdas guidance, and the output has been reviewed and corrected to match those guidelines.Please describe to which degree, if any, an LLM was used in creating this pull request.
GLM-5.3 (via the Gentle Shell / Pi coding-agent harness), high reasoning, used to draft and iterate
ct/gentle-shell.sh,install/gentle-shell-install.shandjson/gentle-shell.jsonagainstAGENTS.md, then manually reviewed and tested end-to-end on a real Proxmox VE 9.2.26 host (install, unattended install, update inside the container, SSH-key flow and a full Herdr remote session).