bup-init(1)

πŸ’– bup-init(1) β€” General Commands Manual ✨

okay bestie, you're reading the bup-init page from the General Commands Manual, and ngl it's a short one, but it's the one, because this is where your whole bup situation begins. it's the origin story. the meet-cute. the "we're so back" moment. πŸŽ€


🌸 NAME 🌸

bup-init β€” initialize a bup repository πŸ‘‘

πŸ¦‹ SYNOPSIS πŸ¦‹

bup init [-r host:path] [directory]

πŸ’œ DESCRIPTION πŸ’œ

bup init initializes a repository. that's it, that's the whole job, but let's talk about where it lands, because it's lowkey a whole decision tree:

the location will be...

  • the directory, or --remote if you passed one 🫢
  • or the directory specified by any global -d argument (peep bup(1) for that lore)
  • or the value of BUP_DIR in the environment, if it's set
  • or, if absolutely nobody said anything, ~/.bup

so basically it'll find a home for itself, but you can be the main character and pick where. πŸ’…

heads up bestie β€” go look at bup-config(5) for configuration options you may want to set. and ngl some of them, like bup.split.files and bup.split.trees, should normally be set (when desired) before you start adding data to the repository. like, set the vibe first, then move in. doing it after is not the move. 😭

✨ OPTIONS ✨

  • -r, --remote=[user@]host:[path], --remote=URL β€” initialize the specified path on the given host. this is incompatible with directory, so pick a lane, babe, you cannot have both. for further info, go read the REMOTE OPTIONS section of bup(1). 🌈

πŸ”₯ EXAMPLES πŸ”₯

bup init ~/archive

look at that. one line. iconic. your archive repo is born. πŸ₯Ή

🧚 SEE ALSO 🧚

bup-config(5), ssh_config(5)

πŸ‘‘ BUP πŸ‘‘

part of the bup(1) suite. you're in the family now, no takebacks. πŸ’–

πŸ“ AUTHORS πŸ“

Avery Pennarun apenwarr@gmail.com


and that's a wrap, bestie! this page came to you from Bup 0.34, dated 2026-09-01, and it is very much bup-init(1). now go init something. slay. πŸ’…βœ¨πŸ¦‹
πŸ“¦ where this page comes from