pastilhasandClaude Opus 5
b27969ba57
It is the same KIND of thing as the root location and the databases — this machine, not the site's content — and a nav row leading to one card was a whole screen to reach three lines. Last of the three, because it needs both of the others: a server has nowhere to run without the checkout and nothing to read without a database. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
31 lines
1.3 KiB
TypeScript
31 lines
1.3 KiB
TypeScript
import { RootLocationBlock } from './RootLocationBlock';
|
|
import { DatabaseBlock } from './DatabaseBlock';
|
|
import { ServersBlock } from './ServersBlock';
|
|
|
|
/**
|
|
* Administration — this plugin's own machinery, not the client's site.
|
|
*
|
|
* A list of blocks, and nothing else. Each one owns its own heading, its own state and its own status
|
|
* message; this file decides only which of them exist and in what order.
|
|
*
|
|
* The order is the order things are needed in: where the site is on this machine, then how to read its
|
|
* data, then the processes that serve it — which need both. Building `derived/` from `originals/`
|
|
* lives with the folders it acts on, inside Root Location, rather than as a section here describing the
|
|
* same two directories a second time.
|
|
*
|
|
* ── What used to be here ──
|
|
*
|
|
* An address and a token: where fofos is, over HTTP. That is gone from the screen. The server half is
|
|
* untouched — `/_config` still stores a URL and a token, and the proxy in `api/router.ts` still reads
|
|
* them — but nothing can set them, which is why `useReady` stays hardcoded false and every other
|
|
* section stays locked. The two are the same unfinished change.
|
|
*/
|
|
|
|
export const AdministrationPanel = () => (
|
|
<div className="flex size-full flex-col gap-4 overflow-auto p-5">
|
|
<RootLocationBlock />
|
|
<DatabaseBlock />
|
|
<ServersBlock />
|
|
</div>
|
|
);
|