<h2>What is laravel pint</h2>as in the defination by the official repository,<blockquote>Laravel Pint is an opinionated PHP code style fixer for minimalists. Pint is built on top of PHP-CS-Fixer and makes it simple to ensure that your code style stays clean and consistent.</blockquote><blockquote>-- laravel/pint</blockquote>and as per me, Pint is the so far most sophisticated code formatter i have ever user in the reference of PHP. You can find more details about <a href="https://github.com/laravel/pint" rel="noopener noreferrer">laravel/pint here</a>. <h2>Installation</h2><pre class="ql-syntax" spellcheck="false">composer require laravel/pint --dev
</pre><h2>General Usage</h2>to use the pint binary all you have to do is run the following command in the root of you laravel project.<pre class="ql-syntax" spellcheck="false">./vendor/bin/pint
</pre><h2>Configuration</h2>The default setup of laravel pint does not require any configuration and as per the official docs, it for <a href="https://www.php-fig.org/psr/psr-12/" rel="noopener noreferrer">PSR-12 Style Guide</a>. Still if you are unhappy with some default rules you can change then by creating a<code> pint.json in root of your project</code>, and adding the preset to it.Currently the following preset are supported<ol><li>psr12</li><li>laravel</li><li>symfony</li></ol>Since Pint is based on PHP-CS-Fixer the configuration rules can be found <a href="https://mlocati.github.io/php-cs-fixer-configurator/#version:3.8" rel="noopener noreferrer">here</a>.<h3>Sample pint.json</h3><pre class="ql-syntax" spellcheck="false">{
 "preset": "symfony",
 "rules": {
 "concat_space": {
 "spacing": "one"
 }
 }
}
</pre><h2>Binding laravel pint with VS Code</h2>So far we are good to use laravel/pint, but opening terminal and running a binary everytime you need to format id one hell of a job. To reduce that effort we will bind laravel/pint with our VS Code with the help of VS Code Task<h2>Creating VS Code task for laravel pint </h2><ol><li>To create a task create a <code>.vscode directory in root of you project</code>, if you don't have one.</li><li>Add a <code>new file named as tasks.json</code> to .vscode directory</li><li>add the following content to the new created file</li></ol><pre class="ql-syntax" spellcheck="false">{
 "version": "2.0.0",
 "tasks": [
 {
 "label": "Pint Formatter",
 "type": "shell",
 "command": "./vendor/bin/pint",
 "problemMatcher": [],
 "presentation": {
 "reveal": "silent"
 },
 "group": {
 "kind": "build",
 "isDefault": true
 }
 }
 ]
}
</pre>You can run this task directly from the <code>Tremial -&gt; Run Tasks</code> from the navigation, but will do it a bit more simpler.<h2>Adding KeyBinding (Keyboard Shortcut) to Run laravel pint</h2><ol><li>Open Keyboard shortcut panel, either from <code>file -&gt; preferences -&gt; keyboard Shortcuts</code> or <code>Ctrl+k Ctrl+s</code></li><li>Ones open click on the file icon on the top to open the json file of the keyboard shortcuts.</li><li>Ones open add the following lines to the file.</li></ol><pre class="ql-syntax" spellcheck="false">[
 {
 "key": "ctrl+shift+l",
 "command": "workbench.action.tasks.runTask",
 "args": "Pint Formatter"
 }
]
</pre>Now all you have to do is hit <code>Ctrl + Shift + l</code> and your laravel project will formatted with laravel pint.<h2>The Extension</h2>If you are more driven toward the extension approach you can get the above integration by using the following extension.<h3><a href="https://marketplace.visualstudio.com/items?itemName=msamgan.laravel-pint-vscode" rel="noopener noreferrer">Vscode Laravel Pint Extension</a></h3><h3><a href="https://github.com/msamgan/vscode-larapint" rel="noopener noreferrer">Show Some Support by staring the repo</a></h3><h3><a href="https://marketplace.visualstudio.com/items?itemName=msamgan.laravel-pint-vscode" rel="noopener noreferrer"> </a></h3><h2>Conclusion</h2>I have been using the unsatisfactory formatters from a long time. All of them have one thing but lack other. Laravel Pint is one who has it all, combining it with vscode is like proving you laravel project a super power.Feel free to pick your brain in comments.

