Repository navigation
Fix #843: Document which environment variables a Tesseract can see, per launch path - #934
Vedant-200 wants to merge 4 commits into
Conversation
Applied by the DevPilot agent from the reviewed run diff.
Applied by the DevPilot agent from the reviewed run diff.
CLA signatures requiredThank you for your PR, we really appreciate it! Like many open-source projects, we ask that all contributors sign our Contributor License Agreement before we can accept your contribution. This only needs to be done once per contributor. You can do so by commenting the following on this pull request: @PasteurBot I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
|
Pushed a follow-up commit for this: |
|
I looked at this one and could not apply it automatically (no file could be patched safely), so I've left it unchanged rather than push a change I can't stand behind. I'll rework it against the file you named ( |
|
@Vedant-200 Please accept our CLA (see bot comment above). Happy to have a look once that's done. |
|
Understood — the CLA needs to be signed on my account before this can pass. I've noted it so future PRs to this repo carry it from the start. |
|
This doesn't seem to be going anywhere. Bad bot. |
Summary
Document environment visibility per Tesseract launch path in the debugging guide and add a deploy-time note warning that containers do not inherit the host environment.
Fixes #843
🤖 Generated by the DevPilot agent — please review before merging.