Skip to content

OperaLibre 0.4.13

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Oct 22:43
· 20 commits to main since this release
0.4.13
2ae15a0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's changed

Changes since 0.4.12:

  • The browser reader now fills the window, with a contents column, reading controls, and a docked player offering playback speed, the sleep timer, and chapters. EPUBs, supplements, and image galleries stay usable across book details and Now Playing, including narrow screens.
  • The iPad interface has separate Shelf and Reading tabs with a sliding transition. Tab selection, shelf layout, and tab-bar colors stay in step when opening a book through different entry points.
  • Explore the on-device demo now includes a bundled Alice’s Adventures in Wonderland audio excerpt, EPUB, and sentence timings for offline listening and read-along. Sources, credits, and license information are available offline. Bundled demo audio also opens correctly in the iOS player.
  • Server and macOS updaters remember accepted signing-key rotations and prevent overlapping update checks from undoing them. This release uses the existing trusted signing key; it does not introduce a key rotation.

Existing generated read-along maps remain valid; the mapping revision is unchanged and no remapping is recommended for this update.

Source changes since 0.4.12: https://github.com/DonovanMontoya/OperaLibre/compare/0.4.12..0.4.13

Downloads

The easy way (macOS and Linux)

One command downloads the right package for your computer, verifies its SHA-256 digest, walks you through setup, and starts the server — and updates an existing installation in place when run again:

curl -fsSL https://raw.githubusercontent.com/DonovanMontoya/OperaLibre/main/script/install.sh | sh

Add | sh -s -- --help to see its options, including --server-only for headless machines.

Which file should I download?

  • Most people: download the combined package for your computer. It includes the server and web app, starts in the background, and opens in your browser without leaving a Terminal window open.
  • Server only: use the same combined package and set web_dist_dir = (blank) in its server.config, then start it with start.sh or start.cmd. The installer's --server-only option does this for you.
  • Frontend only: download the file ending in frontend.zip when you already have an OperaLibre or Jellyfin server and want to deploy only the static web app.
  • Android: the file ending in android-unsigned.apk is an unsigned release build for developers or distributors to sign before installation.
  • Update manifest: operalibre-manifest-v1.json is what installations read to update themselves; you do not need to download it.
  • Read-along sync add-on: the optional sync add-on is published in its own readalong-sync-v… release, only when it changes. Install it from Administration; you do not need to download it yourself.
  • Deployment profiles: new installs start in local mode. Choose lan for a trusted LAN/VPN or proxy behind same-machine HTTPS; remote first-run setup uses a one-time server token.
  • Transfer limits: uploads, generated ZIP downloads, and simultaneous ZIP generation have configurable server-side limits. Existing configs automatically receive safe defaults.

Choose windows-x64 for a 64-bit Windows PC, linux-x64 for a typical Intel/AMD Linux server, linux-arm64 for a 64-bit ARM Linux server or Raspberry Pi, macos-arm64 for an Apple Silicon Mac, or macos-x64 for an Intel Mac.

Every user-facing installation package contains a START-HERE.txt file. The SHA256SUMS.txt attachment can be used to verify downloaded files.

Administrators are notified in the app when a newer release is available. On combined and server-only release installations, an owner can install the matching verified package from Administration — server-only installations update just the server and leave a custom frontend untouched; other custom deployments use the release link for a manual update.

New users can follow the full release installation guide for first launch, adding books, phone access, backups, and updates.

Assets 22
Loading