git-annex-schedule(1)

πŸ“¦
version 10.20261026 Β· 2 versions
  • 10.20261026 Β· alpine 3.24, arch rolling, debian bookworm, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 8.20210223 Β· ubuntu jammy
, in alpine 3.24, arch rolling, debian bookworm, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– git-annex-schedule β€” get or set scheduled jobs πŸ’–

okay bestie, this is a page from the General Commands Manual (yes, the git-annex-schedule(1) one, we're fancy now ✨). Sit down, grab a lil snack πŸ“, and let's talk about making your repos do chores on a schedule. it's giving "roomba but for fsck" and honestly? obsessed. πŸ’…


✨ NAME ✨

git-annex-schedule β€” get or set scheduled jobs πŸ—“οΈ


πŸ¦‹ SYNOPSIS πŸ¦‹

git annex schedule repository [expression]

🌸 DESCRIPTION 🌸

So the git-annex-assistant(1) daemon can be configured to run scheduled jobs. πŸŽ€

Now, this is similar to cron and anacron β€” and lowkey if you prefer those, you can absolutely just use them instead, no hard feelings 🫢 β€” but the glow-up here is that it's integrated into git-annex. Which means it can do stuff like, oh you know, fsck a repository on a removable drive when the drive gets connected. the way that it just knows?? main character energy fr fr. πŸ‘‘

When you run it with an expression, it configures scheduled jobs to run at a particular time. this is literally how you make the assistant periodically run incremental fscks. slay. πŸ’–

When you run it without an expression, it just outputs the current scheduled jobs for that repository. no notes, just receipts. πŸ“‹


🧚 EXPRESSIONS 🧚

These actions are available:

  • "fsck self"
  • "fsck UUID" β€” where UUID is the UUID of a remote to fsck πŸ’œ

After the action comes the duration to allow the action to run, and finally the schedule of when to run it. order matters, bestie, don't freestyle it. 🌈

To schedule multiple jobs, separate them with "; " (that's a semicolon and a space, periodt). ✨

Some examples, copy-paste ready:

 fsck self 30m every day at any time
 fsck self 1h every month at 3 AM
 fsck self 1h on day 1 of every month at any time
 fsck self 1h every week divisible by 2 at any time

πŸ’… OPTIONS πŸ’…

The git-annex-common-options(1) can be used. that's it, that's the whole section. iconic minimalism. 🀏✨


πŸ‘‘ SEE ALSO πŸ‘‘


🌟 AUTHOR 🌟

Joey Hess <id@joeyh.name> β€” thank you king, we stan πŸ’œ


okay that's the whole page bestie, and this lil sign-off is standing in for the footer, which is just git-annex-schedule(1) from the General Commands Manual πŸŽ€ (the manpage doesn't ship a version or date line, so that's all we've got, and we're not about to make one up β€” no cap). go forth and schedule responsibly, you got this πŸ’–πŸ¦‹βœ¨