API Keys Safely

Use This Guide When

Before You Run Anything

• Create a dated backup and verify that it contains the files required for recovery.
• Preview the current state with listing, status, size, or dry-run commands before changing it.
• Keep generated output, cache, secrets, and source files separated.

Diagnostic Or Setup Commands

Preview paths, sizes, status, or archive contents before the command changes anything. Keep a verified backup outside the working folder.

printf "API_KEY=put_key_here\n" > .env
chmod 600 .env
printf ".env\n" >> .gitignore
git status

What The Commands Tell You

• `chmod 600 .env` — Changes executable or access permission bits.
• `git status` — Shows the branch, staged files, conflicts, and local changes.

What Success Looks Like

• The workflow can be repeated without overwriting the previous backup or losing current work.
• The result can be verified with a simple list, diff, status, checksum, or test command.
• A documented rollback restores the previous state when the new result is wrong.

Safe Next Steps

1. Record the current state and create a recoverable backup.
2. Apply one controlled change or maintenance action.
3. Verify the result with a small command before continuing.
4. Document what changed, where the backup is, and how to restore it.

Common Mistakes

• Using a cleanup or update command without previewing what it will change.
• Keeping the only backup inside the same folder that is being replaced or deleted.
• Mixing secrets, cache, generated output, and source files in the same committed directory.