Latest Articles

Replacing dot-console with dot-cli based on laminas-cli Implementing dot-cli in your application DotKernel's dot-cli package comes as a replacement for dot-console, which was abandoned after Laminas abandoned their laminas-console package, that dot-console was based on. Setup Install package Run the following command in your application's root directory: composer require dotkernel/dot-cli Register ConfigProvider Open your application's config/config.

CORS policy setup in Dotkernel using mezzio-cors Error message Access to fetch at RESOURCE_URL from origin ORIGIN_URL has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Most developers have encountered this error when interacting with APIs.

As described in this article, dot-log is a powerful tool for logging messages in your application. It's power stays in the fact that it can be implemented in a few easy steps and that it's highly customizable.

Doctrine caching in DotKernel Following version 2 of doctrine/cache, in 2024 we published an update to this article here: https://www.dotkernel.

Dotkernel Admin PHP Application version 3 was launched. Dotkernel is a Collection of PSR-7 Middleware applications built on top of Mezzio microframework and using Laminas components  Dotkernel Admin is a basic admin panel, based on Boostrap ^4.

Dotkernel Frontend PHP Application version 3 was launched. Dotkernel is a Collection of PSR-7 Middleware applications built on top of Mezzio microframework and using Laminas components You can clone it from github Live demo: v3.

This article will walk you through the process of implementing MailChimp into your instance of DotKernel API using drewm/mailchimp-api   Step 1: Add the library to your application using the following command: composer require drewm/mailchimp-api   Step 2: Create configuration file config/autoload/mailchimp.global.

Dotkernel API has come a long way since this post was created. Check out the newest version of Dotkernel API to stay up to date with the latest functional and security features.

This article covers the basic authorization of a Server Side application  built using DotKernel API Protecting an endpoint no-auth: the resource can be accessed without the need of authentication/authorization authentication: the resource can be accessed only by authenticated users authorization: the resource can be accessed only by authenticated AND authorized users Configuring access to the endpoints is done by editing the following config file: config/autoload/authorization.local.

This article covers the basic authorization of a Client application which use a backend built using DotKernel API Authorization Request Client application users send a POST request to the backend containing the following JSON object: { "grant_type": "password", "client_id": "{API_CLIENT}", "client_secret": "{API_CLIENT_SECRET}", "scope": "{SCOPE}", "username": "{USERNAME/EMAIL}", "password": "{PASSWORD}" } Authorization Response If the credentials are correct, the API will return a JSON object containing the authentication data: { "token_type": "Bearer", "expires_in": 86400, "access_token": "..