feat: Add more details/tips on Pycharm debugging and connecting to local Clickhouse. #10900
+43
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@sortafreel is attempting to deploy a commit to the PostHog Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pauldambra
reviewed
Mar 10, 2025
Comment on lines
+513
to
+526
| If you are using the `mprocs` approach to Posthog (`DEBUG=1 ./bin/start`) and want to debug backend service through PyCharm, you need to: | ||
|
|
||
| 1. Start containers through Docker (for example, using regular `docker compose -f docker-compose.dev.yml -v up`). | ||
| 2. Create a Pycharm configuration to start `uvicorn` manually (instead of the `mprocs` script). | ||
| - Select configurations in the top right corner > `Edit Configurations...`. | ||
| - Add new `Python` configuration (`+` button in the top left corner of the `Configurations` window). | ||
| - Set `module` (instead of `script`) to `uvicorn`. | ||
| - Set script parameters (should be identical to `mprocs` backend script parameters at `posthog/bin/start-backend`): | ||
| ``` | ||
| --reload posthog.asgi:application --host 0.0.0.0 --log-level debug --reload-include "posthog/" --reload-include "ee/" --reload-include "products/" | ||
| ``` | ||
| - Set the working directory to the `posthog` root. | ||
| - Add `DEBUG=1` to the configuration's environmental variables (if you want to replicate the default behavior), | ||
| 3. Start `posthog` through `DEBUG=1 ./bin/start`. |
There was a problem hiding this comment.
there should already be pycharm run configrations... 🤔
although i bet they don't use uvicorn
There was a problem hiding this comment.
What do you mean by "there should already be PyCharm run configurations"? 🤔
There was a problem hiding this comment.
TODO: Rework as a a Pycharm configuration (double-check if it's needed as existing Django config already exists).
There was a problem hiding this comment.
let's add this as a pycharm run configuration instead of as docs :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist
vercel.jsonArticle checklist