In this video, I want to explain the files and folders that are stored on your Web server now, monkey,
like I said before, is a client application that runs on Mac OS, but it does look for a server.
And so your client will point to a monkey repo and it will look for the five folders that you see on
the screen.
And if your Web server has these five folders and the files in those folders are formatted correctly,
then the monkey client will be able to do its job.
If we go ahead and we look and say this manifests folder and we see a couple of files, and if we go
over to this testing one, you can see that we have some XML and you can see that we have managed installs
and then we have a list of things to install.
So everything is human readable and there are no databases.
And so everything is easily backed up, easily moved around.
And that's why I said that you can very easily load balance this or replicate a monkey server across
the country and you can use monkey for pretty much an unlimited amount of clients.
All right.
So to really explain how all of this stuff works, I think a better way to present it is with a program
called Monkey Admin.
Now, in Monkey Admen, you have three main views, you've got your package view, your Chalong view
and your manifest view.
And so when you import software into monkey, it will show up in the packages page, just like Adam
and Firefox are here.
All right.
So if I double click on Adam, you can see that there's some information stored with this, with the
with the application, including requirements, which let me specify those levels that this package
would apply to.
And there's also a section on scripts.
So I could run a script before Adam is installed or script after kind of similar to what we did with
Monkey Package.
Now, the information that we apply to Adam is stored in this package info folder and we click on Adam
Pelias.
Then you'll see that we see the exact same information that we saw in the Monkey Admin Guey.
So here's our OS versions and.
And so, like I said, everything is just stored in simple files.
All right, so let's go ahead and move on to the catalog, and now the best way to explain a catalog
is, I think, with production and testing.
So I'm going to go to testing and you can see everything is checked.
All everything I've imported into monkey is checked.
And I have two versions of Firefox.
I've got sixty six point zero and sixty six zero three.
Now, if I'm going to be testing software before I push it out for compatibility, then testing makes
a lot of sense to have every thing in.
Now, if I'm testing something well and it's not approved yet, then production software would be just
what's approved.
So you can see here I've got Firefox 60 six zero, but I do not have the upgrade of sixty six zero three.
Now the next section is manifests.
And so here I've got a couple of manifest files and including one for testing.
So in the testing manifest you can see I'm showing Manege software installs and you can see that Firefox
is there.
If I have a client that's a member of the testing manifest and it's getting its catalog from the testing.
Catalog, then the version of Firefox that I'm going to get is going to be 60 six zero three.
Now, if I'm a member of the site default manifest and I have Firefox installing and I'm pulling my
catalogues from production, then the version of Firefox that I get is going to be 60 six zero.
All right.
So in this manifest, I'm calling from production and I have three installs and so on, or mahadi machine,
the machine that was on the right.
We had gotten Firefox and we had gotten VLCC and we had gotten the mobile config, the machine that
was on our left, our Heiser machine was part of the developer's manifest.
And so if I take a look at the developer's manifest, you can see I'm pulling from production and I
have one manager install Atem, but we saw that that machine had gotten more installed than Adam, and
that's because it's including the manifest site default.
So developers get everything that the site default gets, plus it gets what's in it's own manifest.
In addition, I created an optional install for developers for Microsoft remote desktop.
And that's why this software that install automatically.