Gmer4Lfe
d9f917ecef
These files are gitignored, so a bad write had nothing to go back to; the escaping order also stored any value containing a quote truncated but still parseable, which only a read-back can catch.
46 lines
2.1 KiB
Plaintext
46 lines
2.1 KiB
Plaintext
# ── Personal configuration — never push to public repo ────────────────────────
|
|
# These contain API keys, passwords, SSH paths, personal hostnames.
|
|
# Templates (*.template) are safe and remain tracked.
|
|
Configurations/host*.conf
|
|
Configurations/master.conf
|
|
# *.bak alone missed conf_upgrade's real output — it writes host1.conf.bak-20260802, which does
|
|
# not end in .bak — so those sat untracked rather than ignored, one `git add -A` from being
|
|
# pushed. The glob has to cover the suffix.
|
|
Configurations/*.bak*
|
|
.vscode
|
|
|
|
# ── Personal scratch notes — dev-only, never pushed ───────────────────────────
|
|
Notes_To-Do.md
|
|
|
|
# ── Runtime state, data, logs ─────────────────────────────────────────────────
|
|
# Contents, not the directory itself. Ignoring "data/" outright means git never descends into
|
|
# it, and a negation for a file inside an excluded directory is silently ineffective — so the
|
|
# README explaining what data/ is would be the one file missing from every installation of it.
|
|
data/*
|
|
!data/README.md
|
|
State_Files/
|
|
.cache/
|
|
*.log
|
|
*.lock
|
|
|
|
# ── Plugin runtime state (per-host, never synced) ────────────────────────────
|
|
schedule.json
|
|
docker_folders.json
|
|
*.db
|
|
|
|
# ── Plugin config files (co-located with scripts on flash) ───────────────────
|
|
varaverk.cfg
|
|
varaverk.cron
|
|
varaverk-*.txz
|
|
|
|
# ── Build artifacts ───────────────────────────────────────────────────────────
|
|
# .txz packages are attached to GitHub releases, not committed to the repo.
|
|
Plugin/dist/
|
|
|
|
|
|
# ── OS / editor ───────────────────────────────────────────────────────────────
|
|
.DS_Store
|
|
*.swp
|
|
*~
|
|
.vscode/
|