|
| ▲ | tetha 7 hours ago | parent | next [-] |
| 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. |
|
| ▲ | Darfk 13 hours ago | parent | prev | next [-] |
| 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. |
|
| ▲ | torstenvl 10 hours ago | parent | prev | next [-] |
| It's in the UI not the command line, but I like Chromium's thisisunsafe |
|
| ▲ | JsonCameron 12 hours ago | parent | prev | next [-] |
| I've done a few --execute --i-know-what-im-doing for some more dangerous scripts |
| |
| ▲ | altairprime 11 hours ago | parent [-] | | May I recommend --I-take-responsibility-for-the-outcome-of-proceeding and require a capital I? |
|
|
| ▲ | altairprime 11 hours ago | parent | prev [-] |
| --commit is solid too |
