ReadMeABook

[MickLesk]

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

[github-actions]

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

[schinguhl]

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

[ChaBoiNick]

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.

[ianfriend]

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:

[eoren1]

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

[MickLesk]

I add it later