BEAN-FILE(1)

💖 BEAN-FILE(1) 💖

okay so bestie, welcome to the bean-file manual page — it's a User Command, she's iconic, and she's about to make your downloaded financial documents make sense. no cap.

---

✨ NAME ✨

bean-file — files and renames Beancount input documents after transaction extraction 🎀

---

🌸 DESCRIPTION 🌸

here's the whole vibe, laid out for you:

usage: bean-file [-h] [--version] [-o OUTPUT_DIR] [-n] [--no-overwrite]

       CONFIG_FILENAME DIR-OR-FILE [DIR-OR-FILE ...]

the main character move: she moves and renames your downloaded files into a documents tree that mirrors your chart of accounts. literally reorganizing your whole life, one receipt at a time. 🦋

🧚 positional arguments (the ones you just have to hand over)

• CONFIG_FILENAME — the importer configuration file. it's a Python file, and inside it lives a data structure that's specific to your accounts. so like, it's giving bespoke. ✨
• DIR-OR-FILE — filenames or directories to search through for files to import. you can pass as many as you want, she's flexible like that. 💅

👑 options (flags, flags, flags)

• -h, --help — shows this help message and dips. the classic. 🙈
• --version, -V — shows the program's version number and exits. tiny flex. ⭐
• -o OUTPUT_DIR, --output OUTPUT_DIR, --output-dir OUTPUT_DIR, --destination OUTPUT_DIR — the root of the documents tree where the files get moved to. four names, one job, she contains multitudes. 🌈
• -n, --dry-run — just prints where the files would be moved; doesn't actually move them. a little peek behind the curtain, no consequences. 🔥
• --no-overwrite — don't overwrite destination files that have the same name. she's polite, she respects boundaries. 🫶

ngl, if you're nervous, run with -n first and vibe check the output before committing. the flags are all listed above, bestie — go wild. 💀

---

that's the whole page, periodt. 💜

the sign-off: this was bean-file 2.3.6, dated April 2024, and yes, the footer said BEAN-FILE(1) too, because she's consistent. mwah. 💅✨🎀