Archived
feat: target settings to selected machine
This commit is contained in:
+17
-12
@@ -153,12 +153,14 @@
|
||||
</p>
|
||||
<p>
|
||||
Use <strong>Settings → PI WEB plugins</strong> to enable or disable discovered PI WEB browser plugins
|
||||
before the browser imports them. This plugin enablement surface is for the PI WEB gateway you opened; to
|
||||
change remote plugin enablement, open that remote machine directly or edit its PI WEB config on that
|
||||
machine. After installing, removing, or updating a Pi package, type <code>/reload</code> in each idle
|
||||
PI WEB session on the target machine to refresh Pi runtime resources such as extensions, skills, prompt
|
||||
templates, themes, and context/system prompt files as supported by Pi. Reload the browser page separately
|
||||
for newly discovered or changed PI WEB browser plugins. A routine session daemon restart is not required.
|
||||
before the browser imports them. In a federated setup, this plugin enablement surface targets the
|
||||
currently selected machine and labels where changes are saved. If an older or unavailable remote PI WEB
|
||||
server does not advertise selected-machine settings support, PI WEB reports the plugin settings as
|
||||
unsupported or unavailable instead of silently falling back to the gateway. After installing, removing, or
|
||||
updating a Pi package, type <code>/reload</code> in each idle PI WEB session on the target machine to
|
||||
refresh Pi runtime resources such as extensions, skills, prompt templates, themes, and context/system
|
||||
prompt files as supported by Pi. Reload the browser page separately for newly discovered or changed
|
||||
PI WEB browser plugins. A routine session daemon restart is not required.
|
||||
</p>
|
||||
</section>
|
||||
|
||||
@@ -325,15 +327,17 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
<h2>Manage PI WEB plugins</h2>
|
||||
<p>
|
||||
Open <strong>Settings → PI WEB plugins</strong> to review discovered bundled, local, dev, and Pi package
|
||||
plugins for the PI WEB gateway you opened. PI WEB can disable any discovered plugin before the browser
|
||||
imports it. Core app contributions such as the command palette, base workspace tools, and themes are not
|
||||
managed through this plugin list.
|
||||
plugins for the selected PI WEB machine. When the local machine is selected, this is the gateway plugin
|
||||
list; when a remote machine is selected, the list comes from that remote PI WEB server and includes
|
||||
disabled discovered plugins it exposes. PI WEB can disable any discovered selected-machine plugin before
|
||||
the browser imports it. Core app contributions such as the command palette, base workspace tools, and
|
||||
themes are not managed through this plugin list.
|
||||
</p>
|
||||
<p>
|
||||
This surface is only for PI WEB plugin enablement. To install, remove, or update Pi packages that may
|
||||
provide plugins or other Pi resources, use <strong>Settings → Pi packages</strong>. In a federated setup,
|
||||
the Pi packages panel targets the selected machine; the PI WEB plugins panel still controls gateway plugin
|
||||
enablement.
|
||||
both the Pi packages panel and the PI WEB plugins panel target the selected machine; plugin enablement
|
||||
still writes the PI WEB <code>plugins</code> config key rather than changing Pi package-manager settings.
|
||||
</p>
|
||||
<div class="code-card">
|
||||
<div class="copy-row">
|
||||
@@ -379,7 +383,8 @@ After editing, check the manifest endpoint and browser-console failure cases.</c
|
||||
</ul>
|
||||
<p>
|
||||
Remote plugin enablement is controlled by the remote machine's PI WEB plugin config. To edit or disable
|
||||
one, open that machine directly or update its config file.
|
||||
one, select that machine and use <strong>Settings → PI WEB plugins</strong> when the remote server exposes
|
||||
selected-machine settings, or open that machine directly/update its config file.
|
||||
</p>
|
||||
<p>
|
||||
Plugin package metadata can set <code>machineSpecific: true</code>. Use it for plugins like Updates whose
|
||||
|
||||
Reference in New Issue
Block a user