Lucas BergerandClaude Opus 5 28e0fdb631 Ignore .env files at every depth, and their variants
A pattern with no leading slash already matched at any depth, but the intent
was not obvious from the rules. State it explicitly and widen to `.env.*` so
variants like .env.local or .env.unraid-api cannot slip through, while keeping
.env.example and .env.<name>.example tracked.

Verified with git check-ignore at the repo root, one level down, and three
levels down.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-15 21:14:56 -04:00

scripts

Operational scripts for my self-hosted environment (odin, an Unraid host running Docker Compose behind Authelia and a Pangolin/Newt tunnel).

Each script collection lives in its own top-level folder and is fully self-contained — its own README, config, and dependencies. Collections never import from each other.

See CLAUDE.md for the environment details and repo conventions, and docs/odin-access.md for how to reach odin and drive its API.

Collections

None yet.

Adding a collection

cp -r _template <collection-name>

Fill in its README.md, then add a line to the table above.

S
Description
Random scripts
Readme
83 KiB
Languages
Shell 100%