Copy traits ProvidesConvenienceMethods from laravel/lumen-framework/src/Routing to your folder as convenient. Eg, App\Services folder.

namespace App\Services\product;

use App\Models\Products\Product;

use App\Services\ProvidesConvenienceMethods;

class ProductCreateService
{
    use ProvidesConvenienceMethods;

    public function store($request)
    {       
        // validate request data
        $product_data = $this->validator($request->all(), [
            'name' => 'required|string|min:1|max:255',
            'sku' => 'required|string|min:1|max:120',
            'qty_available' => 'numeric|required|min:1',

            // validate each array element if array items
            'items.*.sku' => 'required|string|min:1|max:120',
            'items.*.qty_required' => 'numeric|required|min:1',
            'items.*.item_price' => 'required|regex:/^\d+(\.\d{1,2})?$/'
        ]);

According to the documentation: “By default, Lumen’s base controller class uses a ProvidesConvenienceMethods trait which provides a convenient method to validate incoming HTTP request with a variety of powerful validation rules.”

Reference: https://lumen.laravel.com/docs/8.x/validation

Hope this helped someone out there.

The post Laravel Lumen API Validation in Service Class appeared first on .

{
    "name": "Test Bundle",
    "sku": "SKU123",
    "qty_available": "2",
	"items":[
        {
            "sku": "SKU123-1",
            "qty_required": "1",
            "item_price": "32.00"
        },
        {
            "sku": "SKU123-2",
            "qty_required": "1",
            "item_price": "12.00"
        }
    ]
}

Validation in laravel:

// validate request data
        $bundle_data = $this->validate($request, [
            'name' => 'required|string|min:1|max:255',
            'sku' => 'required|string|min:1|max:120',
            'qty_available' => 'numeric|required|min:1',

            // validate each array element if array items
            'items.*.sku' => 'required|string|min:1|max:120',
            'items.*.qty_required' => 'numeric|required|min:1',
            'items.*.item_price' => 'required|regex:/^\d+(\.\d{1,2})?$/'
        ]);

Hope this helped someone else.

Reference: https://stackoverflow.com/questions/42258185/how-to-validate-array-in-laravel

The post Laravel Lumen API Validate Json Array appeared first on .

bin/magento setup:upgrade

using bin/magento

If you sees this error:

 Can't run this operation: deployment configuration is absent. Run 'magento setup:config:set --help' for options.

Please check whether your two files are exist:

1. app/etc/env.php
2. app/etc/config.php

Next, check the settings of dababase and redis connection information, credentials are correct.

Once the above are correctly set, rerun the command

bin/magento setup:upgrade

You might face another error

Fatal error: Uncaught Error: Cannot instantiate interface Magento\Store\Api\StoreRepositoryInterface

When seeing this error, do run another command below:

php -dmemory_limit=-1 bin/magento setup:di:compile

Note, using “-dmemory_limit=-1″ is so that you won’t get “Allowed memory size of 134217728 bytes exhausted” error.

Hope this helped someone out there.

The post Magento 2 Error Can’t run this operation: deployment configuration is absent. appeared first on .

$ php-fpm

Below error:

ERROR:failed to open configuration file ‘/private/etc/php-fpm.conf’: No such file or directory..

It is due to the configuration file with the path /private/etc/php-fpm.conf and the file does not exist.
To solve this cp /private/etc/php-fpm.conf.default /usr/local/etc/php-fpm.conf
After copying this file, you need to modify some of the things in this php-fpm.conf file

1.  ; Note: the default prefix is /usr/var
2. ; Default Value: log/php-fpm.log
3. error_log = log/php-fpm.log

Note that there is an error_log, the default directory is /usr/var/…, but there is no such path in the mac directory, so if you run php-fpm at this time, you will get an error:

1.  $ php-fpm –fpm-config /usr/local/etc/php-fpm.conf
2.  ERROR: failed to open error_log (/usr/var/log/php-fpm.log): No such file or directory

We can modify this configuration code:

error_log = /usr/local/var/log/php-fpm.log

Similarly, modify the pid:

pid = /usr/local/var/run/php-fpm.pid

Note that the last line of this configuration file is:include=/private/etc/php-fpm.d/*.conf
will read all files in the /private/etc/php-fpm.d/ directory with the .conf suffix, and the .conf file does not exist, so we copy one directly. /private/etc/php-fpm.d/www.conf.defaultIs /private/etc/php-fpm.d/www.conf.Just fine.

Run:
$ php-fpm –fpm-config /usr/local/etc/php-fpm.conf
If an error occurs:
ERROR: unable to bind listening socket for address ’127.0.0.1:9000′: Address
This shows that 127.0.0.1:9000 has been bound and can be resolved by the command killall php-fpm

The post MAC Big Sur NGINX Installation PHP-FPM error appeared first on .

You can see password validate configuration metrics using the following query in MySQL client:

SHOW VARIABLES LIKE 'validate_password%';

The output should be something like that :

+--------------------------------------+-------+
| Variable_name                        | Value |
+--------------------------------------+-------+
| validate_password.check_user_name    | ON    |
| validate_password.dictionary_file    |       |
| validate_password.length             | 6     |
| validate_password.mixed_case_count   | 1     |
| validate_password.number_count       | 1     |
| validate_password.policy             | LOW   |
| validate_password.special_char_count | 1     |
+--------------------------------------+-------+

then you can set the password policy level lower, for example:

mysql> SET GLOBAL validate_password.policy = LOW;

The post MySQL Your password does not satisfy the current policy requirements appeared first on .

You may see this error after installed Kubernetes and run “brew doctor”.

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
kubernetes-cli

It can be solved by running below after installing kubectl with brew on macOS.

$ rm /usr/local/bin/kubectl
$ brew link --overwrite kubernetes-cli

The post Mac OSX Kubernetes Run `brew link` on these: kubernetes-cli appeared first on .

Illuminate\Database\QueryException SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client

This issue has been fixed in PHP7.4, please install PHP7.4 in the Droplet. If you are running on NGINX:

## install php7.4 fpm
$ sudo apt install php7.4 php7.4-fpm

## install php7.4 mysql
$ apt-get install php7.4-mysql

After that, update the NGINX sites configuration to the correct PHP-FPM version.

fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;

This should allow you to connect your Laravel 7 application to Digital Ocean’s managed database MySQL version 8.

This post may not 100% fix your situation, hope to bring some idea to this MySQL 8 issue in the managed database.

Few points to note :

• DO Managed database cluster default MySQL version is 8.0, no option to select down.
• MySQL 8.0, upgraded the password encrypting to caching_sha2_password.
• In the managed database, if necessary create a new database username with Legacy – MySQL 5.x.
• Ubuntu MySQL client has only version 5.7. If necessary, you need to manually install MySQL version 8 client.
• Droplet Ubuntu version is 18.04.4 LTS.

The post Laravel 7 Digitalocean managed database error: The server requested authentication method unknown to the client appeared first on .

$ composer create-project --prefer-dist laravel/laravel   my-project
(NOTE: if you do not have composer, please install in your machine and make it global. 
This will make a lot easier)

$ git clone <your repo>

$ npm install

$ composer install

$ php artisan key:generate

$ php artisan passport:keys

To simplified, do below 5 steps for get Laravel with NPM modules such as Vue JS.

$ npm install

$ composer install

$ cp .env.example .env

$ php artisan key:generate

$ php artisan passport:keys

The post Laravel & NPM installation Steps appeared first on .

AddType text/css .css 

this will tell apache to send the right content-type header for .css file

On my case, the above won’t work at all. My own hosted Ubuntu needs below changes so that is will works.

Check your

/etc/apache2/apache2.conf

If there are any

SetHandler application/x-httpd-php

line, try to comment it and then reload your apache by $ sudo system apache2 reload

Reference: https://stackoverflow.com/questions/10553638/resource-interpreted-as-stylesheet-but-transferred-with-mime-type-text-html

The post PHP Apache2 Laravel Resource interpreted as Stylesheet but transferred with MIME type text/html: “ appeared first on .

$ curl -sS https://getcomposer.org/installer | php
$ mv composer.phar /usr/local/bin/composer
$ alias composer=’/usr/local/bin/composer.phar’

However, it could still happen to have error of

“Could not open input file: /Users/kayliongmac11air/composer.phar“

This is due to shell environment didn’t refresh.

To fix this error, simply run below command:

source ~/.bash_profile

This will refresh the shell environment in your OSX environment.
That’s it, now the alias will take effect.

The post Mac OSX Composer Could not open input file: /Users//composer.phar appeared first on .