Skip to content

ReadMeABook #2137

Closed
Closed
ReadMeABook#2137
Labels
Ready For TestingStarted Migration To ProxmoxVE

Description

@MickLesk
MickLesk
opened on Aug 4, 2026

Name of the Script

ReadMeABook

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 supported

📋 Script Details

Request and download platform for audiobooks — the audiobook counterpart to Sonarr/Radarr, feeding a library that Audiobookshelf can serve. Requested in discussion #12841.

  • Stack: Next.js + Prisma. Release v1.2.1 has no assets, so it builds from the tarball: npm ci, npx prisma generate, npx prisma migrate deploy, npm run build, started via npm run start on 3030.
  • Layout taken from dockerfile.unified, which bundles Postgres and Redis into one image. Here they are proper services: PG_VERSION="17" setup_postgresql and the Debian redis-server.
  • Node 20 to match the Dockerfile's node:20-bookworm base.
  • setup_ffmpeg instead of the static ffmpeg the Dockerfile pulls from johnvansickle — with the reworked helper that is now the distribution package, which is both faster and LGPL.
  • NEXTAUTH_SECRET is generated at install; the update path backs up and restores .env around the CLEAN_INSTALL refresh, since changing it would invalidate every session.
  • Note: the Next.js build wants ~4 GB RAM. Below that it tends to get OOM-killed.

Source: https://github.com/kikootwo/ReadMeABook

