KAPLA-SQLITE(1)

💅 KAPLA-SQLITE(1) — the Kapla Manual, bestie edition 🎀

okay so picture this: it's kapla-sqlite, and it's here to read blocks from an SQLite database. That's the whole vibe. Let's get into it 🫶

---

✨ SYNOPSIS ✨

kapla sqlite [COMMAND] …

So here's the tea 🍓 — blocks of encoded content can totally be encoded in an SQLite database. Which is lowkey iconic for removeable storage, delay tolerant transport, or honestly any other sneakernet-esque transport you can dream up (yes, that means literally walking a file to another computer, no cap).

The commands below are all about getting blocks from SQLite databases. If you wanna go the other direction and store blocks to an SQLite database? That's a different quest — go look at the --sqlite option for the encode command, iykyk 💅

---

🌈 COMMANDS 🌈

• import [--socket=ERIS_UNIX_SOCKET] [OPTION]… SQLITE_DB — Import blocks from an SQLite database. Just. Pull 'em all out. 💖
• open [--socket=ERIS_UNIX_SOCKET] [OPTION]… SQLITE_DB — Open the SQLite database and make the blocks available from therein. On-demand queen behavior 👑

---

🦋 COMMON OPTIONS 🦋

• --help[=FMT] (default=auto) — Shows this help in format FMT. The value FMT must be one of auto, pager, groff or plain. With auto, the format is pager or plain whenever the TERM env var is dumb or undefined. (so like, if your terminal is having a moment, it keeps it simple ✨)
• --version — Show version information. The classic. The legend. 🎀

---

🔥 EXIT STATUS 🔥

kapla sqlite exits with:

1. 0 — on success. slay 💅
2. 123 — on indiscriminate errors reported on standard error. 😭
3. 124 — on command line parsing errors. (you typed something weird, bestie)
4. 125 — on unexpected internal errors (bugs). 💀 go file a bug fr fr

---

🌸 EXAMPLES 🌸

Step one: encode some content to an SQLite database:

kapla encode -n --sqlite block.sqlite file.txt

Step two: move the file block.sqlite to another machine with your favorite bike 🚲 (yes, seriously, the manpage said bike, we love a physical transport moment) and open the database using:

kapla sqlite open block.sqlite

This will make the blocks stored in the block.sqlite database available to the Kapla store on-demand. Then you can decode content using blocks using the decode sub-command. Chef's kiss 🔥

Alternatively — the impatient route, extremely valid — you can import all blocks contained in the database:

kapla sqlite import block.sqlite

---

⭐ STANDARDS ⭐

• SQLite for ERIS block storage — https://eris.codeberg.page/eer/sqlite.xml

---

👑 SEE ALSO 👑

• kapla-encode(1) — go read it, it's the other half of this story 💜

---

and that's the whole page, bestie 🧚 no notes, no skips, every flag accounted for. this gorgeous little document is Kapla 0.4.0 and it's signed KAPLA-SQLITE(1) — periodt. 💖✨