From 496bf38236dd8c1aca20fadae7d2f987eaf1363c Mon Sep 17 00:00:00 2001 From: Yoko Li Date: Sun, 2 Jul 2023 22:11:52 -0700 Subject: [PATCH 1/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9f2ad05..1496419 100644 --- a/README.md +++ b/README.md @@ -293,7 +293,7 @@ If you have tried out the Quickstart above, you probably know that we have only To get started, run the following command: -`bash +` npm run export-to-character [COMPANION_NAME] [MODEL_NAME] [USER_ID] ` From 5d70483a76338a8dfd0c5d9bef1ac5f581baa0bf Mon Sep 17 00:00:00 2001 From: Yoko Li Date: Sun, 2 Jul 2023 22:15:51 -0700 Subject: [PATCH 2/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1496419..2de55ba 100644 --- a/README.md +++ b/README.md @@ -218,7 +218,7 @@ h. Now you can text the Twilio phone number from your phone and get a response f - **If you are using Github Codespaces**: You will need to [install flyctl](https://fly.io/docs/hands-on/install-flyctl/) and authenticate from your codespaces cli by running `fly auth login`. - Run `fly launch` under project root -- this will generate a `fly.toml` that includes all the configurations you will need - Run `fly deploy --ha=false` to deploy the app -- the -ha flag makes sure fly only spins up one instance, which is included in the free plan. You also want to run `fly scale memory 512` to scale up the fly vm memory for this app. -- For any other non-localhost environment, the existing Clerk development instance should continue to work. You can upload the secrets to Fly by running `cat .env.local | fly secrets import` +- For any other non-localhost environment, the existing Clerk development instance should continue to work. You should upload the secrets to Fly by running `cat .env.local | fly secrets import` - If you are ready to deploy to production, you should create a prod environment under the [current Clerk instance](https://dashboard.clerk.com/). For more details on deploying a production app with Clerk, check out their documentation [here](https://clerk.com/docs/deployments/overview). **Note that you will likely need to manage your own domain and do domain verification as part of the process.** - Create a new file `.env.prod` locally and fill in all the production-environment secrets. Remember to update `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` by copying secrets from Clerk's production instance -`cat .env.prod | fly secrets import` to upload secrets From ac24fc1d5677997d00f53bdb08a65712b5b765e9 Mon Sep 17 00:00:00 2001 From: Yoko Li Date: Sun, 2 Jul 2023 22:17:34 -0700 Subject: [PATCH 3/3] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2de55ba..7c1ac04 100644 --- a/README.md +++ b/README.md @@ -218,7 +218,7 @@ h. Now you can text the Twilio phone number from your phone and get a response f - **If you are using Github Codespaces**: You will need to [install flyctl](https://fly.io/docs/hands-on/install-flyctl/) and authenticate from your codespaces cli by running `fly auth login`. - Run `fly launch` under project root -- this will generate a `fly.toml` that includes all the configurations you will need - Run `fly deploy --ha=false` to deploy the app -- the -ha flag makes sure fly only spins up one instance, which is included in the free plan. You also want to run `fly scale memory 512` to scale up the fly vm memory for this app. -- For any other non-localhost environment, the existing Clerk development instance should continue to work. You should upload the secrets to Fly by running `cat .env.local | fly secrets import` +- For any other non-localhost environment, the existing Clerk development instance should continue to work. You will need to upload the secrets to Fly by running `cat .env.local | fly secrets import` - If you are ready to deploy to production, you should create a prod environment under the [current Clerk instance](https://dashboard.clerk.com/). For more details on deploying a production app with Clerk, check out their documentation [here](https://clerk.com/docs/deployments/overview). **Note that you will likely need to manage your own domain and do domain verification as part of the process.** - Create a new file `.env.prod` locally and fill in all the production-environment secrets. Remember to update `NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` by copying secrets from Clerk's production instance -`cat .env.prod | fly secrets import` to upload secrets