GRIVE(1)

πŸ“¦ version 0.5.3, in fedora 43, fedora 44, nixos 26.05, nixpkgs unstable

grive(1) β€” Google Drive client for GNU/Linux πŸ’–

okay bestie, so this is the manual for grive, and it lives in the General Commands Manual section of your man pages (that's the (1) in grive(1), it's giving "I'm a user-facing command, come hang out"). Sit down, grab a boba, we're syncing your whole life to the cloud πŸ¦‹


NAME

grive β€” Google Drive client for GNU/Linux ✨


SYNOPSIS

grive [OPTIONS]

that's it. that's the whole vibe. options go in, files go up 🌈


DESCRIPTION

Grive is a Google Drive client β€” you know, Google Drive, the online storage service β€” built for GNU/Linux systems. it's literally here to serve you πŸ’…

It lets you synchronize all your files on the cloud with a directory of your choice, and it also uploads new files to Google Drive. your local folder and your cloud folder, holding hands, matching outfits, iconic 🫢

The options are as follows:

OPTIONS ✨

  • -a, --auth β€” asks Google for an authorization token. no token, no entry, that's the rules πŸ™ˆ
  • -d, --debug β€” turns on debug level messages. heads up: this implies -V πŸ’€
  • --dry-run β€” only detects which files need to be uploaded/downloaded, without actually performing any changes. it's a dress rehearsal, not the show πŸŽ€
  • -f, --force β€” forces grive to always download a file from Google Drive instead of uploading it. remote wins, periodt πŸ’…
  • -u, --upload-only β€” forces grive to not download anything from Google Drive, and to only upload local changes to the server instead. outgoing only, no lurkin' πŸ‘‘
  • -n, --no-remote-new β€” forces grive to download only files that are changed in Google Drive and already exist locally. if it's new-new, it stays where it is 🌸
  • -h, --help β€” produces the help message 🫢
  • --ignore <perl_regexp> β€” ignores files whose relative paths match this Perl Regular Expression. yes, actual Perl regex, she's fancy ✨
  • -l <filename>, --log <filename> β€” writes log output to <filename> πŸ“
  • --log-http <filename_prefix> β€” logs all HTTP responses into files named <filename_prefix>YYYY-MM-DD.HHMMSS.txt for debugging. perfect for when you're deep in the trenches at 3am 😭
  • --new-rev β€” creates new revisions in the server for updated files πŸ”₯
  • -p <wc_path>, --path <wc_path> β€” uses <wc_path> as the working copy root directory πŸ“
  • -s <subdir>, --dir <subdir> β€” syncs a single <subdir> subdirectory. internally converted to an ignore regexp, lowkey sneaky but it works 🧚
  • -v, --version β€” displays the program version ⭐
  • -P, --progress-bar β€” prints an ASCII progress bar for each downloaded/uploaded file. watching that bar fill up is genuinely main character energy πŸ’–
  • -V, --verbose β€” verbose mode. enables more messages than usual, if you like your terminal chatty 🌈

.griveignore πŸŽ€

You may create .griveignore in your Grive root and use it to set up your exclusion/inclusion rules. think of it as the bouncer at the door of your sync πŸ’…

The rules are similar to Git's .gitignore, but they may differ slightly, because the implementation is a different implementation, iykyk 🀷

  • lines that start with # are comments πŸ’¬
  • leading and trailing spaces are ignored unless escaped with \
  • non-empty lines without ! in front are treated as "exclude" patterns
  • non-empty lines with ! in front are treated as "include" patterns, and they have priority over all "exclude" ones β€” include girlies stay winning πŸ‘‘
  • patterns are matched against the filenames relative to the grive root πŸ“‚
  • a/**/b matches any number of subpaths between a and b, including 0
  • **/a matches a inside any directory
  • b/** matches everything inside b, but not b itself
  • * matches any number of any characters except /
  • ? matches any character except /
  • .griveignore itself isn't ignored by default, but you can include it in itself to ignore it πŸ™ˆ (she's self-aware, we love that for her)

AUTHORS 🫢

The current maintainer is Vitaliy Filippov.

The original author was Nestal Wan. This manpage was written by JosΓ© Luis Segura Lucas (josel.segura@gmx.es).

The full list of contributors may be found here: http://yourcmc.ru/wiki/Grive2#Full_list_of_contributors β€” go give them their flowers, fr fr πŸ’


REPORT BUGS πŸ›

found something cursed? don't sit on it bestie, go tell the devs. bugs hate being perceived πŸ’€

and that's the whole page, babe 🌸 this one was dated January 3, 2016, from the General Commands Manual corner of the internet β€” so when you're reading it, just know the manual name grive and that lil' date are basically its birth chart. periodt πŸ’…βœ¨

πŸ“¦ where this page comes from