Own Ebook Customer Portal

Updating Own Ebook

Documentation · Own Ebook self-hosted

Update from your admin panel

Starting with Own Ebook 1.0.14, open your own website and choose Admin → License & Updates. New releases appear automatically, with up to three short highlights. Administrators also receive one email per release when the installation’s SMTP is configured.

  1. Let active book creation and exports finish.
  2. Review the available version and click Update now.
  3. Your license and update entitlement are checked again, the signed package is verified, and a backup is saved before installation.
  4. Follow the progress. The site briefly pauses and restarts; the page reconnects automatically.

Checking is automatic; installing always requires your click. If update entitlement has expired, the page links to your purchaser account for renewal. Failed health checks restore the previous code; backup files and reports remain on your server.

Fresh full-package installations of 1.0.14 or newer include the admin-update controller. Preserve the signed release as published; documentation corrections belong in the next release, not a replacement ZIP under the same version.

Hosting restart guidance in 1.0.16: after updating from an older version, follow the “One more step: restart your hosting application” notice in Admin → License & Updates. A “Finish your hosting update” reminder remains elsewhere in the admin area. Once the update succeeds and book/PDF work finishes, open your hosting panel → Applications / Application Manager, select the existing application for this website, click Stop, wait until it stops, then click Start once. Ask your provider if they manage the controller. Never create another application or restart during an update or restore.

The notice disappears when the current controller is verified and ready. “Check restart status” only reads status. This is not required after every update: application-only updates with unchanged controller code and fresh 1.0.16 installations need no additional restart after normal startup. If status is unavailable or maintenance needs review, follow that message rather than restarting blindly.

Enable it once on an older installation

Shared hosting / Webuzo (or your provider’s panel): follow the illustrated Arabic guide. Run the existing manual updater once, then stop and start the application from the hosting panel to load the new controller. If a provider operates your controller, ask them to perform that one-time transition and restart the same controller; do not create a duplicate application. Do not run the VPS sudo or enable-admin-updates.py command on a shared account.

Managed VPS / systemd: first update using sudo bash /opt/own-ebook/current/management/update.sh. Then enable the local update controller once:

sudo python3 /opt/own-ebook/current/management/enable-admin-updates.py

Use your actual installation path if different. This installs a dedicated update service; it does not grant the web application general sudo access. New managed installations include it automatically. Versions older than 1.0.6 use their existing Node.js update command for this first upgrade.

Manual recovery remains available

The existing manual updater is still available for the one-time transition and technician-led repair. On shared hosting, use the account-level command in the illustrated guide and the provider-confirmed paths. On a managed VPS, use the sudo command above. Update now is the normal path once the controller is installed.

Backups and recovery

Reports and backups are in your installation’s updates directory. Detailed update logs are in admin-updates on a managed VPS, or own-ebook-data/private/admin-updates on shared hosting. If an update is interrupted, inspect the report and restart the application from your hosting panel or ask your server administrator to inspect the service. Intentional update/restore maintenance persists across controller restarts in 1.0.15. Never delete a lock merely because it is old or its process is absent; inspect and complete or repair the operation first.

Keep independent off-server backups. Existing database, uploads, license and provider credentials are preserved. Complete releases replace core code customizations; retain custom work separately. Packages declaring database migrations are refused by this updater.

Saved PDF recovery in 1.0.17

If writing and artwork are saved but the final file failed, choose Check saved PDF in Library or Export. It uses no AI credit and creates no purchase. Review layout opens the saved layout. A fresh successful check clears only the matching old PDF warning; it does not settle pending payments, start Pro production or republish a store product.

Small, Medium and Large allow 20, 40 and 60 printed pages including the cover. The message shows the actual total and limit. Missing images, incomplete content, busy rendering and timeouts have separate messages. Books created without a size tier retain their previous contract. Never regenerate an entire book to resolve an overflowing PDF.

Conflicting numbered sequences are kept for comparison. Selecting a version creates a separate review draft and leaves the original and its financial history intact. A PDF passing its checks does not certify the practical correctness of a crochet pattern.

Read resources/pdf-recovery.md for the administrative dry-run repair tool and guarded backup restoration. No bulk repair or paid generation runs during installation. 1.0.17 keeps the 1.0.16 controller unchanged; follow a same-application restart reminder only when it is displayed.

Pro preparation recovery in 1.0.19

This update bounds retries before an AI request when database connections or PDF capacity are temporarily unavailable. Finished pages, balances, approved spending limits, licenses and settings are preserved. Already paused selections stay paused. After updating, open View Pro progress to review the cause and remaining pages; Continue can spend the existing balance on unfinished AI work. An uncertain paid result is reconciled before any retry. Read the recovery guidance and resources/pro-recovery.md.