News for hackers. Stuff that matters.
Re:In Praise Of –Dry-Run by IgorPartola on Saturday January 31, 2026 @09:54PM (#46843190)
--with-danger

--make-it-so

--do-the-thing

--go-nuts

--safety-off

So many fun options.

Re:In Praise Of –Dry-Run by Darfk on Saturday January 31, 2026 @10:10PM (#46843286)
I'm a fan of --safety-off. It gives off a 'aim away from face' or 'mishandle me and I'll blow a chunk out of your DB' vibe.
Re:In Praise Of –Dry-Run by JsonCameron on Saturday January 31, 2026 @10:43PM (#46843416)
I've done a few --execute --i-know-what-im-doing for some more dangerous scripts
Re:In Praise Of –Dry-Run by altairprime on Saturday January 31, 2026 @11:29PM (#46843624)
May I recommend --I-take-responsibility-for-the-outcome-of-proceeding and require a capital I?
Re:In Praise Of –Dry-Run by altairprime on Saturday January 31, 2026 @11:28PM (#46843620)
--commit is solid too
Re:In Praise Of –Dry-Run by torstenvl on Sunday February 01, 2026 @12:32AM (#46843907)
It's in the UI not the command line, but I like Chromium's thisisunsafe
Re:In Praise Of –Dry-Run by tetha on Sunday February 01, 2026 @03:51AM (#46844621)
I find it important to include system information in here as well, so just copy-pasting an invocation from system A to system B does not run.

For example, our database restore script has a parameter `--yes-delete-all-data-in` and it needs to be parametrized with the PostgreSQL cluster name. So a command with `--yes-delete-all-data-in=pg-accounting` works on exactly one system and not on other systems.