Skip to content

fix: prevent credential leaks via .env files #1038

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mattcarrollcode wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: prevent credential leaks via .env files #1038

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,6 @@ __pycache__
wandb/
artifacts/
node_modules/
.env
.env.*
!.env.example
0 end-to-end-use-cases/blog_generator/.env → ...end-use-cases/blog_generator/.env.example
View file
Open in desktop
File renamed without changes.
0 ...o-end-use-cases/whatsapp_llama_4_bot/.env → ...e-cases/whatsapp_llama_4_bot/.env.example
View file
Open in desktop
File renamed without changes.
8 changes: 7 additions & 1 deletion end-to-end-use-cases/whatsapp_llama_4_bot/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,13 @@ pip install -r requirements.txt

### Step 3: Configure Environment Variables

Create a `.env` file in the project directory and add your API keys and other configuration details as follows:
Copy the `.env.example` file to `.env` and fill in your API keys:

```bash
cp .env.example .env
```

Then edit `.env` with your configuration details:

```plaintext
ACCESS_TOKEN=your_whatsapp_access_token
Expand Down