From 9f07c3ca273f2f378edd48ab9e47dab896c3c842 Mon Sep 17 00:00:00 2001 From: Lewis Wolfgang Date: Mon, 5 Aug 2024 10:12:35 -0400 Subject: [PATCH] Fly.io example: remove step to cache silero models. No longer necessary. --- examples/deployment/flyio-example/Dockerfile | 3 --- examples/deployment/flyio-example/README.md | 6 +----- examples/deployment/flyio-example/install_deps.py | 4 ---- 3 files changed, 1 insertion(+), 12 deletions(-) delete mode 100644 examples/deployment/flyio-example/install_deps.py diff --git a/examples/deployment/flyio-example/Dockerfile b/examples/deployment/flyio-example/Dockerfile index 2e1b9bad9..b2cc45701 100644 --- a/examples/deployment/flyio-example/Dockerfile +++ b/examples/deployment/flyio-example/Dockerfile @@ -9,8 +9,5 @@ COPY *.py . COPY ./requirements.txt requirements.txt RUN pip3 install --no-cache-dir --upgrade -r requirements.txt -# Install models -RUN python3 install_deps.py - # Start the FastAPI server CMD python3 bot_runner.py --port ${FAST_API_PORT} \ No newline at end of file diff --git a/examples/deployment/flyio-example/README.md b/examples/deployment/flyio-example/README.md index 709bcc63b..689ef11fc 100644 --- a/examples/deployment/flyio-example/README.md +++ b/examples/deployment/flyio-example/README.md @@ -2,8 +2,6 @@ This project modifies the `bot_runner.py` server to launch a new machine for each user session. This is a recommended approach for production vs. running shell processess as your deployment will quickly run out of system resources under load. -To speed up machine boot times, we also download and cache Silero VAD as part of the Dockerfile (`install_deps.py`). If you are using other custom models, you can add them here too. - For this example, we are using Daily as a WebRTC transport and provisioning a new room and token for each session. You can use another transport, such as WebSockets, by modifying the `bot.py` and `bot_runner.py` files accordingly. ## Setting up your fly.io deployment @@ -14,7 +12,7 @@ You can copy the `example-fly.toml` as a reference. Be sure to change the app na ### Create your .env file -Copy the base `env.example` to `.env` and enter the necessary API keys. +Copy the base `env.example` to `.env` and enter the necessary API keys. `FLY_APP_NAME` should match that in the `fly.toml` file. @@ -32,7 +30,6 @@ Note: you can do this manually via the fly.io dashboard under the "secrets" sub- `fly deploy` - ## Connecting to your bot Send a post request to your running fly.io instance: @@ -40,4 +37,3 @@ Send a post request to your running fly.io instance: `curl --location --request POST 'https://YOUR_FLY_APP_NAME/start_bot'` This request will wait until the machine enters into a `starting` state, before returning the a room URL and token to join. - diff --git a/examples/deployment/flyio-example/install_deps.py b/examples/deployment/flyio-example/install_deps.py deleted file mode 100644 index 30396bba3..000000000 --- a/examples/deployment/flyio-example/install_deps.py +++ /dev/null @@ -1,4 +0,0 @@ -import torch - -# Download (cache) the Silero VAD model -torch.hub.load(repo_or_dir='snakers4/silero-vad', model='silero_vad', force_reload=True)