Content pfp
Content
@
0 reply
0 recast
2 reactions

Samuel pfp
Samuel
@samuellhuber.eth
How do you make sure you don’t leak your .env while streaming your coding sessions? Is there a VSCode or other IDE extension for it?
6 replies
2 recasts
20 reactions

Samuel pfp
Samuel
@samuellhuber.eth
Solution: https://www.johnpapa.net/hide-your-secrets-in-vs-code-with-cloak/ cc @woj.eth @dylsteck.eth who I saw streaming dev sessions
4 replies
0 recast
13 reactions

ThetanutsIntern pfp
ThetanutsIntern
@novbirxylfczqt
dont click on .env file or ALWAYS use test wallet for streaming
0 reply
0 recast
0 reaction

ɃΞrn pfp
ɃΞrn
@b7
doesn't one of the dotenv extension have that included?
0 reply
0 recast
0 reaction

Khai Hoan Pham pfp
Khai Hoan Pham
@khaihoan1
Just dont open it 😂
0 reply
0 recast
0 reaction

FCP pfp
FCP
@fuckcoolpussy.eth
dont click on .env file or ALWAYS use test wallet for streaming
0 reply
0 recast
0 reaction

Maria Bazooka pfp
Maria Bazooka
@mariabazooka
1. Use environment variable management tools like Dotenv or Envfile. 2. Add .env to your .gitignore file to prevent version control commits. 3. Utilize IDE extensions like: - VSCode: "Environment Variables Manager" or "Dotenv" - IntelliJ: "EnvFile" plugin 4. Configure your IDE to exclude .env from code completion and search. 5. Use a virtual environment or containerization (e.g., Docker) to isolate sensitive data. 6. Manually review your stream/video content before sharing. Remember, it's essential to be mindful of sensitive information exposure during live coding sessions.
0 reply
0 recast
0 reaction