Continues from last commit

HumeAI · May 23, 2024 · c471d5d · c471d5d
1 parent 57e1333
commit c471d5d
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 2 deletions.
diff --git a/evi-typescript-example/.env.example b/evi-typescript-example/.env.example
@@ -0,0 +1,2 @@
+VITE_HUME_API_KEY="YOUR_API_KEY"
+VITE_HUME_CLIENT_SECRET="YOUR_CLIENT_SECRET"
diff --git a/evi-typescript-example/.gitignore b/evi-typescript-example/.gitignore
@@ -23,4 +23,5 @@ dist-ssr
 *.sln
 *.sw?
 
-# Secrets
+# Secrets
+.env
diff --git a/evi-typescript-example/README.md b/evi-typescript-example/README.md
@@ -48,7 +48,10 @@ export VITE_HUME_API_KEY=<YOUR_API_KEY>
 export VITE_HUME_CLIENT_SECRET=<YOUR_CLIENT_SECRET>
 ```
 
-You can make these environment variables persistent by adding them to the `.env` file in the root folder of the repo, which currently exists with placeholders. Once the API secrets have been added to the file, they will persist there and you do not have to set them as environment variables going forward. The `.env` file is listed in the `.gitignore` of the repository, so there is no risk of accidentally committing these secrets to a public repository. 
+You can make these environment variables persistent by adding them to a file named `.env` in the root folder of the repo.
+> There is an example file called `.env.example` with placeholder values, which you can simply rename to `.env`.
+
+Once the API secrets have been added to the `.env` file, they will persist there and you do not have to set them as environment variables going forward. Importantly, the `.env` file is listed in the `.gitignore` of the repository, so there is no risk of accidentally committing these secrets to a public repository. 
 
 ## Serve project