$errorMiddleware = $app->addErrorMiddleware($config['error']['debug'], true, $config['error']['log']['communication']);
$errorMiddleware->setDefaultErrorHandler($container->get(ErrorHandler::class));

It works, but every now and then I got a fatal error, which is rendered by the default HTML renderer and I guess it is not logged as well. Is there a way to handle fatal errors with a custom error handler?

I know from my own frameworks, that this is a tricky question, because if the custom handler raises an error, then the code can collapse into an infinite error loop… But I still want to do this.

and this is how a module looks like:

as you can see both in terms of structure “parent” (application) and “child” (module) they are identical, an hooking module to your application is as easy as:

As you can see there is 6 modules (as composer packages) hooked to the monolith `OllamaAssistant`.

Monólito modular é outra história

como eu poderia criar módulos autocontidos e independentes com o Slim?
penso em fazer isso para reaproveitar módulos em vários projetos.

./psr-worker.php

<?php

declare(strict_types=1);

require './vendor/autoload.php';

use Dhosting\AiCrowd\Common\StdLogger\ThrowableMessageFormatter;
use Dotenv\Dotenv;
use Nyholm\Psr7\Response;
use Nyholm\Psr7\Factory\Psr17Factory;
use Psr\Container\ContainerInterface;
use Slim\App;
use Spiral\RoadRunner\Worker;
use Spiral\RoadRunner\Http\PSR7Worker;

$dotEnv = Dotenv::createImmutable('./');
$dotEnv->load();

require './bootstrap/bootstrap.php';

if (isset($app)) {
    $worker = Worker::create();

    $factory = new Psr17Factory();

    $psr7 = new PSR7Worker($worker, $factory, $factory, $factory);

    while (true) {
        try {
            $request = $psr7->waitRequest();
            if ($request === null) {
                break;
            }
        } catch (Throwable $t) {
            try {
                $psr7->respond(new Response(200, [], $t->getMessage()));
                error_log(ThrowableMessageFormatter::format($t));
            } catch (Throwable $t) {
                error_log(ThrowableMessageFormatter::format($t));
            }
            continue;
        }
        try {
            /** @var App<ContainerInterface> $app */
            $psr7->respond($app->handle($request));
        } catch (Throwable $t) {
            try {
                $psr7->respond(new Response(500, [], $t->getMessage()));
                error_log(ThrowableMessageFormatter::format($t));
            } catch (Throwable $t) {
                error_log(ThrowableMessageFormatter::format($t));
            }

            $psr7->getWorker()->error((string)$t);
        }
    }
}

./bootstrap/bootstrap.php

<?php

declare(strict_types=1);

use DI\ContainerBuilder;
use Slim\App;

$builder = new ContainerBuilder();
$builder->useAutowiring(true);
$definitions = array_merge(
    require './config/settings/settings.php',
    require './config/dependencies/dependencies.php',
);
$builder->addDefinitions($definitions);
$container = $builder->build();

$app = $container->get(App::class);

require './bootstrap/middleware.php';
require './bootstrap/routes.php';

./rr.yaml

version: '3'
server:
  command: "php psr-worker.php"
http:
  address: 0.0.0.0:80
  pool:
    num_workers: 1
    debug: true

and finally trigger the roadrunner server:

./rr serve -c .rr.yaml

According to @LLEGAZ’s constructive remark

web app standard (AJAX, even if it’s old fashioned it works well)

I replaced AJAX with Fetch API slim4-foto-kit/public/js/admin at master · emyca/slim4-foto-kit · GitHub .
And yes, I remain jQuery in the project. I think it’s more convenient than vanilla JS. Also I’d like not to use any JS framework to be minimalistic as much as I can. A sentence “jQuery is dead” looks like “PHP is dead”, but reality is another for now.
Thank you.

UPD: You can find AJAX-way here slim4-foto-kit/public/js/admin at first-release · emyca/slim4-foto-kit · GitHub

UPD2: Recent news - jQuery has its final release 4.0.0 https://blog.jquery.com/2026/01/17/jquery-4-0-0/. It’s really not dead)

and what makes it stick is how light and flexible it is. There’s no bloat, middleware is easy to connect, and routing is a breeze compared to full-stack frameworks like Laravel.

How come above would be a contraindication to carry out large projects?

The hard part is scaling past a few endpoints. You have to be smart about caching and dependency injection, or performance will drop.

Are we still talking about Slim? I have an impression you just copy/paste something you heard/read around. It is Slim that allows you to solve all mentioned by you obstacles in ways impossible for other enterprise frameworks.

Speaking about the size, I had exactly two, quite a big enterprise challenges made with Slim, and it was a metaphysical experience, especially that one of them it was a complete rewrite of a Symfony6 hyped approach (although I may have exaggerated a bit with the enterprise thing, it was certainly nor Meta neither Netflix ) In any case, these were big enough projects to make an impression.

… but don’t try to fit a huge monolith into it.

This is more kind of a general remark not particularly related to Slim. Don’t try fit a huge monolith into anything. Modular monolith, is another story. Slim is perfect for that.

Finally to get to the point, would you share your experience and justify why wouldn’t you write anything big with Slim?

… ActionControllerInterface

It’s interesting to see its code. Interface of Action plus Controller.

class ActionController…

If it’s invokable class with some action, may be it can be named just SomeAction instead of weird ActionController.