Activity

  1. MickLesk
    added
    task
    Ready For Testing
    and removed
    task
    on Aug 4, 2026

  2. github-actions commented on Aug 4, 2026

    @github-actions
    github-actionsbot
    on Aug 4, 2026 – with GitHub Actions
    Contributor

    The ReadMeABook script is ready for testing:

    bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/readmeabook.sh)"

    Create your account through the web UI at http://:3030 on first visit - the first user becomes the administrator.
    Mount your audiobook library into the LXC and point the download directory at it, otherwise finished downloads stay inside the container.
    NEXTAUTH_SECRET is generated at install and stored in /opt/readmeabook/.env. Changing it invalidates all existing sessions. The update path backs the file up and restores it around the source refresh.
    Next.js build with Prisma migrations against the local PostgreSQL. The build needs roughly 4 GB RAM; less tends to end in an out-of-memory kill.

    Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

    Discord testing thread: https://discord.com/channels/1302816934508630047/1534101381391061143

  3. schinguhl commented on Aug 5, 2026

    @schinguhl
    schinguhl
    on Aug 5, 2026

    CONFIG_ENCRYPTION_KEY= was missing in .env file during installation. I added the line manually, restartet and continued the wizard.

  4. ChaBoiNick commented on Aug 14, 2026

    @ChaBoiNick
    ChaBoiNick
    on Aug 14, 2026

    I had to grab my key from the env and add "Environment=CONFIG_ENCRYPTION_KEY=your_generated_hex_string" this line in the [service] section of the etc/systemd/system/readmeabook.service.
    Worked perfectly after.

  5. ianfriend commented on Aug 21, 2026

    @ianfriend
    ianfriend
    on Aug 21, 2026

    UPDATE: This is caused by the issues above about the missing CONFIG_ENCRYPTION_KEY. I generated my own key and added it to the .env file they it all worked ok

    I get to the end of setup with green ticks all the way through but then get an error at the end:

    Image

  6. eoren1 commented on Aug 22, 2026

    @eoren1
    eoren1
    on Aug 22, 2026

    Same issue that got solved using Claude on my Proxmox VE with (triple check this is correct for you):
    echo "CONFIG_ENCRYPTION_KEY=$(openssl rand -base64 32)" >> /opt/readmeabook/.env systemctl restart readmeabook journalctl -u readmeabook -f

  7. MickLesk commented on Aug 22, 2026

    @MickLesk
    MickLesk
    on Aug 22, 2026
    MemberAuthor

    I add it later

  8. Quotacious commented on Aug 26, 2026

    @Quotacious
    Quotacious
    on Aug 26, 2026
    Image

    At this point, it continues and takes you out of the setup, but there are no Scheduled Jobs and there is no option to create them manually.

    -- Boot 3a899c1be00f46c39e1b8cfef7c58066 --
    Aug 26 16:38:45 ReadMeABook systemd[1]: Started readmeabook.service - ReadMeABook.
    Aug 26 16:38:45 ReadMeABook npm[332]: > readmeabook@1.2.2 start
    Aug 26 16:38:45 ReadMeABook npm[332]: > next start
    Aug 26 16:38:45 ReadMeABook npm[366]: ▲ Next.js 16.0.7
    Aug 26 16:38:45 ReadMeABook npm[366]: - Local: http://localhost:3030
    Aug 26 16:38:45 ReadMeABook npm[366]: - Network: http://10.10.10.47:3030
    Aug 26 16:38:45 ReadMeABook npm[366]: ✓ Starting...
    Aug 26 16:38:45 ReadMeABook npm[366]: [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: npm i baseline-browser-mapping@latest -D
    Aug 26 16:38:46 ReadMeABook npm[366]: ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead.
    Aug 26 16:38:46 ReadMeABook npm[366]: ✓ Ready in 487ms
    Aug 26 16:40:00 ReadMeABook npm[366]: [ERROR] [Auth] User not found in database
    Aug 26 16:40:00 ReadMeABook npm[366]: {
    Aug 26 16:40:00 ReadMeABook npm[366]: "userId": "6b4235a8-5a81-44a6-bb65-01b54cec884e"
    Aug 26 16:40:00 ReadMeABook npm[366]: }
    Aug 26 16:44:48 ReadMeABook npm[366]: [INFO] [QBittorrent] [QBittorrent] No credentials configured — running in auth-optional mode (suitable for IP-whitelisted qBittorrent or auth-less proxies like Decypharr)
    Aug 26 16:44:49 ReadMeABook npm[366]: [INFO] [QBittorrent] [QBittorrent] No credentials configured — running in auth-optional mode (suitable for IP-whitelisted qBittorrent or auth-less proxies like Decypharr)
    Aug 26 16:45:27 ReadMeABook npm[366]: [INFO] [API.Setup.Complete] Configuration saved successfully
    Aug 26 16:45:27 ReadMeABook npm[366]: (node:366) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Commander]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
    Aug 26 16:45:27 ReadMeABook npm[366]: (Use node --trace-warnings ... to show where the warning was created)
    Aug 26 16:45:27 ReadMeABook npm[366]: (node:366) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added to [Commander]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
    Aug 26 16:45:27 ReadMeABook npm[366]: (node:366) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added to [Commander]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit

  9. GeekCad commented on Sep 2, 2026

    @GeekCad
    GeekCad
    on Sep 2, 2026

    Is there a way to force RMAB to rescan the imported books?
    I've adjusted the folder and file templates and would like to rescan and update my library.
    Thanks

  10. ChaBoiNick commented on Sep 2, 2026

    @ChaBoiNick
    ChaBoiNick
    on Sep 2, 2026 via email
  11. MickLesk
    added
    Migration To ProxmoxVE
    on Sep 2, 2026

  12. github-actions commented on Sep 2, 2026

    @github-actions
    github-actionsbot
    on Sep 2, 2026 – with GitHub Actions
    Contributor

    A PR has been created for readmeabook: community-scripts/ProxmoxVE#16963

  13. github-actions
    added
    Started Migration To ProxmoxVE
    and removed
    Migration To ProxmoxVE
    on Sep 2, 2026

  14. MickLesk commented on Sep 2, 2026

    @MickLesk
    MickLesk
    on Sep 2, 2026
    MemberAuthor

    Merged with #16963 in ProxmoxVE

  15. MickLesk
    closed this as completedon Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Ready For TestingStarted Migration To ProxmoxVE

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions