First-run setup
On this page
After the install, Moorhold's setup pages take you from a one-time setup code to your first dashboard. This page walks through them. The steps are the same on every provider and on your own server.
Before you start
Section titled "Before you start"-
Moorhold is installed and both DNS records point at the server. See Requirements and your provider's install guide.
-
You have the one-time setup code. A terminal install ends with the command to read it. After a cloud install, open the server's console in your provider's panel, sign in as root, and run:
Terminal window cat /etc/moorhold/secrets/MOORHOLD_SETUP_CODEThe file is readable by root only, and the code is never written to the install's log. If the file isn't there, the server is still installing, so wait and try again.
- On Who are you?, enter the setup code and set your admin password. Go to
https://data.yourorg.example/setup, using your own address, and enter the setup code. On the same screen, set a password of at least 16 characters. If your organisation's sign-in isn't connected, as on a new install, setup also asks for your name and email, so your server's own sign-in service has them when you first sign in. - On Your organisation's sign-in, connect Microsoft Entra ID, Google or Okta, or skip it and use Moorhold's own accounts. Setup asks for your provider's client secret as a reference, never as a value.
- Get to your first dashboard. Choose how to start.
- Explore the sample data opens a ready-made dashboard in Superset, built from a snapshot of real public data about AI models that includes Epoch AI's data under CC BY 4.0. While the sample is loading, setup shows how far it has got and offers the dashboard once Superset has it. The sample also comes with an optional lesson, Build your first pipeline, in four short steps.
- From 2026.10.16, a new server has the sample only if the installer was asked for it. If it
isn't there, setup offers Download the sample data under "See what Moorhold can do first".
From 2026.11.2, an admin presses it and the request is approved as they ask, so one admin is
enough. A request from an earlier release that's still waiting can be approved by any admin. Adding the sample restarts Airflow's scheduler, so a pipeline that's
running at that moment stops, and the page says so. On 2026.10.16, setup says the load takes
about 10 minutes, but on our test server it took about 15 minutes from approval. From 2026.11.2
it says about 15 minutes on a server, and about 2 minutes in the Mac app. Where it can't tell a Mac from a
server, it gives both figures. If your server can't
act on the request, setup shows the one command to run in the server's console instead,
sudo moorhold sample-data add, with a Check again button. On 2026.10.13 and 2026.10.14, a new server has the sample unless the installer was told to leave it out. - Connect your own data brings in a web service (a REST API). Setup offers no Postgres
database on an installed server. Someone with root puts the API's extractor in
/opt/moorhold/codeand makes it readable withsudo chmod -R a+rX /opt/moorhold/code, adds the extractor's module toentrypointPrefixesin/opt/moorhold/stack/stack.yamland puts the API's key in a file directly in/etc/moorhold/secrets, named with letters, digits and underscores. An admin adds the source on the Sources page, and someone with root runssudo moorhold applyonce. The Add a web service guide gives these steps in full.
- Select See the sample dashboard, in Apache Superset, once the sample has loaded. Superset
opens at
https://superset.data.yourorg.examplewith the sign-in you already have.
On the core profile there's no dashboards tool, so setup ends at the portal instead of Superset. From 2026.10.16, the portal's Assets page on a core server searches its own tables, marts, pipelines and checks by name and description.
Next, see Your first dashboard.
The account setup makes
Section titled "The account setup makes"The admin account you make in setup is your server's own account. It signs you in to the portal and the tools on that server. It's separate from your Moorhold account at account.moorhold.dev, which is only for downloads and access keys.
If something goes wrong
Section titled "If something goes wrong"/setupdoesn't open. Check that both DNS records are correct and that ports 80 and 443 are open, then check in your provider's console that the server is running. The certificates may not be ready, so wait and try again./setuprefuses the code. Read the file again. A code works only until the admin password is set.- The portal opens, but Superset doesn't. The wildcard record (or the three tool records) is probably missing.
If you're still stuck, email hello@moorhold.dev and say which step you reached.