At this stage, this posst is a stub, I am simply compiling information here then I will come back to edit this
Under linux, the Laravel extensions that i like up to now are
This part of the tutorial is a hands on setup to have Laravel working on nginx under Linux. this is not the only way to run Laravel, for all the options, see here
NOTE: Most if not all of the popular development tools are available for Linux and Windows, so If this setup is for development, you might want to install Debian Linux with the Gnome GUI so that you can install the development tools used in the next part of this tutorial, if you are going to be developing on a different machine or this is for production, then you shouldn’t.
STEP 1: Install Debian 11 (Bullseye) on a computer.
STEP 2: Install the basic Laravel environment with the following commands, Laravel 9 requires PHP 8, which at the time of writing is not available in Debian 11 repositories, so we will need to add the repositories from the guy who manages PHP for Debian anyway
sudo apt-get install ca-certificates apt-transport-https software-properties-common gnupg unzip curl echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/sury-php.list wget -qO - https://packages.sury.org/php/apt.gpg | apt-key add - apt-get update
Now, to the actual installation of the environment
apt install php8.1-fpm nginx
apt install php8.1-{dev,common,xml,tokenizer,zip,mysql,curl,mbstring,mysql,opcache,gd,intl,xsl,bcmath,imap,soap,readline,sqlite3,gmp}
apt install redis-server
apt-get install php8.1-redis
apt install mariadb-server mariadb-client
Now you need to secure redis !
Now remember to secure your mariaDB (MySQL) installation with the following command
mysql_secure_installation
Next, we need composer, the PHP dependency manager, to get it execute the following
curl -sS https://getcomposer.org/installer | php mv composer.phar /usr/local/bin/composer chmod +x /usr/local/bin/composer composer --version
The last line above should show you what version of composer you have just installed
Now, remember to never run composer as root, but rather as a regular user, from this point on I am assuming you are running the terminal as a regular user.
I understand that Debian puts the web root in /var/www/html, but i usually like to create a separate directory called /var/vhosts and put all my web projects in it
mkdir /var/vhosts
Now, we need to create a sample project for our learning and training experience
cd /var/vhosts composer create-project laravel/laravel laraveltestapp chmod -R 0777 /var/vhosts/laravelapp/storage
Next, We would need to setup nginx to serve this website (“Would like to” actually, because there are alternatives, but I’m keeping it simple), here is an almost standard template for nginx, modify the host name and project name to match your project and preferences.
NGINX vhost config file (In my case /etc/nginx/sites-available/laraveltestapp)
server {
listen 80;
listen [::]:80;
server_name ltest.net www.ltest.net;
root /var/vhosts/laraveltestapp/public;
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block";
add_header X-Content-Type-Options "nosniff";
index index.html index.htm index.php;
charset utf-8;
location / {
try_files $uri $uri/ /index.php?$query_string;
}
location = /favicon.ico { access_log off; log_not_found off; }
location = /robots.txt { access_log off; log_not_found off; }
error_page 404 /index.php;
location ~ \.php$ {
fastcgi_pass unix:/var/run/php/php8.1-fpm.sock;
# fastcgi_pass unix:/var/run/php-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
include fastcgi_params;
}
location ~ /\.(?!well-known).* {
deny all;
}
}
Surely for this to work, you will need to add the following two lines to the end of the /etc/hosts file
127.0.0.1 ltest.net
127.0.0.1 www.ltest.net
As soon as we have the file above, we need to create a symbolic link for it in the sites enabled directory
cd /etc/nginx/sites-enabled ln -s /etc/nginx/sites-available/laraveltestapp
Suddenly, it works through nginx, you should see the welcome page (View) here
Now, to the development environment, how to setup your development environment can be found here
The following are things that are commonly used with Laravel. broken down by category
Other
If you are like me, running only your own projects on a server, you might want to skip authentication
the changes I generally make to the file /etc/redis/redis.conf are
1- At the very beginning, limit the RAM redis can use with the line
maxmemory 2gb
2- Change the supervisor to systemd by modifying the line
supervised no
to
supervised systemd
Now, to test the new config, from the command line, run the following commands
systemctl restart redis-server redis-cli ping config get maxmemory quit
You have just configured redis and tested your new settings.
The following is a list of plugins I have installed to help with Laravel Development, I will add to them as I go, I will also remove the ones i don’t think were worth it from the list as well
| Plugin | What for | Publisher |
| PHP IntelliSense | Advanced Autocompletion and Refactoring support for PHP | Felix Becker |
| PHP Namespace Resolver | Import and expand php namespaces | Mehedi Hassan |
| laravel-blade | Laravel blade syntax highlighting | Christian Howe |
| Laravel Blade Snippets | Laravel blade snippets and syntax highlight support | Winnie Lin |
| Laravel goto view | Quick jump to view | codingyu |
| Better Align | Align code without selecting them first | wwm |
Disambiguation: This tutorial is about Blade, the template engine for Laravel…. I am covering blade on Laravel 9, but I am also taking into account that you might be maintaining code from blade 5 !
long as this tutorial may be, it should be an easy read. no need to memorize stuff or write notes, I am trying to structure it in such a way so that you can effortlessly understand the concept, then come back for that one little syntax you have forgotten very easily.
Simply put, i think blade is a very simple framework that you can complicate if you insist, I think there is an easier way to get someone up and running with blade, a tutorial that compares the Blade way to the traditional way, does not invoke flashy abbreviations before explaining what they mean, and serves you the simplest explanation first… Also one that involves illustrations, shows the different features and explains how they differ and when to use features and why…
I’ll leave the flashy terms and history lessons near the end of the tutorial for completeness, and because they may be useful, but not before you are comfortable with Blade.
If this gets any attention, I will create a video from it, but I personally prefer reading and looking at illustrations.
Traditionally, when creating a website in PHP, your HTML is mostly in the same PHP files that provide the functionality ! blade is here to help you separate your HTML content from your PHP functionality…
Blade is a special folder in your Laravel project where you add those PHP files that contain your HTML*, plain old folder where you simply separate those files from the rest of your code. files in that folder enjoy extra functionality provided by blade that takes out the inconveniences of separating the HTML.
in your Laravel project, that folder is usually /resources/views, blade PHP files end in .blade.php, for example, mytheme.blade.php
* HTML And JSON if you are also writing an API…. and whatever you normally add to your HTML such as inline CSS and inline JS
Well, that is what blade is for, it provides tools to make this simple and easy
Traditionally, if you wanted to separate the HTML from the rest of your code, you would create PHP files with the HTML in them, and use PHP’s include function to show them… or embed the HTML inside functions that are in separate files, and send the data to those functions (or classes) and print what is returned…
That works, and blade is more or less the same thing, but as you proceed with Blade, you will see how blade resolves many inconveniences that this method comes with.
First, I am assuming you have already setup Laravel and created a new project, if not, please take a look here (/2022/09/07/laravel-tutorial-laravel-setup/) for instructions on how to do that !
Now that you have such a setup, We will need to add a couple of routes (URL definitions), don’t concern yourself with what they are or what they mean, they are covered in the next section, they are just here to enable us to learn blade, routes is in a totally different place, all you need to learn for now that those two routes are invoked when you visit the URLs they define, and they pass the variables you see in them to the blade templates
Routes are added to the /routes/web.php file, so open that file and add the following at the end of it, now you have two URLs that work, the home page, and a /test page
Now, let us create our first BLADE file, let us call it example.blade.php, and in that file, we will simply add an HTML page with nothing to do with blade specific features, Just that page that will display whether you use the home page (the first route from above), or the /test route that you see in the other route !
If you stick to a couple of rules, it is compiled into PHP code and cached, so it is really fast !
Asset helpers
Layouts (extends, Yeild, section, show)
Partials
Components: includes, arrays vs collections {{$var->entry}}, props, <x-cards>,
BLADE is inspired by .NET’s Razor engine.
Allows you to use PHP code inside (@php directive), but you should not need to, and you should not unless you have to
(If you feel a need, you are misplacing your code)
If you come from Symfony, you can use Twig through Twig-bridge !
Syntax
1- Echo
{{ $variable }} is equivalent to <?= htmlentities( $variable ) ?>
Sometimes you may need to echo handlebar notation into the output, so you can simply use an @ before the above notation
@{{ $variable }} will output {{ $variable }} (Without the @)
or, if you want things to just print as they are, you can use the @verbatim directive !
{!! $variable !!} is equivalent to <?= $variable ?>
{{ $variable }} = <?= htmlentities( $variable ) ?>
{!! $variable !!} = <?= $variable ?>
{{-- comment is here --}}
self explanatory blade directives
if elseif else endif (endif is the closing after all of them)
@unless and @endunless = equivilent to if(!cond)
@for, @foreach, and @while (endfor endforeach enwhile)
@forelse and @endforelse = ForElse is a ForEach loop, but with extra handling for empty array.
@forelse ($talks as $talk)
{{ $talk->title }} ({{ $talk->length }} minutes)<br>
@empty
No talks this day.
@endforelse
-----------------------------------------------------------
Defining Sections with @section/@show and @yield
yeilds first param is the section name, it's second is A DEFAULT VALUE
instead of yeild, if you want an entier block as a default fallback, you can use
@section('footerScripts')
<script src="app.js"></script>
@show
In this @section .... @show, if we want to append to the default value above, we should include @parent in the child template extending this, otherwise, the contents above will be overwritten !
Note that The @show is in the parent section, shows in place, while the @section and @endsection are in the child !
the section show is both defining a default and doing so in such a way that its default contents will be available to its children, through @parent
to use all of the above... assuming the template is at resources/views/layouts/master.blade.php
@extends('layouts.master') {{-- Each file should only extend one other file, and the @extends call should be the first line of the file --}}
@section('title', 'Dashboard')
@section('content')
Welcome to your application dashboard!
@endsection
@section('footerScripts')
@parent
<script src="dashboard.js"></script>
@endsection
-----------------------------------
partials
------------------------------------------------
1: creating a folder called images under public !
---------------------------------------------------
Method 1: @yeild
put the header and footer in one file called layout.blade.php in one peice (empty doc)
within the template, you put in
@yield('content)
in other layout components, you use the extends directive, and make the content inside
@extends(layout)
@section('content')
whatever needed to appear in the theme, the content that is labeled content just like in yeild
@endsection
partials are added with include, so if you put the thing in the partials directory, the convention is that a file starts with underscore as a partial, _hero.blade.php
include('partials._hero)
Method 2: making the layout a component
---------------
in routes, read on route model binding, instead of passing $id to the inner function and route specification, we pass an object of type listing (The model listing) to the inner function, and in the route specification, the word /blah/{listing}, we it allows us to just
The people behind Laravel have created multiple ways to setup laravel, one popular such way is using a docker container which is useful for may situations. I will cover them all is this tutorial ever takes off, for now, the only ready tutorial is how to setup Laravel with nginx under linux