I have been using the unsatisfactory formatters from a long time. All of them have one thing but lack other. Laravel Pint is one who has it all, combining it with vscode is like proving you laravel project a super power.

How to Add Laravel Pint to VS Code Formatter

Here I am working under the impression that, the setup is ready, tables and migrations are there, form and view files are good to go.We will focus here on the main uploading part, ones the file reach the controller. I am also skipping the validation part for the file as we will take it in consideration some other time.So, as per me the best approach is to put the entire path of the file in database, instead of just putting the name of the uploaded file.<pre class="ql-syntax" spellcheck="false">$fileLink = url(Storage::url(Storage::put('public/files', request('file'))));
</pre>The above piece of code will put the file in storage/app/public/files, with a uuid name and will return with the complete URL foe the file.Before be able to access this file in browser by the provided link, you need to do one more thing, create the symlink from storage to public by running the following command<pre class="ql-syntax" spellcheck="false">php artisan storage:link
</pre>and now we are good to go.

As per me the best approach is to put the entire path of the file in database, instead of just putting the name of the uploaded file.

File Upload Made Easy in Laravel

I am familiar with the love of Eloquent among the laravel community but sometimes, sometimes its better to go for raw queries. Its saves you a lot of time and trouble.Trust me, its hard to digest but is true. Lets consider a case where the following query is a complex one.<pre class="ql-syntax" spellcheck="false" data-cacher="true" data-cacher-block-id="1779193543">select count(id) from users where admin_id = 2
</pre><h2>Step one (Creating required directory)</h2>Create a queries directory in storage. <code>storage/queries</code>, you can create further sub directories as per requirement.<h2>Step Two (Adding helper method)</h2>Add the following method to you helper methods.<pre class="ql-syntax" spellcheck="false" data-cacher="true" data-cacher-block-id="333058884">if (!function_exists('getQuery')) {
 /**
 * @param $queryName
 * @param null $data
 * @return array|false|string|string[]
 */
 function getQuery($queryName, $data = null)
 {
 $query = file_get_contents(storage_path('queries/' . $queryName . '.sql'));

 if ($data) {
 foreach ($data as $key =&gt; $value) {
 $query = str_replace($key, $value, $query);
 }
 }

 return $query;
 }
}
</pre><h2>Step Three (Calling the query)</h2>once the directory and helper function is in place all you have to do is create SQL query files in the <code>storage/queries</code> directorysay, <code>storage/queries/admin.users.sql</code>containing the query, <pre class="ql-syntax" spellcheck="false" data-cacher="true" data-cacher-block-id="3128878593">select count(id) from users where admin_id = adminId
</pre>Please make note, the dynamic ids are replaced with a variable name.Call the query with helper function as follows.<pre class="ql-syntax" spellcheck="false" data-cacher="true" data-cacher-block-id="461072977">use Illuminate\Support\Facades\DB;

/**
 * @return array
 */
public function adminUsers(): array
{
 return DB::select(getQuery('admin.users', [
 'adminId' =&gt; auth()-&gt;id()
 ]));
}
</pre>In this way, you can get any complex query data, without going through the trouble of Eloquent.Feel free to provide us with your review and feedback in the form of comments.

I am familiar with the love of Eloquent among the laravel community but sometimes, sometimes its better to go for raw queries. Its saves you a lot of time and trouble.

Approach to Handle Complex queries in laravel

Deployment in itself is a messy task, and it becomes a bit more of hectic if you need to run a bunch of commands every time you deploy.The one of the best way is to create a deployment script and run it every time you deploy.<h2>Step 1: Create deployment script</h2>create a deploy.sh file in the root of your folder and make it executable. You can use the following commands.<pre class="ql-syntax" spellcheck="false">touch deploy.sh
sudo chmod +x deploy.sh
</pre><h2>Step 2: Update the script</h2><pre class="ql-syntax" spellcheck="false"># Turn on maintenance mode
php artisan down

