# For Python tools
pip install python-dotenv
.env File# Copy the template
cp .env.example .env
# Edit with your values (if needed)
nano .env # or use any text editor
Windows (PowerShell):
.\install-hooks.ps1
Linux/Mac:
chmod +x install-hooks.sh
./install-hooks.sh
# Check that .env is ignored
git check-ignore .env
# Should output: .env
# Test Python config
cd Python
python config.py
β No API keys required - This project currently works 100% offline!
The secret management system is set up for future use when you add:
The pre-commit hook prevents committing:
.env filessecrets.propertiesQ: Do I need a .env file right now?
A: No! The project works without it. Itβs there for future API integrations.
Q: What if I accidentally commit a secret? A: See the What to Do If You Accidentally Commit a Secret section in the full security documentation, or visit the Security Policy for more details.
Q: Can I skip the pre-commit hook?
A: Yes, but not recommended. Use git commit --no-verify to bypass (use carefully!).