kanshan/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-02-11 05:24:39 +08:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity
91e23027f1
dify/.vscode
History
hj24 00af19c7f2
Some checks failed
Build and Push API & Web / build (api, DIFY_API_IMAGE_NAME, linux/amd64, build-api-amd64) (push) Has been cancelled
Details
Build and Push API & Web / build (api, DIFY_API_IMAGE_NAME, linux/arm64, build-api-arm64) (push) Has been cancelled
Details
Build and Push API & Web / build (web, DIFY_WEB_IMAGE_NAME, linux/amd64, build-web-amd64) (push) Has been cancelled
Details
Build and Push API & Web / build (web, DIFY_WEB_IMAGE_NAME, linux/arm64, build-web-arm64) (push) Has been cancelled
Details
Build and Push API & Web / create-manifest (api, DIFY_API_IMAGE_NAME, merge-api-images) (push) Has been cancelled
Details
Build and Push API & Web / create-manifest (web, DIFY_WEB_IMAGE_NAME, merge-web-images) (push) Has been cancelled
Details
feat: sandbox retention basic settings
2025-12-18 14:19:33 +08:00
..
launch.json.template feat: sandbox retention basic settings 2025-12-18 14:19:33 +08:00
README.md docs: format all md files (#24195) 2025-08-20 13:49:11 +08:00

README.md

Debugging with VS Code

This launch.json.template file provides various debug configurations for the Dify project within VS Code / Cursor. To use these configurations, you should copy the contents of this file into a new file named launch.json in the same .vscode directory.

How to Use

  1. Create launch.json: If you don't have one, create a file named launch.json inside the .vscode directory.
  2. Copy Content: Copy the entire content from launch.json.template into your newly created launch.json file.
  3. Select Debug Configuration: Go to the Run and Debug view in VS Code / Cursor (Ctrl+Shift+D or Cmd+Shift+D).
  4. Start Debugging: Select the desired configuration from the dropdown menu and click the green play button.

Tips

  • If you need to debug with Edge browser instead of Chrome, modify the serverReadyAction configuration in the "Next.js: debug full stack" section, change "debugWithChrome" to "debugWithEdge" to use Microsoft Edge for debugging.