Skip to content
Maran

beta · 23 September 2026

Maran 1.0.0-beta.2: an installer that installs

A repair release. beta.1 could not finish an install on any Debian-family host; this fixes it. The panel, agent and SPA are unchanged from beta.1.

This is a repair release and nothing more. The panel, the agent and the SPA are byte for byte the same as in 1.0.0-beta.1. The only change is that the installer now gets past PostgreSQL.

What was wrong with beta.1

It could not complete an install on any Debian-family host. The packages installed, initdb created the cluster, and the installer then refused:

text
30-postgresql.sh: could not locate postgresql.conf

The file was exactly where Ubuntu puts it. The step searched /etc/postgresql only two levels deep, but Debian and Ubuntu put the file three levels down, at /etc/postgresql/<major>/<cluster>/postgresql.conf. Both resolvers had this bug, the one for postgresql.conf and the one for pg_hba.conf, so beta.1 could not finish on any such host.

It was published because the project's container harness copies that step into its image and never runs it: the image installs MariaDB, not PostgreSQL. Nothing had ever run the resolver against a real Debian layout. That is now covered. The test also checks that the old depth fails on the same directory tree, so it cannot pass against the very bug it was written for.

Known defect still in these artifacts

The installer cannot read the artifact URL out of the release manifest. After the manifest's signature verifies, the step reports:

text
50-artifacts.sh: manifest has no entry for api-x86_64

The entry is in the file. The reader matched a quoted value only at the end of a line, but every JSON field except the last in its object is followed by a comma, so it returned nothing for the URL.

This is fixed in the source but is not in the beta.2 artifacts, so an install from the published manifest will hit it. The next beta carries the fix.

Installing

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

The beta limits have not changed: no certificate has been issued by a real certificate authority, no disk limit has been enforced by a real filesystem, and no restore has been run on real hardware. Do not put somebody else's customers on it.