background top icon
background center wave icon
background filled rhombus icon
background two lines icon
background stroke rhombus icon

Download "Полный курс Laravel 04 Структура проекта (Project Structure)"

input logo icon
Video tags
|

Video tags

html
css
js
php
mysql
laravel
vue
nuxt
nuxtjs
vuejs
reactjs
react
dev
web
one code
1code
onecode
max orlov
верстка
сайт
создать сайт
программирование
tailwindcss
ларавел
пхп
веб
макс орлов
gulp
laravel mix
backend
frontend
fullstack
full stack
фулстек
бекенд
фронтенд
фул стек
разработка
laravel курс
курс по laravel
фреймворки
Subtitles
|

Subtitles

subtitles menu arrow
  • ruRussian
Download
00:00:01
stack remote web developer I'm
00:00:03
very glad to welcome you to the next
00:00:05
video in which we're learning such a
00:00:07
wonderful framework like marvel
00:00:09
guys, I immediately apologize for the sound quality
00:00:11
because I have birds singing in the background, some
00:00:12
dogs barking - those sounds, the
00:00:15
fact is that our family moved to the south and
00:00:17
decided to live here for a while and
00:00:19
now I’m in the Crimea and while we out of 5
00:00:21
tied up on the balcony we recorded this
00:00:23
video for you guys, I also want to say that I’m
00:00:24
currently working on several projects,
00:00:26
traveling with my family and I got up specially
00:00:28
at 6 in the morning to record this video for you,
00:00:30
so if your brain comes up with
00:00:31
some excuses like your mind doesn’t have time,
00:00:33
and so on, in order to study the
00:00:35
issue, work, practice, then this is all
00:00:37
[ __ ], you can always get up early and go to bed
00:00:40
later, find some more... then ways to
00:00:42
find time to take steps in the
00:00:44
right direction so guys,
00:00:45
sit back, listen
00:00:46
carefully because today there will be
00:00:48
very interesting and useful content, the thing is
00:00:50
that before we start
00:00:51
writing code and practicing with you, I decided to
00:00:53
record another video in which we will
00:00:54
learn more I’ll tell you how
00:00:56
the framework itself works, I decided to do this because
00:00:58
it will save you from possible questions
00:01:00
that otherwise will arise
00:01:03
when we practice,
00:01:04
and thanks to this video you can become better
00:01:06
acquainted with the right slide, understand how
00:01:08
it works from the inside
00:01:09
to avoid it as I already said, there are
00:01:10
some questions when you and I
00:01:12
practice and write code, so the
00:01:14
video will be very useful, and if you
00:01:16
don’t fully understand something, then there’s nothing
00:01:18
wrong with not paying attention to it, in
00:01:19
fact, then over time you’ll
00:01:21
understand everything In any case, I will try
00:01:22
to explain everything in simple words so that you
00:01:24
can understand it, so let's go guys,
00:01:26
let's go straight to the
00:01:27
documentation section, in fact,
00:01:29
I will often refer to my videos in the documentation for
00:01:30
several reasons because firstly it is
00:01:32
very important to learn how to use
00:01:33
the documentation because it is firstly
00:01:35
Uvarova is very good, and
00:01:36
secondly, it’s very useful because
00:01:38
here, in principle, there are answers to all questions, and
00:01:40
there I often see how beginners take
00:01:41
various questions and answers to
00:01:43
most of them, there is always
00:01:44
documentation, here in general there is an
00:01:45
excellent search that very easily
00:01:47
finds everything we need, for example
00:01:48
you can write his tire people and get
00:01:50
delivered validation here in the menu
00:01:52
we can immediately find for example yes
00:01:54
not the validation rules, that is, the link is
00:01:55
immediately lowered, we see all the rules here,
00:01:57
for example, we don’t remember what it’s called,
00:01:59
spent the IP address there, click on the IP
00:02:01
address, we get right here
00:02:02
plus everything here throughout
00:02:04
the documentation there are headings and
00:02:05
subheadings and each of them is, well, it’s
00:02:07
like a hash link written on it,
00:02:10
click on it, we have a hash mark appearing in the address
00:02:12
bar and just the same link
00:02:14
to the heading, we can take this link and
00:02:16
send it somewhere and immediately get there in the
00:02:19
same section to this title of
00:02:21
the documentation, that is, to to it is really very
00:02:22
useful and convenient and therefore refer to
00:02:24
it during the work process when
00:02:26
questions arise and we
00:02:27
will also use it in our videos, but in the
00:02:29
second documentation here everything has already
00:02:30
been thought out for us here
00:02:32
the structure is built logically, so today we also
00:02:34
come to the getting started section, let's
00:02:35
look at the file structure with you, that
00:02:37
is, what files and directories
00:02:39
our project consists of, then we will see what a
00:02:41
service container service provider is and what
00:02:43
facades are,
00:02:44
in fact, everything is very simple not
00:02:45
be scared now you will understand everything, let's
00:02:48
move on to the first part of the video and
00:02:49
see what files the directory
00:02:51
contains in the directory of our project,
00:02:52
here, in principle, all this is described in what I
00:02:54
will say today, yes, but in
00:02:56
my own words, try to explain it
00:02:58
maybe a little simpler and so on in
00:02:59
fact, everything is very clearly
00:03:00
described here, so let’s
00:03:02
deploy an empty clean project here, I stole it,
00:03:04
don’t let’s see what
00:03:05
files and directories we have here, what the
00:03:07
first directory consists of, this is the ap directory, that
00:03:10
is, this is the application directory of our
00:03:11
application, this directory will
00:03:13
contain it all the main code of your
00:03:15
application, all the code, classes, modules, and
00:03:17
so on, which will create,
00:03:18
implement some kind of business logic,
00:03:19
this will all be stored in a directory, and
00:03:21
most of the time you
00:03:23
will most likely spend in this directory
00:03:24
when you create some files
00:03:26
mainly through command line,
00:03:28
they will all end up in the ap directory, that
00:03:30
is, these are event models, listeners, there is a
00:03:33
notification letter, and so on, we have a bunch of
00:03:35
everything, everything will end up here, and there is
00:03:37
such an interesting point that will help
00:03:39
you understand a little better right here, there
00:03:41
is a directory, eat, etc.
00:03:42
there is a console directory, the thing is that to
00:03:44
use the framework to launch the
00:03:46
framework in general there are two
00:03:47
interfaces, that is, 2 ways to launch
00:03:50
our framework, this is through http
00:03:52
requests, for example through a browser
00:03:54
and through the command line through the
00:03:55
console, so here the
00:03:57
whole thing is divided for us, the directory
00:03:59
clear write holds the controller rome
00:04:01
dvr resources and so on, well, everything that is
00:04:03
necessary to process our search pi
00:04:05
requests via api lisa through the browser yes,
00:04:07
as I already said, the directory console
00:04:09
color contains everything necessary for
00:04:11
processing commands took in the fact that larolles
00:04:14
clothes There are various console commands from the box,
00:04:16
but we can also create our own
00:04:17
console commands, they
00:04:19
will just end up here and in the console directory
00:04:21
there is an hp ink file and in the directory that
00:04:23
you also have a fart php file,
00:04:25
here they are, as it were, basic files
00:04:27
like the kernel type for the kernel consoles and the kernel of the
00:04:29
mod and almost the type of layer for example the directory
00:04:32
honor and peter gave we set up saw
00:04:33
you and sobs and the classes that
00:04:35
process our request before the
00:04:36
ditch controller falls we will
00:04:38
study them in detail in one of the following
00:04:39
videos yes well here we will set them
00:04:41
up register some other points,
00:04:42
so on, and in the console file we
00:04:44
fed, we can register our
00:04:46
console commands and do some other
00:04:48
things, but now you need to understand that
00:04:50
there are 2 ways to launch the framework:
00:04:51
through sending you a request and through the console,
00:04:54
and just like that the ip directory contains
00:04:55
these two directories here, these two parts are sort
00:04:57
of separated here, the files necessary for
00:04:59
processing requests will be stored in a
00:05:01
directory in the steppe which also contains the
00:05:02
helm file in which we can make
00:05:05
certain settings and the files
00:05:07
necessary for processing console
00:05:08
commands are contained in the console directory
00:05:11
there is also a term file that
00:05:12
allows us to make certain
00:05:14
settings for the console, in short, but all the
00:05:16
other files we need for
00:05:18
work will be added to the root of
00:05:19
the directory, well, more precisely, the
00:05:22
necessary directory will be created here, and also, for
00:05:24
example, dare we create some kind of job and
00:05:26
there and joc la roll you are here there
00:05:28
is no such directory until winter from work
00:05:30
automatically create a jobs directory here and
00:05:32
will put it there you
00:05:33
will see all this when he was working in Varkal
00:05:35
then the next directory is called
00:05:36
bootstrap as an investigator name yes
00:05:38
this is a type of download and here essentially there is
00:05:40
one file a php this is the main
00:05:42
file for launching our application there
00:05:44
in the comments I'm looking for creates an application that is
00:05:47
this file
00:05:48
the work of the framework starts here happens in the
00:05:50
m variable puts a
00:05:52
new instance of the application yes this is a
00:05:54
cool [ __ ] fondation
00:05:55
applications we'll look at it a little
00:05:57
later here it is
00:05:58
just this http core from the cabins that is being registered,
00:06:01
the file from the directory is lowered there, which
00:06:03
we just talked to you, then there is a
00:06:04
dacha, the same snort is being registered,
00:06:06
only from about the console to the console,
00:06:08
this is the topic,
00:06:09
and in principle, then the earth simply rotates
00:06:11
from our application, this file from the
00:06:13
stove as osake is used when a
00:06:15
request comes to us from a browser, for example, yes,
00:06:17
or when we enter some kind of console
00:06:19
command, for example, we
00:06:20
’ll make a framework so that all requests that
00:06:22
come to us, for example, from a browser, yes,
00:06:23
they should go to the public directory, the
00:06:25
file index.php
00:06:27
that is, if you
00:06:28
then deploy your project website on a server for
00:06:30
hosting, you need to configure it
00:06:32
in April in such a way that it
00:06:34
redirects all requests and minutes to this
00:06:36
file, there are some points that
00:06:37
we will now omit for you, for now the
00:06:39
dense main thing is that we are just
00:06:41
here we take into the variable ef this is our
00:06:43
application which is initialized in
00:06:45
bootstrap first aid kits which you yourself just
00:06:46
looked at then we take this here look for
00:06:48
now our kernel I start
00:06:51
processing the request basically everything and when
00:06:54
we enter the console command
00:06:55
used favor through the console we are
00:06:57
essentially essentially we enter before usually here php
00:07:00
artisan and even some command,
00:07:02
this site is exactly the file that
00:07:04
lies in the root of the project where
00:07:05
it is here, here it is with Ortis and everything that
00:07:07
happens here is essentially the same thing we
00:07:09
take here is our it is fast php
00:07:12
let's take our application from here already in the
00:07:13
console, this is the core kernel and
00:07:16
we process our outgoing command in the same way, well, in
00:07:18
principle, hand over everything, now you need to
00:07:19
understand that when a request comes from the
00:07:21
browser, it should go to index.php,
00:07:24
this index.php uses the booster file
00:07:26
to load the saw and applications and
00:07:28
processing the request,
00:07:29
and when we use the console, we
00:07:31
use an artisan file that
00:07:33
basically does the same thing, takes our
00:07:35
application from quick php and also
00:07:37
processes the request from the
00:07:40
console, in principle, everything is simple, yes, I hope the guys
00:07:42
understand, there is also a file cache in the quick directory
00:07:44
which adds ignore, that
00:07:45
is, in this story you won’t have
00:07:47
all this business,
00:07:48
this directory needs a framework in
00:07:49
order to cache some system issues with the site
00:07:51
in order to
00:07:53
optimize the work of the framework, in
00:07:54
principle, you will never have to
00:07:56
go into the directory at all quickly just explained to
00:07:57
you for For example, you will understand
00:07:59
how the hillock generally processes our
00:08:01
requests after tickling, as the
00:08:02
name suggests, it is responsible for the configuration, here
00:08:04
we have many configuration files
00:08:05
because the device contains a
00:08:07
lot of functionality to many
00:08:10
different modules, and the configuration is
00:08:11
also divided into separate files for
00:08:13
convenience, here for example. there is a
00:08:15
configuration for databases to give for
00:08:17
varnishing for mouse food and so on,
00:08:19
then we will
00:08:21
talk to you separately about regulation today, so now
00:08:23
remember that in the config directory there are
00:08:24
configuration files, we can also
00:08:26
create our own configuration files here
00:08:27
very easily when we
00:08:29
need it chick then Lord the bass,
00:08:30
as the name suggests, here we
00:08:32
store the files necessary for working with the
00:08:34
database; you don’t contain
00:08:35
any logic of our application here; here
00:08:37
we describe, for example, the schema of our
00:08:39
database; when we need to poop
00:08:40
a sign,
00:08:41
we create a migration that goes into the
00:08:43
migration directory here We already have
00:08:45
migrations out of the box, for example for
00:08:47
creating a user table,
00:08:49
we will also talk about database migrations separately
00:08:50
before we begin, you just need to understand
00:08:52
essentially that
00:08:54
the files necessary for working with the
00:08:55
database are created in the accident directory, to create tables for
00:08:57
filling with basic tests data and so
00:08:59
on, the next directory is called
00:09:01
public and, as the name suggests, this
00:09:03
directory contains all public files, that
00:09:05
is, as I already said, when you
00:09:06
deploy a project on the server, you
00:09:08
must configure it in such a
00:09:09
way that all requests end up in the
00:09:11
public directory and in a saucepan and all
00:09:13
the files that will give are in this directory,
00:09:14
they are available upon request, that is,
00:09:16
the user can open any of them, for
00:09:18
example, when you write java
00:09:20
script code there, you can create a gst directory
00:09:22
and in it there is an ageless file
00:09:24
and write some kind of you in it and java
00:09:25
script code also if you use the
00:09:27
java script assembly, yes then you
00:09:29
will have it there resources now we
00:09:31
will move on later
00:09:32
and after the assembly you will also get
00:09:33
this thing here or if you use
00:09:35
creates and also also wait the files will
00:09:37
be here
00:09:38
and this We will now also get into the
00:09:40
public directory and will be available for
00:09:41
connection in the browser, but
00:09:43
some static images, yes,
00:09:45
you can create a disk and push the same and
00:09:46
store your image, for example, the
00:09:48
site logo, there are some pictures that are
00:09:50
used on the pages, and so on and so on
00:09:52
static files should be
00:09:53
stored here under the favicon, here we already
00:09:55
have robots.txt to set up
00:09:58
indexing, in general, when requests come in, they
00:10:00
fall into this directory and the first
00:10:02
thing it does is the file on request,
00:10:04
if there is no such file, then
00:10:05
index.php is used by default and starts I’ve
00:10:07
already found work, in general, now you need to
00:10:09
understand that the public directory
00:10:11
just accepts all requests, sends files
00:10:13
if they exist, this launches
00:10:15
index.php, which already launches our
00:10:16
application and processes this request, the
00:10:18
next resource directory is a very
00:10:20
interesting directory which you will also
00:10:22
spend a lot of time time, what is there
00:10:24
in general, first of all, there are templates in the
00:10:25
ear,
00:10:26
that is, these are our pages, there
00:10:28
is already a file for the wolves, just the page
00:10:30
that you and I see here on the main
00:10:31
page when we are just deploying a
00:10:33
clean project with you, all the pages of your
00:10:35
site will be stored in the views resource is
00:10:37
also here
00:10:38
their directory lang which contains a
00:10:40
directory n-yes English here already
00:10:42
out of the box there are some translations
00:10:44
some texts in English
00:10:45
for example for validation all the rules for
00:10:47
validation to check our requests
00:10:49
example that this is an image they are
00:10:51
already stored everything here is in English,
00:10:53
but it’s clear that we often
00:10:55
develop projects in Russian, and that’s why
00:10:56
we need Russian translations,
00:10:58
but we will study localization in more detail
00:11:00
in one of the following videos.
00:11:01
Now I’ll say that it’s very easy to
00:11:02
add all Russian translations, we just
00:11:04
googled Rowling. there are repositories
00:11:07
specially in which the same
00:11:08
files are stored only with translations into any
00:11:10
languages, we download the required
00:11:12
language for us, for example y, and drop this file directly here into the
00:11:14
catalog bark and immediately all the texts will be
00:11:16
in Russian, this is very convenient,
00:11:18
we can also create our own here files with
00:11:19
translations and so on, that is, if you are
00:11:20
working with a bunch of language sites,
00:11:22
make a multilingual project all
00:11:24
translations and the
00:11:26
slang resource will also be stored here, as a
00:11:28
rule, the original style and original
00:11:30
scripts of ours are also stored here,
00:11:31
i.e. if you have some more complex
00:11:32
proposal in a java script, the husband would even
00:11:34
look like hardware and so on, that is,
00:11:36
you store everything with the jane streamer in the directory, you
00:11:38
can create a directory here, wait, so
00:11:41
in it, accordingly, some kind of paul, for
00:11:43
example, and pss before You can also create
00:11:45
some kind of file like wars with them, they are not
00:11:48
variables and connect this file with our
00:11:50
of chess.
00:11:51
You can do this then wars s.s. it
00:11:54
actually didn’t work there in a minute, well, it seems like this is how it’s
00:11:56
done, then you set up the assembly
00:11:58
very easily and simply using a
00:11:59
mix on the head and this whole thing is already final,
00:12:01
that is, the css file gets to our public page,
00:12:03
now you need to understand what is what from
00:12:05
the directory resources for your
00:12:06
pages are stored in the translation language and also
00:12:09
static, some of your resources java
00:12:11
script css and so on, the original ones
00:12:13
after assembly they go into public and are
00:12:15
available for connection in the browser the
00:12:16
following directory which is called rus
00:12:19
as the name suggests, this is a roll trouble
00:12:21
or routes you are here,
00:12:23
routes are stored that also give
00:12:25
access to our application,
00:12:26
here also this whole thing is divided into
00:12:28
several files for convenience,
00:12:30
we can also create our own route files
00:12:31
in some other way, combine them in some other way, this is an
00:12:33
example that gives a device
00:12:35
that is very clipped convenient and suitable
00:12:36
for developing any practically
00:12:38
projects, what is interesting here,
00:12:40
but if it makes sense, there are
00:12:41
several files here and each of them
00:12:43
is responsible for its own part, that is, for
00:12:45
example, php
00:12:46
contains routes for the browser
00:12:48
directly, that is, when users
00:12:49
use our site Through the browser,
00:12:51
we basically add all the routes here to the
00:12:53
stove’s api and these are just the routes
00:12:55
needed for the arch. yes, you and I
00:12:56
are writing some kind of feature, for example, for a
00:12:58
mobile application for a single piece
00:13:00
apple, of course, it can be given, that is,
00:13:01
the route or api is stored in this
00:13:03
separate file, but this does not mean that we
00:13:04
should research this way, that is,
00:13:06
if we have it in the file For example, there are a lot of
00:13:08
routes already, we have
00:13:09
some public routes there, then routes
00:13:11
for the user’s account, you are there
00:13:13
for the admin panel, and so on, that is, we
00:13:15
can easily create here, for example, a
00:13:16
userpic file food and
00:13:19
a sheet, write here routes for the
00:13:21
user’s account separately then the creators, for example,
00:13:22
php admin and wrote routes, names for the
00:13:25
admin panel and in the first aid kit we can, for example,
00:13:27
in general, you are jealous of them, sit down with us, they stuff a
00:13:29
general route here and well, just
00:13:30
the main ones there, the main page of the site
00:13:32
news there and so on, just a general
00:13:34
public route, that is, here, as it were,
00:13:35
about the hard ones there are no rules, we can
00:13:37
act according to if necessary,
00:13:39
and well, you can start with in php and then, as the
00:13:41
project grows, you can easily divide
00:13:43
these routes into different files. gif
00:13:44
rally there are no problems here, also there is
00:13:46
also a stove console file that I
00:13:48
rarely use, but it allows us
00:13:50
to register like routes for the
00:13:51
command line and narrow it down, we can
00:13:53
create the essence of our command, that is,
00:13:54
using both the class and artisan, we said
00:13:56
we need the espiro command,
00:13:58
here this example just goes straight out of the
00:13:59
gate and then call back we indicate
00:14:01
which will be executed when we
00:14:03
run this command in the console for example
00:14:05
. artisan inspire and here we get an
00:14:07
error
00:14:09
file in php and there is to do what we
00:14:12
renamed baking to main.
00:14:14
this thing is all just registered in the mouth of the
00:14:16
service provider and in another file, here
00:14:18
we are registering this file, yes,
00:14:20
fail, we will also have to rename it here,
00:14:22
let’s not
00:14:23
change anything here for now so that you do
00:14:25
n’t have to download the film either, we’ll just return
00:14:27
it to the web again Once we run the command,
00:14:29
write to the father of a giant, here we
00:14:31
got some kind of
00:14:32
inspiring quote from Marcus
00:14:34
Antonius, so we return to the
00:14:36
console and here we can
00:14:38
register our commands, but some
00:14:40
small commands, in principle, it is convenient
00:14:41
to register here even even large ones, in
00:14:43
principle, he too For some reason I
00:14:44
never use this because laravel
00:14:45
allows you to create a separate class or
00:14:47
commands as an example.
00:14:48
artisan make commands and I will test the
00:14:52
commands and create my custom command,
00:14:54
I usually do this in this way and another it
00:14:55
gets to our console of course
00:14:57
commons
00:14:58
here it is a test command if we can
00:15:00
write the name of this command for example
00:15:01
test just give a description of the date some
00:15:04
functionality that will be executed this
00:15:06
command here we can display the console
00:15:07
for example some kind of message here info
00:15:10
hello for example yes like this
00:15:13
and now we can run this command php
00:15:15
artisan test lab
00:15:18
here is our cold complexity very, very
00:15:20
easy and simple with one one command we
00:15:21
created a file and wrote it like this command
00:15:24
We will also call some
00:15:25
functionality here, that is, it’s very easy and
00:15:26
simple, so I don’t really use it; it’s
00:15:28
somehow more pleasant for me to fire these commands in
00:15:30
separate files between writing
00:15:31
routes here. In principle, this is also an option,
00:15:33
because in essence it’s also like robots only
00:15:35
on fire for requests there from the browser before or
00:15:37
almost the like.
00:15:38
namely through the console and there
00:15:40
are also more files here, he is responsible for the websocket, he
00:15:42
tore it off allows us to work with the court using
00:15:44
sockets, some events broadcast
00:15:45
his packet, the channel here is Tatar, we can
00:15:47
register these channels, check the
00:15:49
user’s access to a specific channel,
00:15:51
because it happens, but not
00:15:53
everyone the user must have access
00:15:54
to one or another channel, so here we
00:15:56
also register them, now he
00:15:58
needs to understand the following: the
00:15:59
root or routes directory contains
00:16:01
files with routes that give access to
00:16:04
clients to users of
00:16:05
our application through the api
00:16:08
web console and so on in reality in fact,
00:16:10
everything seems to be easy and simple, let me
00:16:11
think, it should be clear, then we have a
00:16:13
directory, as the
00:16:14
name suggests, 100 comes from the storage,
00:16:16
some useful files are also stored here, the directory is
00:16:19
necessary for storing our
00:16:22
files, then here we can put
00:16:23
some files necessary for
00:16:25
our application to work,
00:16:26
they will not be accessible from the browser in
00:16:29
any way, that is, they will
00:16:30
lie here and no one will be able to get them.
00:16:32
Yours, we can use them inside
00:16:33
our framework in some way, but
00:16:35
some files may be stored here, I don’t know, there
00:16:37
may be some then keys and something else,
00:16:39
and in the rap directory there is also the entire
00:16:40
public directory, so it can already be available upon
00:16:43
request, as a rule,
00:16:45
files that users upload on
00:16:47
our website end up here, for example, use unloads
00:16:48
the avatar and we just
00:16:50
put it in the public directory that is,
00:16:52
here we can create, for example, an
00:16:53
avatar directory like this,
00:16:54
and all
00:16:56
user avatars will be added here, but
00:16:58
how will they be accessible to
00:17:00
the browser? In fact, we will study
00:17:01
this issue with you in a separate video and
00:17:03
about the file system about downloading files
00:17:06
but in short, laravel allows
00:17:07
us to create a symbolic link
00:17:10
using one command; a symbolic
00:17:11
link is created in the public directory and
00:17:13
redirects requests also to the
00:17:16
directory guard a public, so the
00:17:18
request will come to public and there it
00:17:19
will additionally be checked if
00:17:20
such a file is in the directory guard a public
00:17:23
that is, well, I don’t know exactly why this was
00:17:25
done, but in principle it’s quite convenient, that
00:17:27
is, for example, if we talk about
00:17:29
pictures, date, we store them here in the
00:17:30
public directory mg2 here for ordinary anime,
00:17:33
find images that statically, they do
00:17:35
n’t seem to change, as I already said,
00:17:37
which website logo the images that
00:17:38
we use there on the main
00:17:40
page are given, which are simply in the
00:17:41
layout we have these files that are
00:17:43
already directly downloaded and for
00:17:45
users from the account or for example
00:17:47
from the admin panel, they already end up in the
00:17:48
Guardian Public directory and through a symbolic
00:17:51
link they will also be available in
00:17:52
in the browser, it’s
00:17:53
just about the core root fd, it
00:17:57
is used to store files that are
00:17:58
not accessible, but this also does not
00:18:00
happen so often, but sometimes it’s useful further
00:18:02
aside, we have a directory framework
00:18:04
here, in principle, the device itself
00:18:06
can be sessions in any of its files
00:18:07
the user here is also a cache of
00:18:09
compiled templates, well, that is,
00:18:12
already cached, you can say
00:18:14
in short, also for optimization,
00:18:15
the need to climb here on principle is
00:18:17
also never necessary, this is a purely
00:18:18
technical directory for your cleaning and the
00:18:21
clogs channel, as is clear from the name, it
00:18:23
contains a log, some error
00:18:25
occurs here here we have
00:18:27
them written in the log, from just the same we are
00:18:28
already in the error our consoles that we received
00:18:30
when we renamed the file rose to
00:18:32
pokes, yes, this is what we have here, we
00:18:34
immediately see what else the problem is the description of the
00:18:37
error the entire call stack up to
00:18:38
sequentially, you can directly
00:18:39
trace the entire path of
00:18:40
the framework’s operation. Now we are clearing this
00:18:43
log. Remember that the logs are stored in a
00:18:45
storage box,
00:18:46
so when you see some kind of error, the
00:18:47
first thing you do is immediately go here and see
00:18:49
what you bought behind the error; well, such a haircut
00:18:51
did not happen, then fixes Fixing
00:18:53
the error, you can clear your mind on your feet to
00:18:55
look at everything again and so on, that is,
00:18:57
it is very convenient and so
00:18:59
now, here’s what to fill out: the guard directory
00:19:00
is used to store such and such
00:19:02
files in the hills that we don’t need to
00:19:05
pay attention to them to store
00:19:06
our
00:19:07
internal files for storing public files
00:19:10
that are uploaded by the user or
00:19:11
admin and also for storing logs and
00:19:13
let's move on to the next
00:19:15
directory test, as the name implies,
00:19:17
tests are stored here, that is, the selection window
00:19:18
allows you to create tests as well,
00:19:20
just a fungus testing system, there is
00:19:22
also an artisan oven command for this
00:19:24
iq test for creating tests and
00:19:26
we can sit down the test just like that, in short,
00:19:29
just the test it gets right here to
00:19:32
us, open the future, here it is, our test is
00:19:34
already here, an example tests are here, we
00:19:35
can send a request to the main
00:19:37
page of the site using the get method and check
00:19:39
that the answer is 200 before this Thus, here
00:19:41
in the test we are already checking that the head of the
00:19:42
site page answers us works
00:19:44
correctly and so on, of course, we
00:19:45
will also work separately now, in
00:19:47
principle, it is clear that
00:19:48
all the tests of our application are in the tests, here is the
00:19:50
next directory, vendors, this is the directory
00:19:52
that creates composer composer is the
00:19:54
dependency package manager analogue of ampy
00:19:56
m.v.
00:19:57
but James, that is, here he is our composer,
00:19:58
the file itself, which contains all the
00:20:00
necessary dependencies, all the necessary
00:20:02
packages necessary for the work of our
00:20:04
project, when you connect some packages,
00:20:06
they will also
00:20:07
appear here and will end up just
00:20:08
in the vendor, that is, even now here are
00:20:10
a lot of different packages that are
00:20:11
used robbed and also here
00:20:13
we have the world from work itself
00:20:15
which, in principle, here you can visit the
00:20:17
source code our file of spoons but also
00:20:19
had to add useful on the number and cleaned
00:20:21
itself unical even the insides of how it
00:20:23
works I didn’t delve too much
00:20:24
There is a basic point
00:20:26
that I understand today and I’ll
00:20:27
explain to you later, by the way, we
00:20:29
’ll come back here again, so now it’s important to understand that the
00:20:31
vendor directory is exactly from
00:20:33
composer, all
00:20:34
installed packages are added here, let’s
00:20:36
go through the files, here’s the first file
00:20:38
we have there are roots here, this is
00:20:40
the editor config, apparently there are
00:20:42
some parameters for our
00:20:44
code editor and some stupid lines here and so
00:20:46
on, to be honest, I
00:20:47
have never climbed here, I haven’t even changed anything here, the
00:20:49
next file is the file . Inge this is a very
00:20:51
important file, first of all you need to understand right away
00:20:53
that this file was added with git ignore, that
00:20:55
is, you will not have it in the repository,
00:20:57
here it is and envy, this file is
00:20:59
created separately by each cattle developed
00:21:01
what they need is our application, that is, we
00:21:02
deployed the framework automatically we
00:21:04
created this file here
00:21:05
when we parse it on the server, this
00:21:07
file most likely will no longer be there
00:21:08
and we will need to create it there
00:21:10
manually, that's what this is for, in order
00:21:11
to configure configuration parameters
00:21:14
separately in each place where
00:21:16
our application is deployed, for example the parameter
00:21:17
connection with databases, yes, we have only
00:21:19
one on our computer, for example, we are here, and on our computer,
00:21:21
databases, yes, we have a user there,
00:21:22
maybe a robot, some kind of password,
00:21:24
maybe there is no password at all,
00:21:25
but on the server before that in production,
00:21:26
for example, there is already another database, maybe
00:21:28
it’s called otherwise, another
00:21:29
user, another password, and so on,
00:21:31
that is, there is already a separate all these
00:21:32
parameters are
00:21:33
taken now, we are talking about Kanske, by the way,
00:21:34
we will talk later in this video in a
00:21:36
separate block, now it is important to understand that
00:21:38
this Invis file can be managed separately
00:21:40
each time in the place where it is deployed
00:21:42
our application and here the
00:21:43
environment variables are configured
00:21:45
specifically for this
00:21:47
specific application and also here there
00:21:49
is a file dot y simple, this file is
00:21:51
no longer clogged, grief, that is, it
00:21:53
is always in our project, why is it needed,
00:21:54
essentially it’s just a template just a template
00:21:57
from which we then create this one.
00:21:59
envy is very convenient, yes,
00:22:00
all the necessary environment variables are already listed here, we
00:22:02
can also add
00:22:04
our own here, for example, some kind of thing, we just
00:22:06
even full bore, and we save everything; this
00:22:09
file is stored in our repositories when we
00:22:10
deploy sites somewhere in a new place
00:22:12
or on a new server and so on, we
00:22:14
just copy this file, make
00:22:16
envy dots and immediately see that we still need to
00:22:17
remember to add variable changes here,
00:22:19
no longer food, we don’t even indicate the value here with the husband, but
00:22:21
we just see that we
00:22:22
will need to add this, well, just
00:22:24
don’t forget which ones environment variables,
00:22:25
what happens in general, there are a lot of
00:22:27
custom ones, in fact,
00:22:28
this is just a template for creating
00:22:30
already. file . envy in a new place the
00:22:32
next file we have is github and 3
00:22:34
beauty guide ignore, well, it’s probably clear yes the
00:22:36
guide is a business, to be honest, I don’t even
00:22:38
know what these are, these are the files
00:22:40
and directories that we don’t need to put in
00:22:42
the repositories, we ignore them here in
00:22:43
principle by silence even it’s already written down,
00:22:45
you can add yours like everything else if
00:22:47
necessary, in principle, I
00:22:49
never use this rule, that is, it’s rarely
00:22:51
necessary to add git1
00:22:53
separately, then we have a file,
00:22:55
I tried some kind of honestly, I won’t even
00:22:57
lie, I don’t
00:22:58
even know you I’ve never even
00:23:00
delved into it and it’s visible over the years, they did
00:23:01
n’t have to be soaked, so
00:23:03
maybe you shouldn’t even
00:23:04
bother what it is next, we have
00:23:06
files by the artist, as we said, this is
00:23:07
the entrance. for console commands until when
00:23:09
we write to the nickname artisan
00:23:11
this file is used until through the console
00:23:13
10 can talk to you
00:23:15
our application is launched, it’s the console part
00:23:17
and the request from the console is processed it’s
00:23:19
a shame Jason this file for installation
00:23:20
will be tolerated depending on here when the stacks are
00:23:22
further packages that we install
00:23:24
for our project will be listed there
00:23:26
and for example we install a new package
00:23:27
here here for example liquor block and
00:23:30
it will be added here with one more
00:23:31
line so when we
00:23:33
install the project on the server we
00:23:34
enter here composer in the table yes it can
00:23:38
even start displaying and
00:23:40
composer check which packages
00:23:41
need to be installed and the whole thing
00:23:43
will be installed, served in the directory,
00:23:45
of course, the vendor there is a fire curl
00:23:47
to fix the simplicity of the dependencies of their
00:23:48
versions that we have installed so that
00:23:50
on production, for example, the same versions
00:23:52
then install then we have
00:23:54
a file here dk campus
00:23:55
this file is used during installation
00:23:58
deployment projects numbers were torn
00:23:59
Ilkum themselves recorded previous videos
00:24:01
staging a raven in sight of son McQueen just the
00:24:03
same when installing past the quest I
00:24:04
used the installation option sent
00:24:06
now this thing comes out of the box
00:24:08
words deftly force and we create new projects
00:24:10
that is, the docker compass will be
00:24:12
short if there is
00:24:13
you may have some old project, yes, that is, it
00:24:15
may not be there yet, and we can
00:24:16
also install this village through composer
00:24:18
and the file will also appear here,
00:24:20
that is, if you are working on numbers, tore
00:24:22
through burst in, that is, here it is just the
00:24:23
same all configurations can also be
00:24:25
customized,
00:24:26
which in principle is also rare and it is necessary to
00:24:28
already have some parameters, as we see,
00:24:30
they take easy field, which is very convenient, here is
00:24:32
the name of the database, database passport,
00:24:34
and so on, in general, it is also rare that
00:24:36
you have to look here for the next
00:24:38
file and We already have this
00:24:39
for the packages through which
00:24:42
PMPK is installed. Woman is essentially an analogue of composer
00:24:44
only for javascript, and here you
00:24:46
can also download dependency scripts.
00:24:49
By the way, an exe
00:24:50
Oslo roll mix will come out of the box for assembling frets after c
00:24:53
and so on. there are those window packages
00:24:54
listed here they will also be installed
00:24:56
our application
00:24:57
if you don’t need something here you can
00:24:59
remove the world whear yah now you don’t need it
00:25:00
we can just remove this line will it
00:25:02
not be installed on you stocking guardianship this is the
00:25:04
same thing composer varnish here to fix the
00:25:06
versions of packages and so on so that the
00:25:08
same rockets are actually installed
00:25:11
there on the server and for example with you we
00:25:12
will also, in principle, cook about this matter in a
00:25:14
separate video. Now it’s just important to
00:25:15
understand that composer Jason is a
00:25:17
package manager for the stove, the packages are listed here
00:25:19
which we install for our
00:25:21
framework, but for now the woman is the same
00:25:24
only for the java script, here we
00:25:25
indicate what packages and dependencies we
00:25:27
need for our jalla script up to
00:25:29
which is not enough 10 we store put the resources
00:25:31
with let's move on further we
00:25:33
have a php file in June.
00:25:35
xml here, in the xml format, oddly
00:25:37
enough,
00:25:40
the parameters for testing are configured when we
00:25:42
run our tests, the
00:25:43
parameters for them are taken from the test directory and from
00:25:45
here a separate environment is launched, the
00:25:47
envy point file is no longer used for
00:25:49
tests, this file from 50 is used and
00:25:52
when you don’t have to change anything except
00:25:53
these, this block here, we have the
00:25:55
environment parameters too, that
00:25:57
is, for testing we can separately
00:25:59
indicate that our environment is called
00:26:01
testing, that the connection to the database is
00:26:03
already different from us, for example, sparks like in
00:26:05
general databases should be stored in the
00:26:06
sea and in RAM so that the tests
00:26:08
go faster and so on some
00:26:10
other point sometimes food can be
00:26:12
built up for our tests well, as a
00:26:14
rule, just uncomment
00:26:15
probably the databases, in principle you do
00:26:17
n’t have to do anything special here, well occasionally
00:26:19
maybe yes, that is, in principle, an hour needs to
00:26:20
understand what the oven will change the xml this one for the
00:26:22
helmet is needed to set up tests for the
00:26:24
environment for testing, let's move on to the
00:26:25
readme file.
00:26:27
Andy, this is a file in McDow Mardan format,
00:26:29
which is actually entered
00:26:30
here on the main page of the
00:26:31
Lara repository, in principle, you can
00:26:33
delete everything here and write your own
00:26:35
content, for example, instructions for
00:26:37
deploying your application, but in
00:26:38
principle, in general, the normal approach, as a
00:26:40
rule, is what everyone and other developers should do
00:26:41
they can easily deploy
00:26:43
your project there according to the instructions,
00:26:45
yes, maybe you have some
00:26:47
additional steps you need to do, so on,
00:26:48
this is basically a normal topic, then there is a
00:26:51
file server. .
00:26:52
this is a built-in rsi server in the ditch and, in
00:26:54
principle, we can run our framework
00:26:56
through the built-in server in the ditch, that
00:26:58
is, if you have php and databases installed on your computer,
00:27:00
then you do not need to
00:27:02
install separately, for example, Apache or
00:27:04
James before a web server - some kind I have
00:27:06
invested the whole of such a simple
00:27:07
built-in server that allows you to
00:27:10
use one command to load the RTS it surf that’s what
00:27:12
it’s called now I won’t
00:27:14
launch it because my project
00:27:15
has already been launched and there will be a port conflict there,
00:27:17
most likely we’ll try.
00:27:18
artisan surf made a typo, well, yes,
00:27:22
here, in principle, I’ll write the server to start this according to the
00:27:24
Urals, our server will be visited,
00:27:26
our server will be available now I’m in, I broke
00:27:28
into other containers, this I won’t
00:27:30
work now you need to understand that you
00:27:31
have a built-in server that can
00:27:33
start using teams food
00:27:35
artisan surf here and open our project in
00:27:38
this way
00:27:39
in the corner you can see even through what’s happening by
00:27:41
the way in this file everything is
00:27:43
happening here it’s essentially
00:27:45
what this public index is taken for which is so you
00:27:46
accept our requests
00:27:48
well and in short this server is launched and
00:27:50
can accept our requests
00:27:51
are processed as usual, our own, but
00:27:53
I just haven’t
00:27:55
used it either, but there is such a possibility that
00:27:57
there is and the last file is like this mix
00:27:59
James, as I already said,
00:28:01
the box was broken into, there are cool themes, it’s called
00:28:03
la remix,
00:28:04
here it is, this npm package that allows
00:28:06
we need to collect our statics, that is,
00:28:08
collect the java script file css files
00:28:10
after with the windows stl there quickly because whatever
00:28:13
you want, in general there are a lot of functions there,
00:28:15
in fact, there is a separate video on the channel
00:28:16
from I won’t forget, I’ll attach
00:28:18
links to it, it’s called gold, it’s
00:28:20
no longer needed in fact, this is really what body
00:28:22
roll mix is, it’s an excellent replacement for daw
00:28:23
because it allows you to really, in two or
00:28:24
three lines, simply configure any
00:28:26
assembly, even a row with anything,
00:28:28
because under the hood it
00:28:29
uses vopak, firstly, and many,
00:28:31
many different enzo modules we have
00:28:34
to do a lot of work,
00:28:35
it’s difficult for you to understand that according to the books, Jess is needed
00:28:38
to set up the assembly of our java script
00:28:40
and disappeared, and so the guys went through
00:28:42
all the files and homework for not doing the task,
00:28:44
as I already said, you will have
00:28:46
to go through this page again and
00:28:48
read it again if something will not be clear to the
00:28:50
end not solved attention over time everything
00:28:51
will be clear
00:28:52
anyway now you already have a
00:28:53
better idea of ​​what
00:28:56
the framework contains guys in short it’s been almost an
00:28:58
hour now I’ve been recording the video after editing I
00:29:00
think maybe forty minutes
00:29:01
or so will remain half an hour, so I’ll keep the recording process short,
00:29:04
I decided that we are still
00:29:06
dividing this video into several parts
00:29:07
and the next part and we’ll also discuss a
00:29:09
few more important points that
00:29:11
will allow you to better understand and
00:29:12
get acquainted with the framework, so
00:29:14
be patient, write your
00:29:16
comments and questions if you have any I
00:29:17
think I saw it even we still found it
00:29:19
useful and understandable thank you for
00:29:20
watching again and see you in the
00:29:22
next video thank you all bye

