mirror of
https://github.com/rmcrackan/Libation.git
synced 2026-09-12 21:57:19 -04:00
Cursor Agentandrmcrackan
bc297330ad
Quite a lot of Libation only appears once an account exists, and it is not one switch but two: nothing, one account, or several. The one/many split changes the Import and Remove menus, and the new empty-library panel offers 'Add Account' or 'Scan Library' depending on it. None of that was reachable in a test environment without signing in to Audible, which is how I ended up writing this by hand to check the empty-library states. seed-demo-accounts.cs writes structurally valid but meaningless identities, so Libation counts and lists the accounts and enables everything gated on having one. Any actual scan is refused by Audible, which the script and the docs both say plainly. It appends rather than overwrites, and --clean removes only what it added - the accounts matching demo*@example.com - because this is the file holding real Audible tokens. The first account is demo@example.com, the same one seed-demo-library.cs assigns its books to, so seeding both describes one library instead of two unrelated ones. Co-authored-by: rmcrackan <rmcrackan@gmail.com>
1.2 KiB
1.2 KiB
Scripts
Developer utilities. None of these ship in a Libation install - they exist only in a source checkout.
| Script | Purpose | Documented in |
|---|---|---|
seed-demo-accounts.cs |
Seed fake Audible accounts, to reach what is gated on having one without signing in | Testing Changes |
seed-demo-library.cs |
Seed a library covering every Liberate-column icon, for manual UI testing | Testing Changes |
seed-download-history.cs |
Seed completed downloads so the daily download limit can be tested without downloading | Testing Changes |
Bundle_Debian.sh |
Build the Linux .deb package |
Used by .github/workflows/build-linux.yml |
Bundle_Redhat.sh |
Build the Linux RPM package | Used by .github/workflows/build-linux.yml |
Bundle_MacOS.sh |
Build the macOS app bundle | Used by .github/workflows/build-mac.yml |
Windows/ |
Windows installer (Inno Setup) | Windows/README.md |
Usage for the testing scripts lives in the docs rather than here, so there is only one copy to keep current.