Skip to content
Maran

Getting started

Installation

Installing Maran on a fresh server, what the installer checks first, and how the first administrator is created.

Install on a server you control, with root access, running one of the supported platforms.

Run the installer

bash
curl -sSL https://get.maran.innovayse.com | sudo bash

The installer verifies the system before changing anything: the distribution and its version against the supported matrix, the RAM and disk floors, and the ports it needs. It collects every failure before exiting, so you can fix the whole list at once instead of re-running the installer for each problem. Free space for backups is only a warning: when the filesystem that will hold them has less than 10 GiB free, the installer says so and carries on.

If the checks pass, it installs signed release artifacts, hardens the systemd units, and sets up the pieces a hosting server needs: the web server, PostgreSQL for the panel's own data, the database server for hosting accounts, file transfer, the firewall and the scheduler.

The installer records the server's host name in panel.env (Panel__HostName) and uses it as the panel's server_name. If the host name is unusable (empty, localhost, or containing characters other than letters, digits, dots and hyphens) nothing is recorded and the panel answers on localhost. Re-running the installer after fixing the host name updates both.

Installing without internet access

A server that cannot reach the download host installs from a bundle carried to it. The bundle is one file, made by maran release package from a release that was built for the server's architecture (maran release build) and signed (maran release sign). Copy it to the server and, from the unpacked installer package, pass it to the installer:

bash
sudo bash install.sh --offline-tarball <bundle>.tar.gz

A bundle holds the signed manifest, the code-integrity list with its signature, and the three archives (the API, the agent and the panel interface). The installer verifies the manifest's signature and each archive's checksum against its manifest entry before it unpacks anything, and checks each checksum again immediately before extracting that archive. A bundle that fails either check stops the install.

The first administrator

When installation finishes, the installer prints a link to the setup page and, on its own line, a one-time setup token. Open the link and paste the token into the token field. This is the only way to create the first administrator account. The token is deliberately kept out of the link, and it stops working as soon as the panel has a user. If you lose it, read Setup__Token from /etc/maran/panel.env as root.

After the first sign-in

Turn on two-factor authentication, then create your first hosting account. An account is a real Linux user with its own home directory, its own php-fpm pool and the plan's disk quota; creating one through the panel is what provisions it on the host.

Updates

To update, run the installer again. It is safe to repeat. It fetches the current signed release, verifies the signature and every checksum before unpacking, and applies each module's database migrations before the panel starts. There is no one-click update in the panel yet and no maran rollback command, so take a panel backup first (see Panel backup and restore); restoring that archive onto a clean install is the way back. Maran does not configure automatic operating system updates.