Own Ebook Customer Portal

System requirements

Documentation · Own Ebook self-hosted

Hostbas Hero + MongoDB Atlas (use 1.0.16+): use the illustrated Arabic shared-hosting guide. It uses the separate English browser installer and prepared frontend. The server instructions below apply to the VPS/systemd option only.

Check Will my hosting work? before ordering a hosting plan.

Automatic setup (1.0.6+): choose a new Ubuntu 24.04 x86-64 server with AVX, systemd, at least 4 GB RAM and 20 GB free disk. It prepares Node.js, the private database, PDF browser and HTTPS. Existing web servers and hosting panels are refused. Other prepared Linux environments use the technician installation path.

Shared-hosting requirements

Use a provider-prepared account with Node.js 24 recommended (minimum 22), npm, Python 3, a persistent Application Manager, Chromium system libraries and Arabic/English font files visible inside CageFS or the provider’s isolation. Self-managed setup also needs Terminal. Keep at least 8 GB free disk; the installer does not raise memory/process limits or change your plan. The package contains the prepared frontend: do not compile Next.js on shared hosting.

The application source and private data must be outside every web-served directory, including public_html and add-on domain DocumentRoots. Confirm the app’s public egress IP, allow it in Atlas (/32 for a single IPv4), and have the provider permit outbound connections to Atlas nodes on 27017 with DNS/SRV. No inbound MongoDB port is needed on the web server. A basic requirements pass does not establish Atlas connectivity or license activation; inspect Arabic and English text in a real PDF as well.

Resource capacity in 1.0.15: shared hosting defaults to one PDF job and one Chromium browser at a time. This does not certify a 512 MB or 1 GB account for production. Have the provider measure RAM and process/thread peaks using a representative book and confirm a bounded restart policy. Run one API process per installation; do not enable cluster workers. See the resource and recovery settings.

VPS/systemd server requirements only

  • A separate Linux VPS/dedicated server with systemd and root/sudo access. Ubuntu 24.04 LTS is the recommended setup target; Ubuntu 22.04 and supported Debian releases also need the correct browser dependencies.
  • Supported Node.js LTS: Node 24 recommended, minimum Node 22; npm and Python 3.
  • A dedicated MongoDB replica set with a database-scoped account. A standalone MongoDB instance and MySQL are not sufficient. Use a compatible CPU for local MongoDB, or a managed MongoDB service such as Atlas.
  • Nginx or an equivalent reverse proxy, a domain and valid HTTPS.
  • Playwright Chromium, its Linux system dependencies and readable Arabic/English font files for PDF exports, plus permission to run background application jobs.
  • At least 3 GB RAM available during frontend builds, with additional capacity for the OS and running services. Start with 4 GB RAM and 20 GB storage, and size up for concurrency and data. Allow space for two releases, Chromium, database/files and independent backups.
  • Outbound HTTPS to licensing.ownebook.com, updater.ownebook.com, dependency registries and your configured service providers.

The managed-server installer and updater described here use root/sudo and systemd. Ordinary shared hosting, including a plan that merely advertises Node.js, is not a supported target for these tools. Hosting, setup assistance, database, AI, email and payment services use your own accounts and are billed separately.

PDF recovery requirements

1.0.17 retains the limited hosting profile's bounded PDF/Chromium queue. Allow MongoDB replica-set transactions and creation of the PDF-check and generation-receipt indexes. Existing records are not bulk-transformed. Multiple backend processes must divide the hosting resource budget; their book leases are coordinated in MongoDB. A free PDF check still needs CPU, memory, readable image/font files and disk space for exports. It does not require an AI request.