Replies: 1 comment 1 reply
-
Hello, For debugging with VSCode I am doing the following:
{
"name": "Existing Dockerfile",
"build": {
// Sets the run context to one level up instead of the .devcontainer folder.
"context": "..",
// Update the 'dockerFile' property if you aren't using the standard 'Dockerfile' filename.
"dockerfile": "../Dockerfile" // this is the Dockerfile in the pipelines repository.
},
"features": {
"ghcr.io/devcontainers-contrib/features/ruff:1": {}
},
"runArgs": ["--network", "host"]
}
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Python Debugger: FastAPI",
"type": "debugpy",
"request": "launch",
"module": "uvicorn",
"args": [
"main:app",
"--reload",
"--port", "9099",
"--host", "0.0.0.0"
],
"env": {
//your env variables if you have. These env variables will go into valves.
},
"jinja": true
}
]
}
I believe it is not the optimal way, but I can not think of anything else, hope it helps! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am setting up a WebUI, Pipelines, LiteLLM-Proxy, Database combination. The base setup is there and now I want to add my pipelines.
Locally for debugging I setup most using docker-compose and I was wondering how you guys use debuggers like VSCode to see what's going on in you custom code?
I was experimenting with a git clone of the repository but that didn't quite work because of the way the pipelines are inserted within the pipe directory.
How are you dealing with it? print debugging when mounting it directly into the console?
Beta Was this translation helpful? Give feedback.
All reactions