flarum/api.php
Toby Zerner fde00934f8 Change order of bootstrapping
1. Enable database access
2. Load settings
3. Load extensions
4. Load Flarum core/etc

This way, when the app boots, extensions get to register event
listeners for events that may be fired during core/etc's boot process.
2015-07-20 18:02:43 +09:30

39 lines
992 B
PHP

<?php
use Flarum\Core;
use Psr\Http\Message\ResponseInterface as Response;
use Psr\Http\Message\ServerRequestInterface as Request;
use Zend\Diactoros\Server;
use Zend\Stratigility\MiddlewarePipe;
// Instantiate the application, register providers etc.
$app = require __DIR__.'/system/bootstrap.php';
// Set up everything we need for the API
$app->register('Flarum\Api\ApiServiceProvider');
// Build a middleware pipeline for the API
$api = new MiddlewarePipe();
$api->pipe($app->make('Flarum\Api\Middleware\ReadJsonParameters'));
$api->pipe($app->make('Flarum\Api\Middleware\LoginWithHeader'));
$api->pipe('/api', $app->make('Flarum\Http\RouterMiddleware', ['routes' => $app->make('flarum.api.routes')]));
// Handle errors
if (Core::inDebugMode()) {
$api->pipe(new \Franzl\Middleware\Whoops\Middleware());
} else {
$api->pipe(new \Flarum\Api\Middleware\JsonApiErrors());
}
$server = Server::createServer(
$api,
$_SERVER,
$_GET,
$_POST,
$_COOKIE,
$_FILES
);
$server->listen();