fix: address Copilot follow-up comments on develop-plugin docs

This commit is contained in:
RiskeyL
2026-05-19 20:15:28 +08:00
parent 30b5781da9
commit 7bdfeb6a99
3 changed files with 3 additions and 3 deletions
@@ -1,6 +1,6 @@
---
title: Plugin Logging
description: Emit log lines from inside a plugin using the SDK plugin_logger_handler, visible during remote debug and persisted to daemon container logs
description: Emit log lines from inside a plugin using the SDK plugin_logger_handler, visible during remote debugging and persisted to daemon container logs
---
As a plugin developer, you may want to print arbitrary strings to logs during plugin processing for development or debugging purposes.
+1 -1
View File
@@ -41,7 +41,7 @@ No. Plugins run inside a managed Python 3.12 environment. Pin your dependencies
## Remote debugging
### The plugin starts but never appears in the workspace.
### Why does my plugin start but never appear in the workspace?
Three things to check, in order: (1) the daemon log shows an incoming registration, (2) the `REMOTE_INSTALL_KEY` matches what's shown in the debug dialog, (3) `REMOTE_INSTALL_URL` uses the `host:port` format (not separate variables). See [Plugin Debugging](/en/develop-plugin/features-and-specs/plugin-types/remote-debug-a-plugin) for the full troubleshooting list.
@@ -7,7 +7,7 @@ dimensions:
standard_title: Third-Party Signature Verification
language: en
title: Sign Plugins for Third-Party Signature Verification
description: Enable signed `.difypkg` installation in Dify Community Edition without disabling signature verification entirely. Generate keys, sign packages, distribute the public key
description: Enable signed `.difypkg` installation in Dify Community Edition without disabling signature verification entirely (generate keys, sign packages, distribute the public key)
---
<Warning>