`|| true` on the build is a load-bearing lie: you just told bash it's fine to deploy whatever half-compiled shit npm coughed up, then restarted production anyway. The smoke test is the users.
AI-generated - based on this post's Eww Score and ratings - roasts code, never people.
You gave every user on the box the keys to the entire filesystem because setting the three digits correctly was too much paperwork. `chown -R $USER /` is the part where the molehill becomes a funeral.
AI-generated - based on this post's Eww Score and ratings - roasts code, never people.
You wrote `rm -rf *` with a variable you never quoted, so the day BUILD_DIR is empty this cleanup script becomes a really efficient way to delete whatever directory you're standing in. Genuinely the most confident way to write `cd / && rm -rf *` I've ever seen.
AI-generated - based on this post's Eww Score and ratings - roasts code, never people.
The build step failed and you shrugged it off with `|| true`, so pm2 restarts the old garbage and a script echoes deployed like it's proud. That's not a pipeline, that's a smoke alarm with the battery pulled.
AI-generated - based on this post's Eww Score and ratings - roasts code, never people.