# Pull the latest changes from the git repository
git reset --hard
git clean -df
git pull origin master

# Install/update composer dependecies
composer install --no-interaction --prefer-dist --optimize-autoloader --no-dev

# Run database migrations
php artisan migrate --force

# Clear caches
php artisan cache:clear

# Clear expired password reset tokens
php artisan auth:clear-resets

# Clear and cache routes
php artisan route:clear
php artisan route:cache

# Clear and cache config
php artisan config:cache
php artisan config:clear

php artisan view:clear

# Install node modules
npm install

# Build assets using Laravel Mix
npm run prod

# Turn off maintenance mode
php artisan up
</pre><h2>Step 3: Run on Deployment</h2>Now every time you need to deploy. just run deploy.sh<pre class="ql-syntax" spellcheck="false">./deploy.sh
</pre>Feel free to suggest any modification if you feel so.

Creating a Deployment script to make the Deployment Easy

There are a number of options available for purpose of blog creation but if you are a developer non of them are as satisfying as <a href="https://github.com/themsaid/wink" rel="noopener noreferrer">laravel wink</a>. It not only comes with a straight forward deployment but also the UI implementation for the blog is super easy (we will discuss it in our next article).In this article we will discuss how to get started with wink for blog creation. <h2>Step One</h2>Since wink is a laravel package its but obvious first we have to install laravel. You can follow the <a href="https://laravel.com/docs/8.x/installation" rel="noopener noreferrer">official installation guide</a> for the same<h2>Step Two</h2>Ones we have laravel all setup and running wink is installed as all the other laravel packages <pre class="ql-syntax" spellcheck="false">composer require themsaid/wink
php artisan wink:install
php artisan storage:link
</pre>Ones this is done, we have to set up the Database. Configure the database connection in&nbsp;config/wink.php. <div class="embedded_image" contenteditable="false" data-layout="default"><img alt="" src="/storage/wink/images/ehvh5zHWzfVXFcy9DtiRMLVUL9b4Sm2zvgchbzto.png"></div> use "mysql" if you want the use the default DB connection else you can make a different one as per the requirement. After this run the following commands<pre class="ql-syntax" spellcheck="false">php artisan config:cache
php artisan wink:migrate
</pre>and that it, you are good to go.Head to&nbsp;"your-project.test/wink/login"&nbsp;and use the provided email and password to log in.Although there is not much left for the setup part but here is the source of <a href="https://github.com/themsaid/wink" rel="noopener noreferrer">wink GitHub</a>.<h2>Updates</h2>as in each update there might be a chance DB is changes so make sure to run these two commands too.<pre class="ql-syntax" spellcheck="false">php artisan wink:migrate
php artisan vendor:publish --tag=wink-assets --force
</pre>Feel free to comment.

There are a number of options available for purpose of blog creation but if you are a developer non of them are as satisfying as laravel wink

How to get started with laravel wink for creating a blog

below are mentioned things to be taken care of at the time of deploying a laravel project to production.<ul><li>Make site down for maintenance (&nbsp;php artisan down&nbsp;)</li><li>clear all manual changes if any (&nbsp;git reset –hard&nbsp;)</li><li>Sync with mater from VCS ( production will always be in sync with master,&nbsp;git pull origin master&nbsp;)</li><li>Install/update composer dependencies (&nbsp;composer install –no-interaction –prefer-dist –optimize-autoloader –no-dev&nbsp;)</li><li>Run database migrations (&nbsp;php artisan migrate –force&nbsp;)</li><li>Clear caches (&nbsp;php artisan cache:clear&nbsp;)</li><li>Clear expired password reset tokens (&nbsp;php artisan auth:clear-resets&nbsp;)</li><li>Clear and cache routes (&nbsp;php artisan route:clear, php artisan route:cache&nbsp;)</li><li>Clear and cache config (&nbsp;php artisan config:cache, php artisan config:clear&nbsp;)</li><li>Install/update node js dependencies (&nbsp;npm install&nbsp;)</li><li>Compile the resources (&nbsp;npm run prod&nbsp;)</li><li>Make site Up (&nbsp;php artisan up&nbsp;)</li></ul>

