Self-hosted distribution

Download & installation

Resources for deploying Rhinobase Next on an Ubuntu 24.04 LTS server controlled by your institution.

Release status: This website package includes a functional host-readiness checker and a release-bundle installer framework. It does not include the Rhinobase Next application source, database schema, container images or a verified production release archive. An application download must not be advertised as ready until those components are packaged and tested.

Available · shell script

Ubuntu 24.04 readiness checker

Checks supported OS, architecture, memory, disk availability, Docker availability and selected network exposure indicators. Does not modify the server.

File: check-ubuntu-24.04.sh
Download .sh ↓
Available · requires separate release

Rhinobase Next installer framework

Validates your local application archive and SHA-256 checksum, copies the verified release into /opt/rhinobase-next and starts its Docker Compose stack. Requires a tested application release and a private environment configuration file.

File: install-rhinobase-next-ubuntu2404.sh
Download .sh ↓
Not yet included

Rhinobase Next application release

The actual deployable application archive must be built from the current verified source tree. No placeholder package or invented download address is provided.

Minimum planning requirements

Operating systemUbuntu Server 24.04 LTS (amd64)
Processor64-bit processor; 2 vCPUs as a provisional planning baseline
Memory4 GB RAM provisional baseline; 8 GB recommended for larger installations
Storage40 GB free for the application baseline, plus separately sized clinical media and backups
RuntimeDocker Engine and Docker Compose plugin required by the installer framework
NetworkPrefer private LAN/VPN, firewall, HTTPS/TLS for user access; do not publicly expose PostgreSQL
AdministratorRoot/sudo access for installation, a designated administrator for ongoing maintenance

Hardware sizing above is provisional, not a measured production benchmark. Validate against the actual application archive and expected user/media volume.