1
00:00:01,060 --> 00:00:06,970
Now, so far, we have installed Gatsby and generated a project and we have managed to start the local

2
00:00:06,970 --> 00:00:12,880
development there, but what we actually have locally is a bit different from what we want to send in

3
00:00:12,880 --> 00:00:13,450
production.

4
00:00:14,170 --> 00:00:20,320
And generally every tool has like a build step, which is designed for production.

5
00:00:20,530 --> 00:00:27,070
So something that a piece of code needs to be compiled, or in this case, for this very simple website,

6
00:00:27,730 --> 00:00:31,180
there is some JavaScript that needs to be generated.

7
00:00:31,180 --> 00:00:35,260
Resources need to be like minified so that they don't like so much space.

8
00:00:35,920 --> 00:00:40,540
So a lot of the steps that you would not usually use when you're developing the application because

9
00:00:40,540 --> 00:00:46,630
they take a bit of time, you will have them in a build step, which will create production, really

10
00:00:46,630 --> 00:00:49,000
build where everything is nice and clean.

11
00:00:49,810 --> 00:00:53,400
And Gatsby has a command for that is called build.

12
00:00:53,680 --> 00:01:00,010
So if I called Gatsby built, it will generate a new folder and inside there will be like the website

13
00:01:00,010 --> 00:01:01,770
that I can deploy somewhere.

14
00:01:01,930 --> 00:01:02,980
So let's write out.

15
00:01:16,820 --> 00:01:21,620
And now the bill is ready and you will see here that some of the last steps that were executed here

16
00:01:21,620 --> 00:01:25,080
is like building production, JavaScript and Cyesis bundles.

17
00:01:25,080 --> 00:01:30,380
So where this is compressed into one file and everything is included there.

18
00:01:30,410 --> 00:01:31,560
The same goes for JavaScript.

19
00:01:31,580 --> 00:01:35,330
It's compiled and included only one file.

20
00:01:36,320 --> 00:01:38,810
Static pages have been generated and so on.

21
00:01:39,510 --> 00:01:41,870
So let's go ahead and inspect the built folder.

22
00:01:41,870 --> 00:01:47,720
And actually, Gatsby doesn't call the the build folder build it calls it public.

23
00:01:48,470 --> 00:01:53,210
And it makes sense because all the files that are inside that folder are designed to be public.

24
00:01:54,260 --> 00:01:56,870
So let's switch to public and see what's inside.

25
00:01:58,670 --> 00:02:04,730
You have like an index HTML page and you have some JavaScript and everything that is needed in order

26
00:02:04,730 --> 00:02:07,130
to work with the website.

27
00:02:07,350 --> 00:02:11,420
And this is exactly this is or artifact for this website.

28
00:02:11,450 --> 00:02:20,390
This is what we want to take from our build process and save it somewhere so that we can deploy it to

29
00:02:20,390 --> 00:02:21,460
a server, for example.

30
00:02:22,250 --> 00:02:25,120
And now we have to write this process locally.

31
00:02:25,130 --> 00:02:31,850
We now have this build and the idea would be to automate this depth, to use Gottleib S.I in order to

32
00:02:31,850 --> 00:02:32,630
execute this.