Checklist for Production Deployment laravel Project

As you may have known by now that laravel 6.0 has been out. Though it’s expected to have a lot of changes in the major release but in 6.0 there are not that many changes.It’s more like 5.9 in terms of changes.But one major change introduced in laravel 6.0 is the&nbsp;removal of<pre class="ql-syntax" spellcheck="false">php artisan make:auth
</pre>Command. As you may know, this was used to create the authentication scaffolding. Thought the concept is not removed but just the way to implement has been changed.<h2>The New Way</h2>Authentication support is now added with the help of a package now. you can read in detail about it in&nbsp;<a href="https://laravel.com/docs/6.0/authentication" rel="noopener noreferrer">here</a>Command to implement the Auth are as follows.<pre class="ql-syntax" spellcheck="false">composer require laravel/ui
php artisan ui vue --auth
</pre>All the other stuff is the same as 5.8. Same Routes, Controller and all the stuff.Below is an explanatory video for the same. Please have a look.<div class="inline_html" contenteditable="false"><iframe width="100%" height="500" src="https://www.youtube.com/embed/Mqs0O0jDQTg" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe></div> Hope this was helpfulfeel free to share your thought in the comment section.

PHP artisan make:auth in laravel 6.0

The progressive web app is the new trend as well as the need for the present time. I hope before getting in the “HOW” part you know what is exactly a PWA is. If you don’t let’s say, just for the sake of brief introduction they are web apps but also can be installed over the devices like desktop and mobiles.I am adding a demonstration video of how PWA works here below.So, by this video i am assuming that you have understand that how a PWA works.<div class="inline_html" contenteditable="false"><iframe width="100%" height="500" src="https://www.youtube.com/embed/ReP3KssgLj4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen=""></iframe></div> <h2>How a make a PWA</h2>lets come to the main question, how to do this.Before getting into it let me make one thing very clear to you. Making a PWA is&nbsp;not that hard&nbsp;that it seems to be. So, chill it will be funTo make a PWA you need three things. Listed below<ol><li>manifest.json</li><li>Checking all the Audit test from google lighthouse</li><li>Service worker</li></ol>Once these three things are done you are good. So, without any further ado, let’s get the show running.<h3>manifest.json</h3>Consider this file as the guide to tell the browser that from were, what is to be taken. It’s simple and easy to create. The sample code is below. Also, you can take all the code used in this tutorial from my git repo. link is at the end of the article.<pre class="ql-syntax" spellcheck="false">{
 "short_name": "Short name of the application",
 "name": "Name of the application",
 "icons": [
 {
 "src": "/images/path/image.png",
 "type": "image/png",
 "sizes": "192x192"
 },
 {
 "src": "/images/path/image.png",
 "type": "image/png",
 "sizes": "512x512"
 }
 ],
 "start_url": "/",
 "background_color": "#ffffff",
 "display": "standalone",
 "scope": "/",
 "theme_color": "#e5e5e5"
 }
</pre>you can find all the details about all the attribute of manifest.json&nbsp;<a href="https://developers.google.com/web/fundamentals/web-app-manifest/" rel="noopener noreferrer">here</a>. Once created,&nbsp;Add this to your ROOT DIRECTORY. In Case of&nbsp;LARAVEL, PUBLIC DIRECTORY.In the next step, you have to link this file to your HTML. adding in the&nbsp;LAYOUT&nbsp;is the best option for laravel<pre class="ql-syntax" spellcheck="false">&lt;link rel="manifest" href="/manifest.json"&gt;