Description:

Весь плейлист: https://www.youtube.com/playlist?list=PLXCVm4GFpx5CZf4X5ppNJTPsaGwSlBXLX VIP канал https://t.me/+yvsTtN8MkBw2NzMy Структура: https://laravel.com/docs/11.x/structure GitHub: https://github.com/indigoram89/laravel-course Gulp больше не нужен: https://www.youtube.com/watch?v=ySTyI-6POp0 Добавляйтесь в друзья: ►Канал в Telegram https://t.me/onecode_blog ►Сообщество Вконтакте https://vk.com/1code ►Личный Telegram https://t.me/indigoram89_blog ►Личный Instagram https://www.facebook.com/unsupportedbrowser

Preparing download options

popular icon
Popular
hd icon
HD video
audio icon
Only sound
total icon
All
* — If the video is playing in a new tab, go to it, then right-click on the video and select "Save video as..."
** — Link intended for online playback in specialized players

Questions about downloading video

mobile menu iconHow can I download "Полный курс Laravel 04 Структура проекта (Project Structure)" video?mobile menu icon

  • http://unidownloader.com/ website is the best way to download a video or a separate audio track if you want to do without installing programs and extensions.

  • The UDL Helper extension is a convenient button that is seamlessly integrated into YouTube, Instagram and OK.ru sites for fast content download.

  • UDL Client program (for Windows) is the most powerful solution that supports more than 900 websites, social networks and video hosting sites, as well as any video quality that is available in the source.

  • UDL Lite is a really convenient way to access a website from your mobile device. With its help, you can easily download videos directly to your smartphone.

