Then middleware is basically, if you need an extra middleware guys, then plugins. So the plugins file generally is for, Trapi has support for installing several plugins. So when you install a plugin, you want to create your own plugin, your custom plugin, you can, so the way Trapi is built is you can install plugins from the admin dashboard, but you can also build your own personal plugins.
Yeah, so if you have any extra special requirements, any special updates you need to do, you need to create for yourself, the plugins.js file is basically where you probably want to do that. Now, like every new JS file, the server.js is the most important part of it because we need to run a new JS server. When you start up a server.js is basically connecting, creating a 1337 ports for our hosts to listen on. And that's basically just a simple server that has the host and a post generally. That's entirely what the config file is for, which is sort of like the most, one of the most important part of the file.
Then the source folder, which is where a lot of the whole, you know, your whole magic goes on from the UI, et cetera, for the admin dashboard, the extensions your admin dashboard needs, so if you bootstrap a normal Strapi app, yeah? If you bootstrap, you know, a lot of the content you see here would actually not be there because it's bare, but since we already have a built application on, you'd see that the way it's really, really separated into various files, admin, API components, extensions, and your indexes, which is your entry point. It's really, really easier. So, strata now just started the Strapi server, so there's, if you check the repo, there's a instruction there on how to get to this particular point. So, you can just run yarn stage, run yarn develop on your, on the API, inside the API folder, then your admin accounts, create the following credentials with node, workshop, then the email, like admin at example.com, then the password you can use what is being displayed there. And after that, I would like you, Chad, to go to this particular link, the articles, the API slash articles. Can you go there, Chad?
Yeah, sure. The only thing I was gonna add is I ran the yarn seed command, and what it did is initialize this SQLite database, and it gave me all of our images for our restaurant review app in this public uploads. Yeah. As for these credentials, just so you know, you can change these later. You should probably use these. It's not a big deal if you don't, but later on in the demo, these will be credentials that you'll have to use, and you can update it. So I just kept them consistent here. So you wouldn't have to remember a couple of different passwords. Like I said, we can change them later. I logged in with, I created an admin user with those creds, and that gave me the dashboard, and you will see that this has the same structure reflected that was in the source API sub-directory here, and our seed command has initialized all of this initial data to go along with all these different collection types, including the images that were a part of that seed. And so what Shadrach is asking me to do is, Strapi provides this dashboard essentially on top of the database for using, which at this point is SQLite. But we'll switch it to a different service, and the whole point here is we're gonna begin serving an API on top of this. So you'll see inside the instructions, I have this right here. So this is our local server at 1337. So here's the dashboard, but instead I'm just gonna go straight to the articles collection type, and we'll see four of that seated data there. Sorry, go ahead Shadrach. You want to go? You want me to keep going? Oh, yeah, yeah, sure. So this basically, this as of course you're seeing here is what we got from seeing the particular data if you navigate to cinpu.cda.db. So the data.db file is basically what has given us this particular articles. So what we are going to do essentially, what the entire concept of this talk is this workshop is we are going to take this data, this particular article data we are seeing here, the images, the files, and we're going to deploy it, then serve it on a front end. That's basically the entire idea behind this talk. So we're going to add the front end in this talk and connect it to Strapi and see these particular data displayed in a very, very... This very, very interactive form, then we're going to take the entire app and deploy it on platform S.H. as a decoupled application. So that's basically the entire goal of this talk on this workshop rather than used to doing talks. All right, so let's go into platform a little bit. We have a local server. Great, now we just need to get this deployed. So we have already... Let's make sure everything looks okay here. Sweet. So every application is going to have at least three configuration files on the platform that are associated with three different container types. So the first one will be, how do we want traffic directed to our application? In this case, I want all traffic to go to an application container directly, which in this case, we'll name in a second, strappy for this back end, at this placeholder domain. So what's interesting about this placeholder is that when we, in a little bit, create a branch, we'll get a development environment to go along with that branch, and a URL is just going to be generated and substituted for this default placeholder. So that's what that default means there. We're also gonna get an ID. We can see in a little bit where that becomes a handy, but essentially associating this route with an ID.