Run native setup
This is not the recommended way to setup xplex (even as a developer environment), but if you’re feeling adventurous—to build and deploy it without containerization, then here’s how to do it.
Prerequisites
-
Install Dependencies
Depending on the package manager the host system uses, the package names & the commands to install them will vary; please use the appropriate section below:
If you’re on a Debian-based system, using APT as package manager (e.g. Ubuntu, OpenMediaVault, Linux Mint etc.) then run:
If you’re on a Fedora-based system, using DNF as package manager (e.g. RHEL, CentOS, Alma, Rocky, Amazon Linux etc.) then run:
If you’ve chosen to use a system that uses some different & obscure package manager, then you already know what you’re doing and don’t need hand holding to prepare for the build.
Just make sure to update installed packages and then install the build dependencies.
Here’s a generic (and likely non-exhaustive) list of dependencies you may need:
- gcc & g++
- git & wget
- make & autoconf
- perl & perl-modules
- nodejs & nodejs-npm
Good luck!
-
Manage Firewall Rules
xplex uses port
80
for HTTP & port1935
for RTMP. Please make sure the firewall on the host system is configured to allow traffic on these ports.
Setup Script
Inside the directory, there’s a setup.sh
, which automates the tasks to get xplex up and running:
Open a browser & access your xplexHQ dashboard at http://<hostname-or-IP>/
. If you can see the dashboard, then xplex is up and running & ready for the post-installation setup. 🎉