The server home page is the single bookmark every app on the server opens from. Instead of memorizing the address of each agent and tool, you visit one page and see their cards. It is a static board: MultiAgent builds it from its own database and uploads it to the server, where Nginx serves it at the root /. It needs no container of its own — the installed Nginx is enough — and the page keeps no state at all.
The page has no sign-in of its own. Everything is decided by the central login: when it is on, the root is gated together with the other protected apps; when it is off, the page is open. This way one account unlocks both the board and every app on it.
The “Home page” tab
The tab sits just to the right of the Nginx tab — Nginx is installed first, otherwise there is nowhere to install the board. The tab holds the install, the apply button (a rebuild and re-upload), the page’s public address, the number of cards and the language choice; there are no login and password fields — the page is static and has no sign-in of its own.
What is on the board
The cards are what MultiAgent tracks in its own database. One card per agent, product and tool with an address, with the projects’ real logos: agents carry the Agent logo, apps the logo of their template, tools their own. When there is no logo, the card gets a small square with the first letter of the name.
- Extra link icons — the top-right corner of an agent’s or app’s card shows the icons you set on its “Links” tab: hover to see a tooltip with the link’s title;
- The Git card — appears when Forgejo is installed on the server, and leads to its public subfolder;
- The “Logout” card — the last one on the board. It leads to a confirmation page, after which you are signed out of the central login, of every agent and product (their tokens are deleted) and of the board itself. One click ends every session on the server at once, instead of leaving each app separately;
- Same tab — a card opens in the same tab, and the browser’s back button returns to the board. There are no service elements or settings on the page.
The board is always current
You never edit the page by hand: MultiAgent rebuilds it on every change that touches the line-up of apps — an agent or tool deployed, a record renamed, a link added, the central login turned on or off. The manual apply button runs the same update when you need to catch up. Uploads are frugal: when nothing has changed, the file is not sent again.
The page’s language is chosen on the tab — English or Russian. Without an explicit choice the page renders in MultiAgent’s own language; saving the choice rebuilds the board immediately, with nothing else to do.
If an older home page used to run on the server, the install cleanly removes it and puts the new one in place — every step is visible in the progress feed.
Access and priorities
The board is served at the server’s root, and the app subfolders always take priority: an agent with the slug settings is served at /settings/, while the home page keeps working at the root. The board is just static files handed out by Nginx: if Nginx is stopped, the board goes down with it, but the app containers themselves keep running untouched.