…
public function __construct(
protected JsonResponderInterface $responder
) {
…

What about response of not only JSON format? Action response can be an HTML-page.

My comments are not from AI.

It is worse. You don’t even understand what you copy/pasted pal.

Everything can be used. But untill some measure. Nothing can replace real knowledge. AI, for today and in some way, is mostly aggrigator and translator of some knowledge pieces. My comments are not from AI. If you do not believe, it’s up to you. I’ve seen just some chunk of your code. It’s nothing.

@tj_gumis you should train your softskills.

And I agree with @LLEGAZ . Peace for all of us.

@LLEGAZ does not even know it is AI performance.

and they claim to be good enough to evaluate my code. Wtf???

What a waste of time with both of you.

Peace on you both guys, and on your families.

// As I can see ActionController may be some basic 

// for concrete Action controllers. 

// It's interestig to see subtypes of ActionController.

// Also, it's interesting to see ActionControllerInterface.

// Interfaces are abstraction, tools for polymorphism.

class ActionController implements ActionControllerInterface

{

    public function __construct(

        // DI in action.

        // And this is injected with constructor-injection. 

        protected JsonResponderInterface $responder

    ) {

    }




    // Good.

    // As PHP docs say: "The __invoke() method is called 

    // when a script tries to call an object as a function."

    // PHP's way of supporting pseudo-first-class functions.

    // Why? Code clarity.

    public function __invoke(

        // It's Psr\Http\Message\ServerRequestInterface

        ServerRequestInterface $request,

        // It's Psr\Http\Message\ResponseInterface        

        ResponseInterface $response,

        // Why it's here? 

        // Can it be injected in the class constructor? If not, why?

        ActionServiceInterface $actionService,

    ): ResponseInterface {

        return ($this->responder)(

            $request,

            $response,

            $actionService,

        );

    }

}

All in all it’s quite funny everybody was thinking that somebody was lacking humility among other virtues.

Maybe we should all breath a good one and remember we are only human after all.

Plus, I hope, PHP friends.

Please, have a good week (I really mean week not weak this time ^^) and have some fun.. And thank you both for that discussion. I am quite sure you are real humans now xD

Обирай союзників мудро. Не сери на руку, яку хтось тобі безкорисливо простягає.

Otherwise, just like in this case, you will be always left alone. Tapping your shoulders is worthless, but constructive criticism might be priceless.

This small advice is all I can do for you.

You will never achieve anything without humility. Stay humble whole your life, no matter your age, and it will help you to reach any goal much faster.

edit to TJ : not saying mad as an insult against you, just mad like all the world is made lately.. I’m too

I’m not even that french, just french not french french. I can understand (a bit) why you are mad but please don’t take all this too seriously (especially my jokes..)

Please gentlemen can we talk PHP here ?

@tj_gumis stollatz
@EugeneM dobayov ?

(sorry I need some lessons on all those languages too)

My people are wining time now for your people.

Most of your people passing the boreder in 2022, openly admitted they would never do the same for my people.

So no, your people do nothing for my people, your people do everything for themselves, not for anybody else. This statement is just a tool to play with our conscience to force our guilt and obligation.

土も ありがと よ

Touché.

By the way, I am Pole, so don’t forget about “fascist”, “homophobe” or “islamophobe”.

It will be complete, Frenchie.

Tu sais quoi, je jetterai une perle aux pourceaux. The first one, and the last one.
No AI will ever generate anything like that for you, the same as you would never imagine it can be done like that:

class ActionController implements ActionControllerInterface
{
    public function __construct(
        protected JsonResponderInterface $responder
    ) {
    }

    public function __invoke(
        ServerRequestInterface $request,
        ResponseInterface $response,
        ActionServiceInterface $actionService,
    ): ResponseInterface {
        return ($this->responder)(
            $request,
            $response,
            $actionService,
        );
    }
}

Thanks to such ruzzian bots, like me and my people, your people are where they are nowadays. Unfortunatelly after what you and your people say we might not do the same next time.

@tj_gumis , tell us the truth. Show your first class code.

Hey, @tj_gumis. Are you US AI bot?

maybe crappy code like mine is still better than non existing one like yours.. just saying

And btw I’m quite pretty confident that all your so called “expertise” is powered by an US AI so.. keep it to yourself, I can too use an AI if I want a good feeback but again thanks for nothing especially for your kindness and your stagecoach

I have never said my code is great, but with a full responsibility I can say your code is a crap.

Say one more word, and I will gladly put into pieces the first controller in your code.

Believe me or not it will be quite embarrassing for you.

With no regards.

Best regards,

I was just answering Eugene that I had too a slim demo project on my github.

Still. Thanks anyway.

With no effort of searching, first class in your project folder tree: zelty-php-test/src/Authentication/TokenStore/TokenStore.php at 92ce357ff36d7db85f24abac26d05b564ffd2090 · llegaz/zelty-php-test · GitHub

I did not even bother to go any further. It would be a waste of time.

Next time, instead of finding anything offensive, just take your chance, and say nothing.

Especially good quality any best practices applied from below:

Just with a 1 or 2 glimpses of the code I can see :

• good quality

• well documented

• best practices applied.

• web app standard (AJAX, even if it’s old fashioned it works well)

• JWT to manage authentication (not a bad standard at all + ‘httponly’ => true, // prevent XSS which is a good point with the short, 15min duration for the token I think..)

Gosh, it is so sweet of you

If you start answering philosophically then I will too.

There is only one good, knowledge, and one evil, ignorance.

Socrates (~ 420-410 av. J.-C.)

But yes, I’m also very curious (dubious) about what M. has to teach us.

From my point of view when you are talking of “week code” (le code de la semaine ?), by weak I think you mean secure and again, from my side, his code appears secured enough for a demo project (JWT implemetation looks OK, but I didn’t test it or in depth analysis, not even using AI to audit it completely = yes I’m that lazy).

Just with a 1 or 2 glimpses of the code I can see :

• good quality
• well documented
• best practices applied.
• web app standard (AJAX, even if it’s old fashioned it works well)
• JWT to manage authentication (not a bad standard at all + ‘httponly’ => true, // prevent XSS which is a good point with the short, 15min duration for the token I think..)