API / Minn / Engine

Engine final readonly class

Minn\Engine · public/minn/src/Minn/Engine.php · 335 lines

The engine's front door. An unmodified wp-config.php ends by requiring wp-settings.php, which is the engine's own boot file; it hands off here. REST is dispatched first (from the path or from ?rest_route=), then the admin, the login endpoint, and finally the public site.

Uses 66 (show)

Admin\AdminTypes Admin\App Admin\AppController Admin\Appearance Admin\BootPayload Admin\HiddenIntegrations Admin\Translations Auth\AuthCookies Auth\Authenticated Auth\Authenticator Auth\Capabilities Auth\Cookie Auth\LoginThrottle Auth\PasswordReset Auth\Salts Auth\Sessions Auth\SignIn Content\PostRecord Content\Posts Content\Reader Content\Site Content\SiteIcon Content\Users Context Cron\Cron Db Extension\Extensions Extension\Loader Extension\Seams Front\AdminBar Front\AssetsController Front\CommentPostController Front\FeedController Front\FrontController Front\Permalinks Front\ProbeController Front\Renderer Front\Resolution Front\Resolver Front\SitemapController Http\Failure Http\Kernel Http\Method Http\Policy Http\Request Http\Response Http\Router I18n\Gettext Login\LoginController Login\ServeLogin RestError Rest\Api Rest\RestUrl Rest\Types Runtime\AjaxController Runtime\DebugMode Runtime\Options Runtime\Plugins Runtime\Recovery Runtime\Runtime Theme\ClassicRenderer Theme\ClassicTheme Theme\EmbedRenderer Theme\MainQueryBridge Theme\PageRenderer Theme\Theme

Used by 2

Cli\Runtime Ops\Directory

Constants and properties

const

WP_VERSION = '7.1.3'

The WordPress release whose contracts the runtime speaks; wp-includes/version.php says the same.

private

readonly string $version

Promoted from the constructor.

private

readonly string $engineDir

the minn/ folder: the engine's own files (assets, data, the admin bundle)

Promoted from the constructor.

Public

new	`__construct(string $version, string $engineDir)`#
method	`serve(): void`#	The front door: answer the request that arrived and send it. This is the only place the engine touches the world, so everything under it is a function of a request, callable more than once in a process.
method	`answer(Minn\Http\Request $request): Minn\Http\Response`#	The response for one request, whatever happens: a database that cannot be reached, salts that are not set, or a failure anywhere underneath, each answered in the language the request asked in.

Internals 9

Private and protected methods: how the class does its work. Not a contract; they change whenever the code is tidied.

private	`restRoute(Minn\Http\Request $request): ?string`#	The REST route a request names, in the path or in ?rest_route=, or null when it is not a REST request.
private	`bootRuntimeForRest(Minn\Context $context, Minn\Rest\Api $api, string $route): void`#	The WordPress runtime for a REST request: the caller the REST layer resolved is the reader, plugins load, and rest_api_init fires so their routes answer after the engine's own.
private	`recheckNonce(Minn\Rest\Api $api, Minn\Runtime\Runtime $runtime): void`#	A plugin's nonce lifetime (nonce_life) is heard only once plugins load: a cookie caller's nonce is checked again under it, as the reference checks it. A caller the default lifetime refused was nobody while plugins loaded; when the plugin's lifetime proves the nonce, that user reads the request from here (unless plugin code named someone).
private	`adoptSettledUser(Minn\Rest\Api $api, Minn\Runtime\Runtime $runtime): void`#	The user plugin code settled (determine_current_user) as the REST caller, as the reference's cookie check leaves it: a request a plugin signs in by its own token is that user; a sign-in cookie vouches only for its own user (another one fails its nonce, and without a nonce the request is nobody, plugin code included).
private	`markThemedRequest(Minn\Http\Request $request): void`#	WordPress's index.php says its requests use themes before any plugin loads; its own scripts (sign-in, the admin, cron, XML-RPC) do not, and neither does Minn Admin (probe load-remaining).
private	`armRecoveryPause(Minn\Db $db, Minn\Http\Request $request): void`#	With the database in hand, a fatal during boot can be blamed on the extension it came from; the second inside ten minutes pauses it, so the next request comes back without it. The window in which this applies is opened by Plugins::load. Only a request that carries nothing a visitor chose counts: an extension that fails on some input fails for that input alone, and a visitor could otherwise pause it for everyone with two requests.
private	`plain(Minn\Http\Request $request): bool`#	Whether a request carries nothing a visitor chose but its path: a GET or HEAD with no query, body, upload or cookie.
private	`handle(Minn\Db $db, Minn\Http\Request $request): Minn\Http\Response`#
private	`frontPipeline(Minn\Context $context, Minn\Http\Request $request, Minn\Runtime\Runtime $runtime, Minn\Content\Users $users, Minn\Auth\Cookie $cookie, Minn\Auth\Authenticator $authenticator, Minn\Admin\App $app, mixed $session, Minn\Front\Resolver $resolver, Minn\Front\Permalinks $permalinks, ?Minn\Theme\Theme $theme, ?Minn\Theme\ClassicTheme $classicTheme): Minn\Http\Response`#	The themed front, admin app, and probe pipeline; split out so a mid-request ServeLogin signal can unwind it cleanly.