mobile menu iconWhich format of "Полный курс Laravel 04 Структура проекта (Project Structure)" video should I choose?mobile menu icon

  • The best quality formats are FullHD (1080p), 2K (1440p), 4K (2160p) and 8K (4320p). The higher the resolution of your screen, the higher the video quality should be. However, there are other factors to consider: download speed, amount of free space, and device performance during playback.

mobile menu iconWhy does my computer freeze when loading a "Полный курс Laravel 04 Структура проекта (Project Structure)" video?mobile menu icon

  • The browser/computer should not freeze completely! If this happens, please report it with a link to the video. Sometimes videos cannot be downloaded directly in a suitable format, so we have added the ability to convert the file to the desired format. In some cases, this process may actively use computer resources.

mobile menu iconHow can I download "Полный курс Laravel 04 Структура проекта (Project Structure)" video to my phone?mobile menu icon

  • You can download a video to your smartphone using the website or the PWA application UDL Lite. It is also possible to send a download link via QR code using the UDL Helper extension.

mobile menu iconHow can I download an audio track (music) to MP3 "Полный курс Laravel 04 Структура проекта (Project Structure)"?mobile menu icon

  • The most convenient way is to use the UDL Client program, which supports converting video to MP3 format. In some cases, MP3 can also be downloaded through the UDL Helper extension.

mobile menu iconHow can I save a frame from a video "Полный курс Laravel 04 Структура проекта (Project Structure)"?mobile menu icon

  • This feature is available in the UDL Helper extension. Make sure that "Show the video snapshot button" is checked in the settings. A camera icon should appear in the lower right corner of the player to the left of the "Settings" icon. When you click on it, the current frame from the video will be saved to your computer in JPEG format.

mobile menu iconWhat's the price of all this stuff?mobile menu icon

  • It costs nothing. Our services are absolutely free for all users. There are no PRO subscriptions, no restrictions on the number or maximum length of downloaded videos.