All right, so most of the work for this lab is already done, and it all happens from VAR
www.html.
We have this index.html, and we need hello world, okay, you get it, hello world, echo
hello world, great, then index.html.
That's not the exciting part.
The exciting part is the repository server.
What did we do again for the repository server?
Well, we mounted the installation ISO on the directory slash repo.
So let's create a directory slash repo, and let's redefine the mount, etcfs step, and
here we've got it, rel 10.iso, that is what I still want to mount, and this time I want
to mount it on VAR www.html slash repo, and I'm keeping all the other options.
Next, I'm using mount minus A, and mount minus A is giving me this message VAR www.html repo,
write protected, mount delete only.
Well, that's what you normally get when you mount an ISO file, and this is looking okay.
So that is part one.
Part two, we need to restart the Apache web server.
So systemctl restart httpd, and part three, I need to make very sure that the Apache web
server is running, so systemctl status httpd, and it's listening on port 80, so that is
looking okay, and everything is looking fine.
So just to be sure, curl localhost, and curl localhost is giving me hello world.
But now about the repository client, where was that again?
Well, that is in etc yum.repos.d.
Oops, I'm using VI on the directory.
You can't do that, but VIM is showing the contents of the directory with the browser that allows you to
select the file, and that is what I want, and I want to change my base URL, and my base URL this time is no
longer going to be file, it is going to be http, colon, slash, slash, localhost, slash, repo, slash,
base OS, and we need to do the same for the other files, so etc yum.repos.d, and we need repo
underscore fstream, and likewise, the base URL is no longer going to be file, it's going to be
http, colon, slash, slash, localhost, slash, repo, fstream, because this slash repo, fstream,
that's relative to the Apache web server document root, right?
So next, it's a good idea to use dnf clean all, because dnf uses cache, and I want to make sure
that we are using the new configuration, so let me use my favorite command dnf install zsh, for instance,
that's z shell, and what do we see? Well, we see that we get an answer, that's good, but we also
have a confusing message created by dnf config manager from file, colon, slash, slash, slash,
repo, slash, fstream, so we need to verify that. I don't care about installing it right now,
I care about what exactly do we have in the repository files, aha, there is the confusing
message, so I'm going to change this message as well, I overlooked it, and I make that from
http, colon, slash, slash, localhost, slash, repo, slash, fstream, and not created by dnf config
manager, but by Sander, that's me, and I want to do the same for this repo base OS, because,
you know, something small like this, you might remember it today, but it will bite you later
when you forgot about everything that you have done, so let me make the change right here as well,
oops, wrong direction, localhost, and http,
and not the dnf config manager, but Sander, and then I'm doing my dnf clean all, just to make
sure that we don't use any caches whatsoever, and now once again, dnf install zsh, which is telling
me created by Sander, well, now we're in the right direction, isn't it, and is this okay,
yes, this is okay, so now I don't only have an Apache web server,
I have an Apache-based repository server, isn't that cool?