Yeah, all right, cool, thanks. I'll try and keep it a little bit speedy, I suppose. So that's good, I was worried I was gonna be too short, so that works out perfect, actually. Cool, yes, so yeah, my presentation is around yeah, Devisel and Lando. Yeah, you can see some icons there. We'll get straight to it. Cool, all right, so what is WSL? So WSL is like an integrated, virtualized, developer-oriented Linux environment. And I've put the two in brackets because it's the newest and greatest version, it's the one everyone should use. I don't actually know why you'd use number one, but anyway, two is where it's at. Why should you consider Devisel? So I don't have much text on the screen, but basically, if you're locked into Windows, you can still use some aspects of Linux, and it breaks everything like super fast when you're running your Docker containers compared to just like Docker containers directly with your project files, on your Windows file system.  It's a bit confusing because the WSL is also containerized. In your Linux operating system, and then the container file containers, also Linux file system, you get increased speed. And also you get your DevTools, so you can use your Grap and Cat and whatever in your thing rather than using like Gbash, like kind of programs. And you could also like, you know, install Mary container, but that's kind of annoying. So just comparing like the two, so when you install Docker, there's like two different backends that you can use. So the fault is the WSL, but a while ago it was half of a backend. And why is this, don't move. Yeah, so yeah, so comparing the two. So these are the pros of WSL. So it's like starts really quickly compared to the half of a backend. So apparently it can start in like two seconds. It doesn't start in two seconds. It might compute out, but I forgot to set it up. It's like super quick for the Docker daemon to start.  You can like kind of share it with like Windows. Whereas with the high V, it's like all concrete. It's like, okay, eight gig and that's it. Like can't do it, do any more or something. But yeah, you can, with the WSL, it can expand and go, I think it's up to like 85% by default, but you can configure obviously. Yeah, and but if it's not using that much, then Windows can like use like the remainder. So it's like great. It's, yeah, tools as I said before, home edition. I don't know if anyone's home, home edition, Windows 10 home edition at home, but that's the option. If you wanna run Docker at home, compared to like high V, you traditionally need like the Pro edition or Enterprise edition of Windows. There are some cons with it. So it's been like transparent. If you're like, for some reason, you didn't copy your files like into the Linux container and you're like, I'm gonna like use WSL but actually just have your files through Windows. It's like super slow. So don't do that. Put them inside your Linux environment. It's, yeah, so via the file speed, like your file system access speed. So it doesn't have to like translate the like file systems as it like, with your mounting. So look with your project and then like the Apache or NGINX or whatever web server that's inside your container doesn't have to like work across that. If you only go like a couple files, like it's okay, but probably not. And then we shall go into next slide on that one. To edit files inside the WSL, it's not in Windows, right? So you kind of just like, I'm gonna open like notepad. You need to use some like WSL software or you can use notepad, but it's a bit slow.  So you probably, yeah, you should use some do some native programs so it doesn't cross that file system boundary. So yeah, you're like limited limited with like not all programs like WSL and Naver would yet especially like Sublime, Tech, et cetera, which I really like to use, but it doesn't, it's not WSL and Naver, it's not on the way. It's so sad. Yeah, so after like convert to just to do a code. And there's some capacity to do like window programs like kind of natively, but it's not really like, there, yeah, I guess it's a brand new feature. I think it's like six months old or something like that. I do have like example coming up around how you can run Sublime like in Linux, but I haven't really tested it. So it's a bit of a, you know, it's there, but it might not work that great. There also are some memory bugs. It's generally okay, I think in my experience, but apparently Ubuntu uses like a lot of memory and doesn't always have active windows, can't really. See, I've already started occasionally, but it's generally, generally fine pretty much. So what's good or ish or what's okay? What's the notes about half of E back end if you're using the docker? So yeah, if you've got like any small amount of files, so you've got like gov's in a SAS project and you're like or install docker using hyper-v. It's like okay, like it kind of works. I've got some like metrics like later on. It's like, it works all right, but then yeah, only for like small. So the SAS is just like your config in your themes, like not too many files. You do seem to notice that if you've got like complex site, you've got a lot of config, you're like waiting to explore the config and you're like, I'm waiting, I'm waiting, it's like, I can be not too. But it's like small site, it's like not too bad. So that's kind of why you might use hyper-v. But then again, like yeah, that's only for SAS, right? If you're using PaaS or some like stock project, it's like lots of files, super slow, it's terrible, don't use it. But if you just, very small case, it's okay. There are some like networking issues as you can see here. They work a bit differently, like hyper-v commit to every cell. Your enterprise works like a bit differently with it. I personally would just configure your enterprise properly rather than trying to like switch between hyper-v or WSL, but that's something to note. Yeah, and apparently, according to chat VGVG, apparently, I couldn't like, I Googled it and I was like, why would you use hyper-v? When would you use hyper-v? And it like came with some response, but I clicked the sources and the websites weren't really that helpful. But apparently, if you're using Windows containers, it's better to use hyper-v back end, created Linux for your hard drive disk usage and stuff. But if you're using like CPU apparently, WSL is better. Anyway, basically you should use hyper-v and not hyper-v, but that's just some notes around it. So the metrics, yes. So as you can see on the screen, Gaussian SAS is like pretty similar, not too bad for like just clear the cache on a SAS site. So that's okay. But yeah, you really notice the difference when you're using Lender. So when you've got your whole project or your like composer files, it's like much, much faster, nine times faster on my computer, inside a Windows virtual machine, because not natively, because any device problems. Also, because it's like great with lots of files, your NPM and Yarn also will see a decent increase if you wanna run that inside your container as well. So I'm just gonna go through some like notes, kind of like mini intro to like WSL. And yeah, and then I'll go a little bit over like Lender as well. You guys probably are experts because like there's open presentation on it, but this is just like how to install it in WSL. So you basically like execute your command. So long as you've got like the latest version, latest and greatest of Windows, you still like your WSL dash just install from your command prompt. Make sure you've got the WSL base engine is like ticked. So if you like installed your Docker beforehand, then it might not have set that as default. So you like to make sure it's ticked and then it'll transfer between the Hyper-V machine that it runs and then the WSL kind of machine, but it's like a containerized machine. So you do lose your containers when you switch. Like they're still there if you switch back, but like initially they'll be empty. Yeah, and you're probably one like associated. Anyway, yeah, for Lender and things, you can't have the Docker compose to and also for God's sense as well. And yeah, so just go set like the settings to make sure like it should be like by default. But yeah, if you like switching, make sure you've got the like integration settings in event to like set. So when you run your Ubuntu, so that's your WSL that the Docker client talks to the Docker back end like the thing. So when you have your Docker like that, your WSL links can talk to the Docker back end and also your Docker in Windows can talk to the back end. So you install Docker in Windows, but it runs like a machine in WSL which Ubuntu can talk to. And there's some like settings down there if you're like if installs version one for some reason of WSL. Cool, all right. So it had install Lender so some like technical commands here, but essentially yeah, you want to like install Lender inside your WSL inside your Linux container. It is hard coded to like depend on Docker because Docker is like technically not really installed in the Ubuntu in the Linux. You go like add the flag to like ignore the Docker dependency. And then when you do your like your update, it will still like know that it was dependent on Docker. So you go like edit this file to like remove it. So when you do your installs of other software that it doesn't you know, try and, I don't know, I don't know. Anyway, the cross is supposed to say Docker, I typed that wrong. I think it's a bit of a rush job. But you delete Docker from the Lender like the database file thing. Cool, and yeah, the, I've went and I know there, but you can use whatever text file that you want to use to edit the file. Long as you run sudo, that's the key thing. Cool, so next, yes, add your files. So as I said before, if you're editing directly on Windows, it's like bit slow. There is a like when you're still there yourself, there's a little like Linux icon that's like in your cyber, in your Windows file explorer. So you can edit like your Ubuntu and stuff directly there, but it's a bit slow. But if you just like copy and paste a few files, it's all right. But yeah, for your Windows programs, it's like a bit slow. So yeah, you probably want to use like a program with like WSL extension or some native program. So yeah, so just initially get your project files on there. You just like want to get clone like inside your Ubuntu. So I've got like home folder there, but you can use whatever you want. I'm pretty sure home folder is like automatically mapped in Lando. So that's kind of nice as well. So you can access like all your projects at once.  Yep. So this is example of how do you're editing with video studio code. So VS code abbreviated. So you saw the WSL extension. Just click like the blue icon, which is in the bottom left hand of the screen. So once it's installed as blue icon, then you can like connect to your WSL. So if you like open VS code and then go like browse folder, it will like try and open like a Windows folder. But once you click the blue icon and then connect to WSL, you click the open folder button. Now we'll try and open inside your Linux. So that is like a list out of other projects here, but it's a list of all your like files inside the projects folder that I got there on the screen. So inside your WSL Ubuntu. So some other options that just like just being like transparent. Yeah, you can run like Windows programs. So you can kind of run like some things. So like the GNOME text editor works like other books. I haven't used it, but it works. I just like seen it work. You can run sublime as I said before, but you need to also make extra library for it's like work. So that's like a display library I think. But yeah, I haven't really like used it much other than just like, oh yes, it like it runs. I did have one time where it tried to close. I tried to close it and it was like, can't write temporary file. I was a bit confused. So anyway, that's just some, you can try other ideas yet that might work, but if you just do codes where it's at. So, whoo. All right, so you can do some like extra highlighting stuff when you're editing using video studio code. So that was the biggest thing for me. When I moved from sublime to VS code, it was like highlighting stuff's gone. I need to like reconfigure it again. So how do you do that?  And then it's got like a settings file per like environment. So you have to go to the, so this one is like, it's got the GUI for the settings. But then yeah, to add all your like, your JSON settings, you need to like get to the settings file. So you go to the WSL tab and then you find some random setting that's like too complex to be edited directly. So you can click the link, open the settings file and then you can put your settings in. So this one is just like runs the login script for the WSL. So by default in VS code, it like just runs a bash without the login like flag. So it won't run any like login scripts if you have any. So that's like how you put it there. I'll put these, there's a GitHub at the end with the examples that I'll put in there. So you can refer to it later. And the PowerPoint as well. Anyway, so the bash profile file is the one like it runs when you open the terminal. And so yeah, you might run some scripts like your like your prompt and things, which I'll go over in a moment. There's some other like settings. So you probably already know all of these. So just like your standard kind of settings, like make sure your like highlighting is there for few PHP files, like which files are PHP, which ones like are not and things.  Add the dollar sign, like remove the dollar sign from the word separators. So like when you highlight text, like highlights are variable. And so that's what also goes in the settings file. Now for the prompt. So kind of got these like mixed up, but this prompt that you can see here, the git bash bash profile prompt. This is like two things you can do in it. You can set your your prompt. So when you shows up, it will have your current branch, maybe like current date or something, or you know, some like the different colors, like what folder you're in, what host name you're using, things like that. And then there's a copy of this from the Microsoft website. You can share like your SSH agent between different like windows of VS Code. So this kind of does, yeah, detects agent and you can add your like private key. So yeah, anyway, once you have the, I'll go back a second, prompt, add it in. You know, it goes from like boring gray to like beautiful green, yellow and blue. I don't know if it's blue, it might be like off blue. Yeah, that's like, I talk it from like Soul Street, but there's other prompts out there that you can use as well. Cool. All right, so another trick you can use with the Lendo. So while using WSL, you're also using Lendo as well. As you can put, you can make your pygmy, your reverse proxy or Lendo site as well. So Lendo does have like built-in traffic, like the built-in reverse proxy. But you know, not everything can use the same port.  So yeah, to do, to have Lendo site served by the reverse proxy, you can make that happen by adding the environmental variables for the site. And then also connecting the MSIO network through the like compose file. So it says there it's connected through for the app server, which is like the default container that runs for your triple recipe. That's got like the Apache and like the CLI and all those kind of things. And then you've got the compose file. So you can't, not that I'm aware of, you can't like put your defined network directly in your Lendo file. You need to like put it like externally. It's kind of annoying, but that's what the network channel file is. So on this screen, you can see, yeah, it's just like a little tiny file, but that's how you put it in there as well. All right, and a pro tip, if you're like multiple Lendo projects, you can do like a Lendo local file. And when you run it, it like merge the Lendo file and local file together. And that's like your result file. So you can change like the name and things like that. Cool, all right. So XT bug. So obviously we'll want to use Lendo still. It's sort of great. Probably everyone already knows this, but if you don't use, probably everyone knows how to debug, but if you only use the result, probably want to still want to know how to do that. So you can just do like XT bug true, like work straight away, perfect, but it's a bit slow, like if you're not like actively debugging. So another way is you can set the files and then add in your flags like manually for your XT bug and then use like tooling. So yeah, I think when showed like custom drush commands, so you can also add like other commands and some XT bug on, XT bug off. So now off by default. And then yeah, you can like turn it on and or like reload the server. So it's great. There's example there of like the link is like where I copied that from. Yeah, this is a transition Apache for your Docker container, but there's like some example on the internet for using like nginx in your Docker container. So yeah, so usually when you're using XT bug, you need like some flag to like trigger it. So you need like XT bug session start or like you set it in your command line when you're running your like your file. But if you want to run like all the time then you need to like inject like PHP file. And this is what this PHP extra overrides XT bug in is. And that's through like the config config, PHP not config, PHP, two configs, it could be used me too. But the config PHP is for the version, but config config PHP is for the extra file. And that's how you set the start with request. So might be useful for Ajax or something, you know, might always like, you know, can't make triple add the XT flag all the time. So that's useful. That's useful. How do you make VS code connect to that? So once you set all the settings up, then you just go add like a configuration. So you go run, add configuration. And then you put some like JSON file in here, which just like tells it what to look for. Probably the key thing is because XT bug three, we're using like 9003, not XT bug two, which is like for the older PHP versions. The show hidden, it's like show extra variables. And then the app, so forward slash app is like where your project is at, that's like default. Everything under your like .lendo file is like maps your forward slash app in your container. But you can like override that to, you know, to put app like somewhere else. But yeah, assuming that you're like using default setup, that's kind of where the path mapping looks like. This one next slide, here we go. Oh yes, yeah, so you just run it and then there's like a debug tab I can put in the photo, but it's just below the file, like the two like paper thingies on the menu. And it just like drops into that automatically whenever it receives a request from the PHP to run the XT bug. So another trick, it's also like the SQL file input process, progress. I've got like trim this one down. But essentially I think Lendo will like add a progress bar. I think based on the file size.  So one way is using the PV tool. So this is just some like fancy if statement to like install PV and see if it's not installed already, but you could just like run it by itself. But if you do like Lendo rebuild and you don't have internet, then you get some error, it's kind of annoying. So that's why I'd like if statement. Yeah, so yeah, so install PV and then you do some commands similar to this. These are also on the goCMS, all in one developer guide as well. But yeah, this is one way you can do it. You can assign the path to some variable, SQL file, compute the size in bytes and then you pop it into the Lendo service. So the size variable gets replaced automatically, but the SQL database needs to be escaped. Sorry, yeah, thanks. Yeah, I do like technical talk, so it's great. Yeah, anyway, and so we want the SQL database to be escaped inside the containers that's where escape it with the backslash. But usually SQL database is a triple nine or 10 or whatever your recipe name is. Yeah, little progress bar, so it's great all the time. Cool, and then yeah, that's the GitHub at the end, so it's got the slides there. I'll add the code later, but yeah, any other questions?