LJLR

Layered Job Loader & Runner

LJLR by ULXI
LJLR
—
Loading…

Cluster nodes every process pointed at this platform database

A node joins by pointing at the control plane and declaring its roles — install.sh --apply --join <db-host> --roles <names>. Nodes are never deleted from this list; one that stops reporting shows as stale, so a box that vanishes leaves evidence.

Modules what this node loaded, and what it refused

Not loaded

Jobs newest first

Recent events

Health startup preflight, cluster liveness, parked work

Preflight

Dead jobs out of retries — these need a human

Updates

—

Installed

My settings your account on this platform

Profile

Your username and your role are an administrator’s to set — changing your own role is not a feature.

Change password

Changing your password signs out every other session on this account. This one keeps working.

Appearance

Dark is the default. Your choice is remembered in this browser and beats the operating system setting.

Signed in

Your workspace is JANIS — the hub this platform is being built to land you on: people and companies, today, reach and work, in one place.

It is not built yet. This account is real, your sign-in works, and nothing administrative is visible to you by design. When JANIS ships, this is where it appears.

LJLR by ULXI

System settings how this platform is set up — administrators only

Accounts who can sign in, and as what

Add an account

Leave unticked for a client account: it can sign in, and sees nothing administrative.

Active sessions

API & integrations

Nothing here yet — and nothing is switched off, it is simply not built. This is where API tokens, per-module settings and credential references, OIDC, and webhook ingress will live when they exist. Named now so they have an address instead of an argument.

Sign-in methods

Modules what this node loaded, and what it refused

Read-only, because there is nothing yet to choose between. Modules are discovered through Python entry points; none is installed on this node. Turning one on and off arrives with the first real module — a switch over an empty list would be a control that does nothing.

This instance

Read-only in this build. These are real settings; today they change only in ljlr.env, which is what this surface exists to end.

Front door how requests reach this node

Changing the hostname is not a text box. It rewrites the nginx server name, requests a new certificate from a rate-limited authority, and changes the address every existing session was issued against — so it runs where it can be seen and undone: bash /root/ljlr-build/installer.sh → Fix HTTPS. The addresses above are read from the machine, and the certificate is read off the wire rather than off disk — what a browser is actually handed, not what we believe we installed.