Skip to content

Add .gitignore; stop tracking node_modules, dist, data, and media - #44

Open
iamgroot400 wants to merge 3 commits into
arvids-unavailable:mainfrom
iamgroot400:remove-committed-node-modules
Open

Add .gitignore; stop tracking node_modules, dist, data, and media#44
iamgroot400 wants to merge 3 commits into
arvids-unavailable:mainfrom
iamgroot400:remove-committed-node-modules

Conversation

@iamgroot400

Copy link
Copy Markdown

The repo has no .gitignore, so build output and installed dependencies ended up committed: frontend/node_modules (9,619 files), frontend/dist, plus data/ and media/. CONTRIBUTING.md already documents media/ and data/ as gitignored ("Don't commit the exercise media (media/) or data/ — they're gitignored") — this PR makes that actually true.

Summary

  • Added a root .gitignore (node_modules, build output, data/, media/, .DS_Store, .env)
  • git rm -r --cached on the now-ignored paths — untracked going forward, files untouched on disk, no history rewrite

Note

data/ held real instance state (session secret, VAPID keypair, user db) — worth rotating on any instance that shares this history, and possibly a follow-up history rewrite (git filter-repo or similar) if that's a priority; that's a bigger, maintainer-level call so I left it out of this PR. Happy to help with a follow-up if useful.

Test plan

  • ls data/ media/ — files still present on disk after git rm --cached
  • git status clean, nothing untracked besides the new .gitignore

Load starter plan used to hand you one fixed Push/Pull/Legs routine.
It now opens a picker with four templates (PPL, Upper/Lower, Full
Body, 5x5), each built from the same generic spec -> routines/week
mapping in lib/starter.js, so adding another plan later is just a
new entry, not new plumbing.

Addresses the "additional starter plans" item in CONTRIBUTING.md's
good-first-issues list.
The repo had no .gitignore, so build output and installed dependencies
ended up committed: frontend/node_modules (9,619 files),
frontend/dist, plus data/ (the self-hosted instance's session secret,
VAPID keypair, and user db) and media/ (the ~140 MB exercise
image/gif set fetched at runtime). CONTRIBUTING.md already documents
media/ and data/ as gitignored — this makes it true.

Files are untracked going forward, not removed from history — a
history rewrite is a separate, maintainer-level decision given data/
holds what look like live secrets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant