WIP: Fly server #100
Closed
WIP: Fly server #100
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
|
This one is obsolete, closing. We have a working fly.io example here https://github.com/pipecat-ai/pipecat/tree/main/examples/deployment/flyio-example |
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.
This adds another example server (
fly-server.py) that uses fly.io's API to spin up a new Fly Machine for every new bot, instead of using a python subprocess in the web server itself. This will allow us to use Fly's new beefier GPU instances if we want to run local models in the cloud.I'm putting this here now so I can hopefully remember to come back around to it before or after the hackathon. :)