Install on Ubuntu 24.04

Installation scope and release status

The downloadable installation framework requires a separately packaged, tested Rhinobase Next application release. It cannot reconstruct application source code or database schema that has not been supplied. Do not enter clinical information until the tested release and your institutional security assessment are complete.

1. Prepare an Ubuntu host

Start with a dedicated Ubuntu Server 24.04 LTS (amd64) host or VM, with administrator/sudo access, stable storage and network access for initial package setup. Consider 2 vCPU, 4 GB RAM and at least 40 GB available disk as provisional planning values, not measured requirements.

2. Run the read-only checker

Download the readiness checker, inspect its contents and run it locally:

bash check-ubuntu-24.04.sh

The checker reports the operating system, architecture, estimated memory and free space, and whether Docker/Compose is present. It does not install packages.

3. Install Docker from the official repository

Follow the current Docker Engine installation instructions for Ubuntu. Install the Engine and Compose plugin. Docker firewall behavior can bypass some UFW expectations; review network binding and firewall rules before exposing services.

4. Obtain the signed-off application release

The installation framework expects a verified .tar.gz bundle containing compose.yaml (or docker-compose.yml) and application artifacts/images specified by the release. Its SHA-256 digest must be published through a trusted independent channel by the project maintainer.

As of this website package, the application release archive has not been supplied. Therefore this step cannot yet be completed using only the public website ZIP.

5. Install when the verified release is available

sha256sum rhinobase-next-release.tar.gz
sudo bash install-rhinobase-next-ubuntu2404.sh \
  --bundle ./rhinobase-next-release.tar.gz \
  --sha256 ACTUAL_PUBLISHED_64_CHARACTER_SHA256 \
  --env /secure/path/site.env

The script validates OS and checksum, checks for archive path traversal, copies the application to /opt/rhinobase-next, and runs docker compose up -d. It never writes placeholder passwords. Provide an operator-owned secrets file with --env, built from the real release’s documented variable names. The installer will refuse missing configuration rather than invent passwords.

6. Verify before patient use

• Use a synthetic account and synthetic patient to test login and role permissions.
• Test creation, reporting, photo management and data import on synthetic records.
• Confirm encrypted network access, firewall isolation and secure server accounts.
• Test database and media backups and restoration.
• Perform institution-specific HIPAA/GDPR/KVKK legal and security assessment, as applicable.

7. Maintenance

Maintain a written change and patch process. Back up before any upgrade. Do not apply the same install script over an existing clinical deployment without first establishing a tested migration and rollback procedure.