 All right, thanks, June. All right, yeah, so like June said, I am Nick Adams. I live in Rochester, New York. I'm originally from Connecticut. And for a while, I was in London, Ontario. I know a couple of London people here. And so I am the COO at WP Buffs. And so what we do is WordPress maintenance and support. We're a 24-7 team. We've got people on five different continents all around the world, so we're literally 24-7. We cover every single time zone. And that's our website, WPBuffs.com. Also, most importantly, I like to really have a roller coaster. So I really want to start this thing off by really just losing every single person here. And then winning everyone back by admitting that being a Bruins fan because I'm from New England does mean that I am a Bruins fan because the whalers left. And for some reason, it's not advancing. But I'm also a Raptors fan. So I think I just want everyone back. And about to win the Stanley Cup and about to win the NBA championship. So totally true. Pretty sweet that both teams that I love are in the finals. So that is it about me. So today I'm talking about local WordPress development. And so there are a lot of great reasons to do that. The most obvious one that I find is you don't need internet access. I'm someone who I'm all over the place. I like to go to the beach. I like to travel a lot. And so one of the things with that is you don't always have internet access. Even with having your own personal hotspot on your phone, those are so unreliable sometimes that you're fine. And then all of a sudden you lose it. So I love being able to work anywhere and just develop sites without needing internet access. You have control over the server. That's one of the things that I absolutely love as well, especially because there are several great hosting companies out there. But no hosting company ever promises you 100% uptime. And that's on purpose. That's because nobody can promise that with an online server. There's just too many factors. And so I'm guessing probably this has happened to several people where you're working on a website and you're on the deadline and all of a sudden there's just like an issue. PHP stops working. And so it just is giving you errors. It says the PHP module isn't running. Whereas when you're working locally, you don't have to rely on that other host to make sure that your site is running properly. You have full control over the server. And then security. If your website, while you're working on it, is only accessible on your computer, there's pretty much no chance that anyone can hack in unless they're sitting right next to you and hopefully you notice them touching your keyboard. If you see someone doing that, it's usually a security threat for so many reasons. Yeah, cats are the ones who can break this rule. But yeah, so security, for real, when you're developing a site, you may, especially if you're writing plugins or something, you really don't want that to be accessible to the world until you're done with it because you want to be able to test it for security. You don't want to have security flaws sitting on this live site while you're developing it. And that happens a lot. There are bots that can actually scan when, as soon as a website is launched, they can find it and they will immediately try hacking it. Especially because at the beginning of a new website is a lot of times when they're most vulnerable. Especially if you install WordPress but don't set it up, they can actually just set up their own site on your server. So working locally is just awesome for security. You have direct access to the files. This is fantastic for development, especially if you're editing a lot of files. You can just open up several files in whatever IDE or code editor you're using. And you can just edit them and save them and rename them as much as you want without having to worry about sending back and forth between the server. That especially, again, falls back onto you. You want something you can rely on and that you have control over. And if you're relying on your development, sending files back and forth to the server, the second that there's even a mild interruption at the server, all of a sudden, you can't push to live. And so you just end up with delays. I think the remote just died. There's also server caching. Anyone who has ever worked on a live server, especially depending on which one you're on, SiteGround is one that's known for this. They have fantastic server caching. The problem is, if you're trying to edit a site on that, you have to clear four caches before you're sure that you've cleared all of it. And so you can make a change and then refresh. And then the change hasn't happened. So then you clear one of the caches and the change doesn't happen. Then you go and you clear a different cache. And then finally you see your change. Whereas when you're working locally, unless you've put caching on there, there's not gonna be server caching. You don't really need it when you're working locally anyway. And so that's just fantastic because every time you change it, you can change one line in a file, click save and immediately refresh your page and your updates are on there. So that's just the reasons for why to work locally. I highly encourage it for everyone. And so in this talk, I'm also gonna be showing just how easy it is to work locally. So if you've always heard about people saying, like, oh, I build websites locally, but on my own local server, that sounds like something that may be very complicated. But it's actually really easy. Like it's no different than using like Microsoft Word. So just a couple of best practices things I'd like to point out. One of the big ones is naming file versions. This one's really important just because if you're consistently editing files and then you need to go back, this is the same for online, but it's easier to do when you're working locally because you can so rapidly just like edit, save, edit, save, edit, save, then you find out that you accidentally overwrote something or made a change you didn't mean to change. So one of the things I always recommend is whenever you're doing it, it gets a little crazy if you're making a lot of changes. But anytime you're making real changes beyond just like changing the color here or there, especially if you're working on like functions, if you're changing function names or anything like that or using different, using new filters, I always rename the file. And so like I have my style.css, which is like my actual active one, but like if you go into a site that I've worked on, you'll see like style, like only on my local server, I don't push this to live, but I've got like style version two, style version 236, and I do that. And so I actually show that to like use as many as you need to, you know, if you need to get all the way up to up to version 10, if you need to get all the way up to 100, version 100, when you're working locally, I mean, these files are tiny. They aren't gonna slow down your site because you've got, you know, like a whole bunch of like 50 kilobyte files. It's gonna take a lot of files for that to actually add up like thousands and thousands of them. So don't be afraid to just keep renaming files so that you have backups of everything you do. Yeah, you have a question? Yeah, yeah, for sure. Yeah, you can change the file types that it doesn't, you know, show up. Cause if you are editing like PHP files, that is one of those things. If you aren't aware, any PHP files in, you know, in a plugin are active as long as the plugin's active. So you don't want to have excess files. But yeah, so whatever naming convention works best for you, the most important thing here is just make sure you have one that's written out and make sure that it's one that you can understand so that way you can remember, you know, that you had this version and it worked on this version. And then you remember like, oh, I, you know, now I'm on version 13 and it doesn't work. So I need to go back to version 10 and look to see what my changes are. So yeah, whatever naming convention works best for you is definitely a good way to go. Yeah, so Git is definitely another option. I do love using Git, especially when I'm working on like, more like on an actual development server. So I don't, if I'm using Git, I don't actually use like this naming convention. If I'm using Git, then I'm just, you know, I'm using branches and this is more so like, if I'm just like editing a file real quick, which is more so, I don't use Git usually when I'm, like when I'm developing the whole thing locally, I more so use Git when like I'm editing a file locally and then pushing it back to the development server through Git, but definitely if you're using it locally, just use the standard Git convention of branches and core. Oh yeah, yeah, you always wanna make sure you have backups. If Git isn't working for you, then for sure. One of the other things is when you're working locally, if you have a live version of your website, you wanna make sure that you're syncing the live version with the local version. One thing that I've seen go wrong so many times when people are working on a site locally is they copy down the live version to their local and then they work on it for a few weeks and then they're like, okay, well, how do I push my changes back? Now, if you're using something like Git, that's an option, but if you are just editing a site, you don't wanna make a whole bunch of changes over a long period of time and then have your live version of your website become completely out of sync. And I've seen that several times where they say, well, I've made all these changes to the live site while someone else was working on the local site or I was making these changes on local and these ones on live and now they're completely incompatible. There are a few plug-ins that can help with that. Like there's a site sync plug-in, there's MigrateDB Pro that can help with stuff like that so that way any content changes on live can be synced back and forth. What I like to do really is my best practice is if I'm working on changes to a live site locally, I personally pretty much only do that for a certain period of time. So if I'm changing the theme, like if I'm making major theme edits and I wanna work on it locally, I'll pull it down, make no changes to live and then push it back up as soon as I'm ready. But then I also, if I do need to work on it for longer periods of time and I'm working on several parts, especially if it involves changes to content, that's where having a sync plug-in is fantastic because that way whatever changes are on live gets synced right back. So somebody adds a page, it goes on there. Somebody changes a page or some of the content, it goes on to your local server and as long as you've got the plug-in running in both places, that can really save that issue. But that's one of the biggest pitfalls that I see with people working locally is if they have a lot of changes happen. Yes? Yeah, I like Sight Sync by ServerPress. It's a good plug-in. They keep releasing updated versions and they actually are the ones who make one of the local development softwares, software pieces that I'm gonna be showing which is desktop server. So the question, I forgot to reiterate, the question was just if there's a plug-in that I like for syncing. One of the other best practices is using the same PHP version as the host. This is easier in some local development apps as opposed to others. The reason for this is if you're working on something in your local development server has PHP 7.3 and then you're pushing it to a host that's running PHP 5.6, hopefully you're not using a server with PHP 5.6 because that one's been completely end-of-life but I'm finding there are a lot of hosting companies that are still using that. So for security reasons, if your host is on PHP 5.6 or lower, talk to your host and figure out if they're providing long-term support on that or if you can get moved up. But the reason for that is there are several functions that have been deprecated between 5.6 and 7.3 and actually a couple that have been deprecated even just between like 7.0 and 7.3. And so one of the things I'm seeing is I manage hundreds of sites on a daily basis with my team and so we see it all. And one of the things that we see all the time is somebody has somebody building something for them and says, yep, this is all perfect. This works. They push it to the live server and everything breaks and it turns out it's because it was being developed on either an old, more so I see that where somebody's developing something on an old version of PHP. Then they try to push it to the server where some of these functions are no longer available and so if things break because now they have to rewrite the program to make sure that it's the right PHP version. So you want to find out what your PHP version of your host is. If you're not familiar with using like PHP info or other hosting settings, you can usually just contact your host and just ask them what's my PHP version. And that way when you're working locally, you can make sure that you're not using two very out of sync versions because what may work on one may not work on the other. Yeah. Yeah, so the plugins are supposed to say what version of PHP they work with as well. So if it's in the WordPress repository, it should be listed there. What PHP version, what the minimum version is. And so that's one easy way to find out. Yeah, so the question was, what about like when you've got, like he ran into that issue where he had a site that the host upgraded to PHP 7 and then it took down the site because something was not compatible with PHP 7. And so yeah, your best way to do that is if your site is up and working or even if you're on PHP 5.6 temporarily, if the host will do that, they'll revert it. There are some PHP compatibility checkers. I believe WP engines is still out there. And that one, it'll just check for various versions to see does your theme or do any of your plugins have code in them that will not work in PHP 7 or 7.1, 7.2, 7.3. And one caveat about that is that those PHP compatibility checkers cannot figure out if something is in a conditional. So if you've got something that says, if this is available, then run this code. Otherwise, don't run it. These PHP compatibility checkers don't have a way to check that. They can't run that logic. So they can't see that, like, oh, actually, this does work with PHP 7. It just has a fallback in the code. So that's just one of the little things. Yeah. What is this checker? Yeah, I think it's just called PHP compatibility checker. It's just a plugin. Yeah, in the repository. And last I knew they were still using that. In the latest version of WordPress, we've also got the Site Health, which will warn you about your PHP version as well. That one doesn't have the compatibility checker, but there's also a Site Health plugin that's put together by the WordPress core contributors. And that one does have a really cool feature that's called Troubleshoot. And it will actually, only for the person who's logged in, it won't affect anybody else. It will deactivate all the plugins and set you back to one of the default themes, so it'll be like 2019 theme. But that doesn't show to the world, and so you can actually then turn them on one by one to see at what point it breaks. So that way you don't have to test those changes on a live site. But the other option is, test that locally. When you're setting up your local server, choose a PHP version that's at least seven, at this point, at least seven dot two, because seven dot o and seven dot one are now being phased out. So I'm gonna compare a couple of the local server options. So MAMP is one that despite the first M being Mac, it actually does run on Windows. So this is one that's really popular, especially with people who are not building WordPress sites, which as you've seen probably by the numbers, WordPress is now like almost a third of the web. And so at this point, the number of people not building WordPress sites is getting less and less, unless they're professionals who are building like custom built, custom coded sites, and they're most likely not using MAMP, they're gonna use one of the other options that I show. One of the pros is that it is free. MAMP does have a pro version as well. And so the free version does work, it just doesn't have all the features like the ability to give it like a domain name and said it does things by IP, but it's free. And it is stable. MAMP is compared to some of the other options, it is fairly stable. And so that's a great one, especially if you're on a Mac, MAMP works really well and you can just keep running, keep working on it for hours and nothing's gonna break. And it is cross-platform. Version five is only available for Mac and version four is available for Windows. It does have some cons though. It does not auto install WordPress, which means that you have to download and install the WordPress files. It also does not auto create a database for you. You have to go into PHP, MyAdmin and actually create that database that you wanna use and then you can go in there and set up your WordPress site. So this makes it a little less user friendly for WordPress users compared to some of the other options because it requires several extra steps. It's also not easy to change PHP versions. It is possible, but it's not easy. And so that is just not a great option for if you need to test multiple PHP versions, there are some other options that work much better. So a couple of things about using MAMP are just that it has a little weird of an interface. And so I'm just gonna pull it up real quick. Hey, you have a question in the back? Yeah. Uh-huh, yeah. Yeah. All right, so with MAMP, you just saw that startup process is pretty quick. It's just got the power logo and it says start up my website. And so you've got your website, which right now I don't have anything running on MAMP, but you can access here. You've got some tools. You've got like your PHP info and that's where I was talking about, like you can check your PHP version right here at the top. So this one's running on PHP 7.3. And this is where you've got like the PHP MyAdmin for managing the database. So again, this is stuff that's a little more advanced than what some people are comfortable with. If you use PHP MyAdmin all the time, you may have no problem with this. But if you really don't feel like creating your own database every time and installing the files in the right place and going through the actual editing of files, of a certain file to choose a different PHP version, this may not be the best option for you. But that one, as you can see, fairly simple to get started. You click that, you install it and then the first thing you see after it's installed is that first page, that first popup that I showed where you just press the power button that says start the server and then it just goes. They do have a cloud option as well, which is that one's a monthly paid version as opposed to the yearly paid version for MAMP Pro, but that one, it works pretty well. I mean, cloud is nice because it gives you access to more places than just your local one, which you can do with MAMP. You can access your site from other places like within your network. So like if you wanna check it on your phone, you just have to do it by IP address and then use the right port. So the next one is desktop server. This one is really popular in the WordPress world, but it does work for non-wordpress as well. So this one is by ServerPress. Pro is it's free. The free version, they have a free and paid version like the others, and so that's always nice. If you wanna get started, you're only working on one site or a couple sites, you wanna just try it out without paying for it. You can try the free one and you get a whole bunch of features. It really comes only a few features you have to pay for. Usually with desktop server, what you have to pay for is to get more than three sites. Desktop server has built-in local SSL. So that one's great for any time you wanna test something that requires, you wanna check that like HTTPS works. Local SSL is fantastic for that and really, really necessary. It auto-installs WordPress. That one's clutch, so it's just one click. You choose that you wanna use that and it will auto-install the WordPress site for you. It does have some cons. The free version is limited to three sites. You can't change the PHP version. Technically, that's true. You can hack it to different PHP versions but it's not built-in, like it's got a PHP version that it's set to and that's what it sticks with unless you go in there and you're changing the configurations. So now I'm gonna pull up desktop server for you just so you can see. Again, so far all I've done on this is installed the software. That was it. Didn't do any extra setup, so setup is really easy. First thing is it asks, do you wanna restart desktop server with privileges? This is because it has to make some changes to your computer, so if you are on a Mac, it's gonna make you put in a password. If you're on Windows, that depends on whether you have set up the security feature where you have to approve things by an admin. But then you can start the features. It's got a couple of really cool things that they built specifically for themselves, which is an admin color bar. I actually really like this one. If I'm working on testing something locally and I've got the live site is I can have two tabs or just side by side of working on a site and I test it on my local server, test it on the live one. And this changes the admin color bar at the top so you can change it. It'll be a different color than the WordPress one, which is really nice because if you're looking really quick and you're doing it back and forth several times, your brain might start to mix them up and you forget like, oh, which one's local, which one's the right one? So with having different colors, it's just a nice cue. They have an airplane mode so that anything that relies on being online, it'll stop those functions so that you don't start getting errors because you're disconnected from something. You've got a database archive. You've got debug and trace is a huge one when you are fixing a broken site. You can turn on debug mode on a live site. Problem with that is that also can give away to anybody who might be malicious. If you put on debug mode live and somebody can see like, oh, there's this error. They might be able to exploit that error. So having a debug and trace to find the errors on local are really nice. It has CLI. So anyone who's using the command line interface for WordPress and knows just how incredibly fast you can do things with WP CLI will love this feature. It's amazing. Sean Hooper is not here this week, but he's an Ottawa guy who gives a talk on CLI several times a year and he can show you how you can do pretty much everything in a WordPress site like 10 times faster just by using CLI. And again, it's got that local SSL. So when you start it up for the first time, it's gonna run through the start the services and then it'll say done and then you just click next. And if you have a website, it will give you the option in the middle, which is remove or copy or move any of those sites. I wanted to show you what it looks like the first time you load it up. And so you've got created development site. And so this is where it's nice. You get to choose whatever domain name you want for it because it's gonna use .dev.cc. Everyone used to use .dev, then Google decided to buy it because they're Google and they can do whatever they want. And so .dev is no longer a safe one to have because that is potentially an actual real site. So you're gonna run into all sorts of DNS issues if you try that. So they switched over to .dev.cc but you can change it to whatever you want such as go raptors.dev.cc. Eight o'clock tomorrow night, everyone watch. They're gonna win game, the next game because Golden State Warriors are overrated. And so the one thing about this is right now it's on the latest version of WordPress but one thing with desktop service does come with whatever version is like at the time that they put out the version of desktop server and so it can start to get outdated. So one thing to keep in mind is when you choose that you're probably gonna need to update the site as soon as you've started up. Otherwise you may end up with an out of date version but you've also got the option. So if you choose the WordPress version it'll install the database, it'll install WordPress and you can just get started just like you're working on your live site where you've installed WordPress but it also has the blank option which is really nice if you wanna use something else. Like I do a lot of presentations where I use reveal.js and I actually use desktop server for that when I'm testing it out and so things like that anytime you're building a site that's non WordPress or you just wanna install directly from what you have like maybe you want an older version of WordPress you can choose the blank version and then it's gonna show you right there where your files are. That'll change depending on what person it is. You can choose different places so if you wanna drop your website somewhere else you can do that. And one thing I like to do with that is sometimes I will drop it in my Dropbox so that way it's just automatically adding a backup same with iCloud or Google Drive. You can drop it right in there and that way your files are just automatically being backed up to the cloud as you work on them. So then when you just hit create it runs through this thing and then it's going to tell you that your website is ready to go. So this one has a few more steps and so right now there's nothing there because I chose the do not install WordPress versions because I didn't feel like going through the whole thing but other than that when you're done with that it'll just give you the option to remove a website again you can stop the services which is what I'm gonna do because I have one more to show up. So as you can see MAMP was definitely of the three that I'm showing today. MAMP was the most difficult to work with in terms of like technical stuff. Desktop has the most number of options which can be seen as a plus or minus. The one minus of that is that you have to go through like several steps to get your WordPress site set up. So the other option to talk about is local by flywheel. So this one is by a hosting company which makes it a little bit unique and it does have an extra feature in that it's connected to flywheel. So if you're a flywheel customer this may be the best option for you but again local by flywheel is free and you can change the PHP version. You can also switch between engine X and Apache. So depending on what engine you wanna use for your site and you can change your MySQL version. So that's super nice. This really gives you a nice like graphical interface but it gives you a lot of flexibility. So you can really try and match your live server. And these ones right here the PHP versions that gives you the MySQL versions and jumping between engine X and Apache you can match pretty much most like every of the main hosting companies you can match whatever your live server has. So if your live server has PHP 7.1 you can change that if it's running engine X you can change that. And same with like the MySQL version if they're on 5.5 you can move these around. That's really nice and that's really clutch if you have a site where there's a potential that what you're working on locally might not work in the live site if you can match it like you can with flywheel it's really just it eases you because you know that like yep you've got the same software behind the scenes running it so when you push it to live nothing's gonna break on you, hopefully. I always say hopefully because I can't say nothing's gonna break on you. WordPress is always fun like that. Actually that's all web development. Something works fine for six months you test it over and over thank you. And then you push live and something breaks. So I don't wanna make any promises. The one thing about local by flywheel is it uses virtual box. The one somewhat annoying thing with running that is that if you try and run multiple sites there's a potential that you're gonna overload your computer because that can get really resource heavy really quick. If you're running like an eight core processor and like 16 or 32 gigs of RAM have at it have open up 10 sites you should be good. Local by flywheel, I don't wanna disparage anyone but it's been known to be not stable. It'll work fine like you started up 10 times in a row and it works fine and then on number 11 it might not work. And all you have to do is just reinstall it. The problem with that is you're losing time and if you need it in a crunch like you're about to show somebody like present the website there's a chance it may not run. It's been a while since that happened to me where I opened up local by flywheel in it and it just didn't run but it happens and it's kind of a known thing. You'll see it on Twitter a lot but everyone loves to complain on Twitter so I only kind of take that for what it is. So the last, that's the last one I'm actually gonna show you. And so this is what the startup process again this is what it'll look like right when you've installed local so right now it's starting the local machine it's starting virtual box so this one takes a little bit longer to actually start up but it's the easiest to set up. So I find it is, oh this would be ironic if this was the time it doesn't start too. Sorry to question whether it's gonna do that. Yeah, I don't have any others running. This could be my fault because I'm, oh there we go. I can say it because I'm jumping between local servers so I might have just overloaded it a little bit. So real quick you've got super easy you don't have a site there so it'll just tell you straight up. There are a couple things here this is where you connect it to Flywheel so if you've got a Flywheel hosting account you can like pull and push back between that which is really nice. And so they've got a couple of add-ons I'm not connected to the internet right now so I don't have the options. They aren't really anything that I've ever used anyway. There's only like two add-ons last I checked but it's super easy create a new site you can just choose the name so go Bruins. And so it gives you a couple of options and advanced options but you don't have to use them. So that's like for example you can change the domain. By default local uses dot local because that one's also currently not a top-level domain. I would not count on that though because that seems like something that somebody is gonna start selling dot local. So don't plan everything based around that but they'll also let you know because when everyone had to switch from using dot dev it was fairly painless. They created things in there. You can just like the just like desktop server you can choose where your files go and you can use a blueprint. In this case it's a little bit different. You can actually, you can create blueprints which is nice too. So if you are repeatedly spinning up similar sites you can use that within local which is really nice. So you've got this option which is the preferred which is just their default and they're defaulting to PHP 7.2.9 and they are using by default Nginx. They are using varnish cache. So that's one thing to keep an eye out for. Super easy to clear out though. And MySQL 5.7. It does give you all these options though which is super nice. It goes all the way down to PHP 5.2. Please don't build a site on 5.2 because you are so gonna be hacked. And so it lets you choose all the way up to 7.2. I believe it'll do 7.2.9 is like the default. So 7.2.0 is the lowest. So they don't have 7.3 on there yet. But you can jump between Nginx and Apache which is really nice because if you're running Nginx most of these other local ones are only gonna run Apache. And so to be able to have that just so you can duplicate it and say for sure, that's so nice. And then you've got MySQL 5.6 and 5.5 has available options for custom. It's gonna default to 5.7. This is where it gets super easy right away. So rather than you having to go through the normal WordPress install page like you normally do anytime you install WordPress you can totally just create this and don't use the username admin when actually creating a site. And also I use the password admin. But this is local so I'm not ever gonna put this online. Nobody can ever access it. But those are just a couple things to keep in mind. Always use a very strong secure password. Don't use any words in it and never use the username admin because that's the number one that bots are always trying to hack. You can set up a WordPress multi-site install for both sub-directory and sub-domain. So this one is really nice and you can also do that in desktop server. I forgot to mention that that you can set up multi-site which is really convenient. I believe multi-site only works in the pro version of desktop server. They're both like $100 a year for MAMP Pro and desktop server so it's not too bad. But this is what you get once you've created the site. It gives you all this information which is really nice. None of the others make it quite this easy. It shows you your PHP version. It gives you the ability to change. So if you've started on one version of PHP, you can actually change it while you're working on the site and then you just restart it. That's super nice. Nobody else does that. And so that is, it's not gonna let me do that right now. But yeah, so that's a really nice option. And then very quickly, you've got access to your database. They use Adminer and so that's just a really easy way to manage your database. You've got again the local SSL which is nice and you've got MailHog. So this lets you, if you're doing something that sends emails, this actually lets you check those so that way you can see like did the email actually send. That's great when you're dealing with like WooCommerce sites where you need to make sure that all those emails go out properly. And then when you click Admin, it will just bring you right to the login. And so as you saw, I didn't have to actually like create anything on the site. It's just there. So that is it for local by flywheel. So really that's a real quick, just gonna mention Docker is like the pro version to use. Docker is fantastic because you can actually perfectly match pretty much any server you want. It does require a lot of setup. So this is one, the reason I'm not showing this, this is one like if you're like a high-end dev, you're building stuff that needs really custom, you can run multiple containers easily. So if you're using something that is using endpoints, Docker is great for that because you can run both ends of whatever software you're setting up. It's difficult to set up and it is unstable at times. Mostly it'll just, it'll overload the site or overload your server depending on what you've got going on. But that's really anytime you're running multiple things. So not really gonna talk much about Docker, but check it out. If you're looking for something that's more robust than those ones. I think I only have like one minute for questions. Do I have any questions? Yes. Option for local development. So for Linux there are, I believe desktop server, I don't know that they've put it out yet. They have been working on a Linux version. Yeah, last I knew they were, at least it was discussed. I don't know what the status is on that. Really on Linux, I like to use Vagrant personally. Yeah, just because in Vagrant, I find, or in Linux, I find that that's the best option. Usually when I'm doing local development, if I'm using a Linux server, it's usually an external one. So I'm actually running it as an Ubuntu server. So I find that works best is just to run Ubuntu server when you're working locally. That's just really nice. Yeah, any other questions? All right. Well, thank you very much. I'll be hanging around all day. If you think of any more, just tweet me at Nick Adams TV and use the WC Hamont for the hashtag. And I'll keep an eye out.