&lt;meta name="mobile-web-app-capable" content="yes"&gt;
&lt;meta name="apple-mobile-web-app-capable" content="yes"&gt;
&lt;meta name="msapplication-starturl" content="/"&gt;
&lt;meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"&gt;
&lt;meta name="theme-color" content="#e5e5e5"&gt;
</pre>I have mentioned some other meta also which will ease the creation process. After adding the manifest.json and linking it to the HTML you will be able to see it in the application section of the google development tool.<div class="embedded_image" contenteditable="false" data-layout="default"><img alt="" src="/storage/wink/images/9jOjXoNcKUjCMCSiKlgRx1ImMK7a14SUuHe4DIs3.png"></div> <h2>Checking for Audits</h2>After adding manifesto to the system, we will get all the audits to check. you can find the audit in your google chrome developers console. All you have to do is check the appropriate option and run the test.In case any test fails, do not worry. Tests in the installable section are the only mandatory for the app to work. If the test fails in that section get the suitable fixes. You can put the issue in the comment section. Maybe I could be of any help to you.<div class="embedded_image" contenteditable="false" data-layout="default"><img alt="" src="/storage/wink/images/A8tv0muS8sdM71m2FhpN9j0ciyXZRxS4giYywyHI.png"></div> <h2>Service Worker</h2>Last and final step of the process in the initiating and using the service worker. The process can roughly divided into 2 part.<ol><li>Adding the service worker</li><li>Using the service worker</li></ol><h3>Adding the service worker</h3>For adding the service container, add the below code in the file.<pre class="ql-syntax" spellcheck="false">if ('serviceWorker' in navigator) {
 window.addEventListener('load', function () { navigator.serviceWorker.register('/sw.js').then(function(registration) {
 console.log('ServiceWorker registration :', registration.scope);
 }).catch(function (error) {
 console.log('ServiceWorker registration failed:', errror);
 });
 });
}
</pre>This code is registering a&nbsp;sw.js&nbsp;that means we have to create a sw.js which will serve as our service worker.<h3>Special NOTE:</h3>please put&nbsp;service worker and manifest.json on same level. It is highly recommended that you put both of them in the public directory. if they are not on same level scope issue will be there.<h2>Using the service worker</h2>Once added now we have to add the code in sw.js. Please add the following code in the sw.js.<pre class="ql-syntax" spellcheck="false">var CACHE_NAME = 'pwgen-cache-v1';

/**
 * The install event is fired when the registration succeeds.
 * After the install step, the browser tries to activate the service worker.
 * Generally, we cache static resources that allow the website to run offline
 */
self.addEventListener('install', async function () {
 const cache = await caches.open(CACHE_NAME);
 cache.addAll([
 'all files to be cached here'
 ])
});

self.addEventListener('fetch', function (event) {});
</pre>You can find a complete detailed explanation of the added install and fetch functions&nbsp;<a href="https://developers.google.com/web/fundamentals/primers/service-workers/" rel="noopener noreferrer">here</a>Now for the final showdown all, we have to call the prompt to add the app. to do that we have to add the following code to the&nbsp;same file we have registered the service worker.<pre class="ql-syntax" spellcheck="false">window.addEventListener('beforeinstallprompt', saveBeforeInstallPromptEvent);

function saveBeforeInstallPromptEvent(evt) {
 deferredInstallPrompt = evt;
 deferredInstallPrompt.prompt();
}
</pre>The above code will make the prompt for adding the app. And congratulations mate. you got yourself a PWA.In case of any doubt of query feel free to ask in comment section.

The progressive web app is the new trend as well as the need for the present time. I hope before getting in the “HOW” part you know what is exactly a PWA

How to create a progressive web app (PWA) in laravel 5.* and above

create a .htaccess file in the root of your project and paste the following code in the file.<pre class="ql-syntax" spellcheck="false">RewriteEngine on
RewriteCond %{REQUEST_URI} !^public
RewriteRule ^(.*)$ public/$1 [L]
</pre>And you are all set to go. Happy coding.PS: If you want a&nbsp;complete guide for hosting laravel project in a shared server&nbsp;you can it from&nbsp;<a href="https://dev.to/samgankhan/how-to-upload-a-laravel-project-on-shared-hosting-2o1h" rel="noopener noreferrer">here</a>