gromox-dbop(8)

πŸ“¦ version 3.6, in alpine 3.24, opensuse-leap 16.0

πŸ’… gromox-dbop(8) β€” the user database maintenance utility, bestie edition

okay so picture this: it's gromox-dbop(8), straight out of the Gromox admin reference, and she is the User database maintenance utility. that's the whole vibe. she does not do small talk, she does schema surgery. ✨


🌸 SYNOPSIS 🌸

gromox-dbop [-CU] [--create-old] [-c mysql_adaptor.cfg]

look at her. short, sweet, three-ish flags, zero drama. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • -C β€” bestie this one creates the initial set of tables for the user information database, and the database is in MySQL. brand new tables, fresh out the box. 🌱
  • -U β€” this upgrades the schema of the user information database. important caveat though: the database (that's MYSQL_DBNAME) should exist and it should be blank. like, empty-empty. don't come in with a whole personality already in there. ⚠️
  • --create-old β€” creates a blank initial database using version 0. and like, why would you want that? the man page literally says it can be used for testing the upgrade procedure. so it's a little time capsule database for practicing your -U glow-up on. πŸ•°οΈβœ¨
  • -c mysql_adaptor.cfg β€” here's the path to a configuration file that defines MYSQL_HOST, MYSQL_USERNAME, etc. 🫢 and if you omit it? gromox-dbop will read /etc/gromox/http.cfg to locate mysql_adaptor.cfg to locate the mysql parameter. yes, that's three hops. she's giving scavenger hunt. iykyk. πŸ”
ngl, don't skip the -U caveat. the database needs to exist and be blank β€” if it's not blank, that's a you problem and it's giving chaos. 😭

πŸ‘€ SEE ALSO πŸ‘€

go read those too, they're iconic in their own right. πŸ‘‘


and that's the page!! source: Gromox, admin reference, page gromox-dbop(8) β€” the footer's got no date on it so she's simply timeless, no cap. πŸ¦‹πŸ’–πŸŽ€

πŸ“¦ where this page comes from