slim-skeleton | Slim skeleton app - uses

Your test case is missing but I'd guess that the user you're saving in your test is different from the one you used to set up your mock. For clarification:

Slim skeleton actually demonstrate an example of what you need to achieve. After creating the App instance in index.php, there is an assignment like this:

"Domain" is the main term in DDD (Domain Driven Design) architecture. it has many concepts to learn but in summary, we can say that the Domain section is the core section of your application logic and it contains your domain models and their services like factories and model validations. I suggest you read this reference, it can help you to comprehend DDD concepts.

https://martinfowler.com/tags/domain%20driven%20design.html

Edit: In your example which you mentioned, as you see there is a "User" model in the domain section that there are some of their services like exceptions or interfaces of its repository.

'UserController:getNotification' is not a valid callable based on the code provided. Use either a static function 'UserController::getNotification' or construct UserController and pass array($controller, "getNotification") to $app->get().

Okay I found the solution.

You can use a wildcard OPTIONS request to avoid this issue / error. Below is an example:

Change composer.json

The following steps are necessary for your Slim 3 application to work within subdirectories.

Directory structure:

• public/ Web server files (the DocumentRoot)
  • .htaccess Apache redirect rules for the front controller
  • index.php The front controller
• .htaccess Internal redirect to the public/ directory

The content of the file: .htaccess:

Slim 3 doesn't itself handle database connections. Instead, you need to create a bit of code to do that, either using PDO or mysqli (for MySQL). Look for tutorials and examples on the intertoobz.

Both those database access libraries support connection pooling. So, when you have a whole mess of users hit your slim app, each request handler grabs a shared connection to your database, uses it, and then releases it. If the pool of unused connections gets empty, request handlers will wait, queued up, until a connection is available. All this queuing, grabbing, and releasing is built into the access library.

Unless your requests take a very long time to satisfy, a modest maximum number of connections in the pool--perhaps 10--will serve you very well. (If your requests take a very long time to satisfy, 300 active users will give you more problems than connection pooling.)

Your path /src/classes looks incorrect. It's unlikely your src directory is in the filesystem root.

Change your composer.json file to