pipecat-base: allow executing bot() in a different process#64
Draft
aconchillo wants to merge 1 commit intomainfrom
Draft
pipecat-base: allow executing bot() in a different process#64aconchillo wants to merge 1 commit intomainfrom
aconchillo wants to merge 1 commit intomainfrom
Conversation
aconchillo
force-pushed
the
aleix/pipecat-cloud-spaw-process
branch
from
1a4e7b0 to
32d8f40
Compare
mattshep
reviewed
Sep 11, 2025
|
|
||
| image_version = environ.get("IMAGE_VERSION", "unknown") | ||
|
|
||
| spawn_process = environ.get("PIPECAT_CLOUD_SPAWN_PROCESS", False) |
Contributor
There was a problem hiding this comment.
I'd recommend dropping the first _ which would align it with the value we use to trigger integrated keys proxy... it feels more semantically correct to me since its not a "PIPECAT" thing its specifically a "PIPECATCLOUD" thing 🤷
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This allows users to completely isolate each call to
bot()in a separate process. By default, it's disabled. Note that this only applies to/bot, it does not apply to websockets.