Laravel Cloud CLI: Deploy and Manage Your Apps From the Terminal w/ Joe Tannenbaum

Terrible. I should have got cheese. Hi everyone. I love it started just on the cheese part so they didn't get it. My like we're just having a pre-con conversation about cheese. You know how it is. As you do honestly as as one does. It's Wednesday after all. I barely know what day it is. Yesterday I thought it was like Thursday. It was Tuesday. Post EU. I thought Friday was Monday because I just was so backwards from like working and I just I I was I was like, "Oh, but then tomorrow I got it." And I was like, "Oh, wait. Tomorrow's Saturday. Sweet." Yeah. So, it was a it was a pleasant surprise. I thought I had a whole week a whole week ahead of me. No, it was nice. You because you got back on Thursday, right? Like probably late Thursday. I got back on Thursday. Uh I took one day to myself in Amsterdam. I always these conferences are always like I I I get done and the next morning I'm on a plane at like 8 am and I was like let me do let me just do for once I'll just take I'll just wander a city and just get to know it for a minute instead of like being inside a double tree and a conference center you know but it was nice. No, that's smart. I need to start doing that. Devon had messaged me and he's like what are you doing? And I was like I fly back in like two hours Devon. Yeah. Yeah. I was just grateful for a little alone time. Just uh you know, it's a very rare thing these days. And so it's nice to just walk around. I did like did like 20,000 steps or something. Like I I really walked around. I was very happy with that. That's nice. I loved how walkable it is. Like Amsterdam's lovely. Probably like that. Yeah. It's one of those cities where like you imagine it and it is ex it is almost exactly aligned with how you imagine it being, right? It's one of those rare things where like the expectation meets reality um immediately. It's it's really beautiful. I like it there. I agree. I want to go back when I'm not just in a conference center the whole time, too. Yeah. Yeah, I know. I know. Let's see. But hi, everyone. Good afternoon. I went to do it. My mouse went away again. Good afternoon, Vincas. Welcome. Welcome. We got a Let's Go Joe already. I love the hype. There we go. I'm gonna give couple a minute or so for more people to come in and then we'll jump into it too. Um and Joe and I were just talking about Lariu cuz we were both at Larani last week and still I'm starting to feel like a human again after jet lag and sleep deprivation. Think think Joe getting there too. I'm pretty close. Yeah. I you know it's funny. It's like when I did um Australia, I used what is that app? It's like day shifter, time shifter, sun shifter, something shifter or something. And I used that app and it it was so helpful to say like you need to stay up till this time the first day so that like it trips you back on the right time zone. And I just had very little jet lag in Australia of all places. And I just got walloped this round. Like it was it was tough. I was I was a very sleepy boy the entire time. But it was a great conference. It was so nice to meet so many people I hadn't met before. It was my first EU. It's very exciting. Was it your first EU too or did you speak? Oh, nice. Great. Cheers. Yeah, it was my very first one last year. I joined Laraveville because I think wasn't it in February last year? I I believe so. Yes, I believe so. I joined Laraveville March 24th. So it was before have you label less than a year or just I guess just about a year. You're coming up on a year. Oh my god. Wow. That's so that's amazing. I didn't realize that. It felt like it feels like it's been longer. I know. You want to know the crazy part too? Yes. Besides that I the week I joined Laravel last year, it was March 24th. The next day was my first ever conference talk. What? What? Wait, what was March 24th? What was that? Um, it was like It might have been 25th or 26th, but it was Epic Web in Utah. Like a JavaScript. Yes. Yes. Yes. Yes. Mhm. Yeah. Yeah. Is that the Is that Kent? Does Kent run that? Epic Web. Yeah. Yep. Cool. I don't know if he did it this year, but he did it last year. And so that was Kent um Kit C. Dods. He had that conference. It was one day. That was my first ever conference talk was a little like five minute lightning talk. Wow. That's amazing. Excuse me, sir. See, I was trying to fix a banner thing, but I guess we can get into it. Also, Chip said it was time shifter. Time shifter for the time shifter. I knew shift was in there. Um, and it was really, it was super useful. I mean, I had to basically stay up for like 24 hours straight to like get onto the right time zone because of the the timing of my flight and stuff like that. But um it was dead on. Like it really uh it really like tripped me exactly into the right slot and allowed me to like get going and hit the ground running which was awesome. Yeah, I I highly recommend although nowadays you can probably just punch it into like you know your chat of choice and it'll just I mean that's what I did for EU and then I didn't follow the directions and then I had a very bad I had a very bad time in terms of jet lag but a great time in terms of the people and stuff. I think it's direction, too, though, because Australia, I didn't feel jet lag. I also slept most of the 16 hour flight to Australia. Yeah. So, that probably helped. But I got to Australia, I was perfectly fine. I got like walloped on the way back home. I felt like bad for a week. But here in So, in Denmark, I was super jet-lagged for Copenhagen, but also here, I was super jet-lagged. I couldn't sleep. I got like one hour of sleep for my talk. Yeah. Yeah. Yeah. Yeah. That that's that's the worst. That's not fun. No, but we're not just here to talk about jet lag. Sorry. Oh, this isn't the jet lag stream. I'm so confused. Yeah. No. Uh, now releasing Laravel jet lag coming soon. No, but uh Joe and I are here today to talk about the Laravel cloud CLI. You might have seen um Laru last week. We launched um the Laravel cloud API and CLI for general access during Larconu. Taylor even used the API and CLI during his talk like in the really cool demo he did. And Joe Tannen Bomb who's here with me today actually worked on the Laravel cloud CLI. So we're here to talk more in depth about that today. Let's do some quick intros first. Uh my name is Leah Thompson. I am a Devril engineer at Laravel and I interact a lot with our online communities. If you show up to stream, you might have seen my face way too much. Today I'm with Joe Tanden Bomb. Joe, would you like to do a quick intro? Uh, sure. My name is Joe Tannen Bomb. I am the open source lead engineer at Laravel and I'm currently just sort of imagining what Laravel Jetlag would be and I'm trying to come up with it. It's like it's the opposite of Jetream. you would just have a starter kit that like works terribly like you just have like a really tough start to your app like uh just it's a challenge up front right Laravel Jet would be a challenge up front that you have to overcome in order to like I don't know terrible anyway we're here to talk about the cloud CLI not not a hypothetical terrible package no you made me think and I'm like imagining too um like you know how time zone conversions is already a pain I'm imagining the starter kit has it built in where it's like doing the conversions wrong or something Wait. Oh, it wrong. I was like, actually, jetlag is an interesting an interesting package name for a time zone conversion package. That's just fun. That's just fun. I like that a lot. I like the weird connection connected tissue there. Well, now Laravel Laravel Jetlag might be coming soon. Let's build it live on stream. Uh, right now. Let's grab the CLI. Oh, wait. Chip said travel tips with Leah and Joe. Yeah, this is a I don't think we've said a single tip. Maybe maybe time shifter. I think otherwise we've been just saying how good or bad our experiences have been. Sleep on the plane. Arlo, don't always sleep on the plane. That's not always the move. Actually, that's true. I think our tip is um don't listen to the app and then get there and have terrible jet lag. That was our tip. We didn't say they were good tips. We just said they were tips. So, you know. Hi, Zane. Welcome Jetack trademark push pack. How are you? What's up, dude? Hi, Florian. Yeah, how dare you be late? You miss very important stuff. We're talking about jet lag. What meeting was more important than this? I can't imagine. I know. I'm a little offended. Okay. So, yeah. So today we're here to talk about the cloud API and CLI which they let you interact and automate your Laravel cloud infrastructure from your terminal, your scripts or your CI pipeline. Um so let's kind of get into who the Laravel cloud API and CLI is for and why it it exists a little bit. Sure. So uh we recently made the the API public, right? So you can interact programmatically with uh your cloud applications. And so to accompany that uh we basically have a onetoone corresponding CLI. So this is both for humans that want to interact. It's for me it's for Florian. Uh it's just Florian. It's just for Florian. We built it just for Florian. And he seems to really like it. So mission accomplished. Um yeah. Yeah. So it's basically like if you want to interact with your cloud applications, with your cloud environments, with your cloud environment variables, whatever whatever you need to do in cloud, you can now do straight from your command line. And furthermore, um you can interact with it via your agents uh via via agentic. Well, train of thought went out the window. If you are using AI, you can instruct your agents to use the cloud CLI to interact with your applications as well. So you can kind of use natural language to interact with the with the API as well via the CLI via your agent. Um so yeah it's basically it's for humans, it's also for robots. It's also for Florian. It's for everybody. Yeah. So basically anyone who uses Laravel cloud can man my train of thought too but can use the API and CLI to kind of improve their workflows too because well if you're a human using it right it allows you to deploy straight from your terminal without having to go to the cloud interface or if you are um like I know Florian did a demo during the like our 12-h hour cloud anniversary stream where I think he was using the API with his um open clawbot to actually deploy to Laravel cloud from his bot. So it seems like anyone who is using Laravel cloud can really benefit from using the API and CLI. Totally. So yes. So the API uh we love to programmatically you know interact with these things. So like the API really allows you to uh set up orchestrations and set up sort of programmatic flows. So if you want to trigger something to happen in cloud when another thing happens, you could just sort of like connect that pipeline together. The CLI makes it um even easier because you can run it in interactive and non-interactive mode. So we've we've taken great care to get both of those things in place. Um, so yeah, it allows you to basically programmatically easily programmatically interact with your cloud environments and um, you know, if you want to update your deploy script straight from your terminal, you could do that. If you want to up, if you want to add an environment variable without having to like leave your terminal in the environment you're already in, you can do that. So, it makes everything a little bit easier. We're really trying to like grease the wheels for you, make it make it easy. And if you want to hop into your dashboard straight from the terminal, you can also do that. We're really like trying to get you all different ways. So like make it as easy as possible for you from a bunch of different directions. Mhm. What I love about this too is already you're mentioning different ways you can use it that I didn't even think of yet because I was just thinking of the like changing something and instantly like pushing or redeploying to cloud and I didn't think of like updating ENB variables or even like opening the dashboard from the terminal which is really exciting to me. No, we have so so every everything you can do in the API there is a CLI equivalent, right? So there's a onetoone there and then we have a couple of extra commands that are I call them orchestration commands because they're they don't map directly to one API call. So like the vast majority of the CLI is very cruddy, right? It's like you know application get, application delete, application list. It's very cred oriented. But then you have like cloud ship, cloud deploy, cloud uh command run like these things. While the command run does actually uh corresponds to an endpoint, the way you interact with it is a bit different than you would um it it works differently than the C crowd ones because it it waits for like a response to get the the response from the command back. So there are also other commands that are a little more opinionated and try to make educated guesses about exactly what you're trying to do and fill things in for you. You get to, you know, choose exactly what's going on. But ideally, the way we've put it together is you just kind of keep pressing enter and it should always be basically correct based on your application. Does that make sense? I kind of went off on a tangent there. No, it made sense. I'm also like reading chat at the same time. So my brain's trying to multitask actually compute things. I think one of the benefits of having a local CLI that interacts with cloud is that um it can make it has access to your codebase. It has access to you know it's and it's it is just saying like what packages are installed what might they need in cloud based on those packages. So if we detect like you are using reverb the likelihood that you need a websocket application just went up you know to 100%. Because you probably need one up in cloud. So we can offer that to you and say it looks like you're using reverb you want to spin up a web application or use an existing one in in cloud. So um yeah we really are trying to we made a lot of efforts to really streamline this for users and make it as easy as possible. No it's really nice. This is making me think too of like before if I had an issue trying to deploy something to cloud um the like agents had no context of that and so they would try to tell me certain things and it it would just be dumb. It wouldn't really be accurate. And now having the API, having the CLI, all of that, I can see how it would unlock that kind of workflow, you know, it would make it easier to work with and give it more context. Totally. Um yeah, you can say like what went wrong with the last deploy and it can now use the CLI to grab the last deploy and see what the error was and then you know understand how to fix it, right? So you can create this sort of excuse me hopefully like self-healing loop of like well we need to update the build script because we forgot about you know npm run build or whatever. But um yeah, it is it is super useful to have the stuff at your fingertips for both the humans and the agents for sure. Which the self-healing makes me think like Zayn said, merge it of like Taylor, right? I love that so much. I'll just merge it. But like we need like the rotary phones to like hold it up. Yeah, merge. Exactly. Watching Taylor practice that in the conference room at at the hotel was amazing because like he would just be like kind of running through it and every once in a while I'd be like yes and just keep going. It was so it's so great. I loved it. I love that he rehearsed it cuz I I think around the time every was in the like cloud hackathon like in that one room I was walking around Amsterdam with Zuzanna because it was way colder than I thought it would be. So I was like I'm I'm buying a jacket. So, where did I go? H&M. As you do, you go to like, of course, a store we have in America instead of like It always feels silly, but it's also like I know what's here and we could just like, you know, get something real quick. Yeah. Also, I learned a hack. Well, we'll get straight back into the cloud. But a shocking hack is if you go to another country, you can download their app um and you can sign up for a new rewards account in that country and get the initial discount. The H&M lady taught me that. She's like, "Hey, do you have an account?" And I was like, "Yeah, I do." And she's like, "Is it in um is it for the Netherlands, though?" And I was like, "No, it's in the US." She's like, "If you sign up again, you can get the initial 10% off." Yes. Whoa. That's the first good tip we've had the entire time. That's really good. That's pretty good. That might be the only clip from the stream and it's not related. We did it. Cloud CLI 10% off in another country. Peace out. Yeah. Yeah. That's the most useful thing that's going to come out of my mouth for the stream. So, in stream. Bye. All right. That's it. Okay. So, I'm definitely going India though because Pushback said next year Laran India. There are a lot of H&M stores in Goa. So, I'm going to go and then we're going to make new H&M accounts and then we get the discount again. So many discounts in India. Yeah. Think of how many sweaters you could get with that discount. Why do they need so many H&M? I live in New York. What am I talking about? They have we have so many HN stores. I was like, why do you need so many HN stores in one spot? And then I immediately stopped. What I was going to say, you could probably get to like 10 in like what, a five minute distance. I could think of three in in a within a pretty reasonable vicinity right now. Yeah, there's a lot of Starbucks in New York. Yeah, there's a lot of Starbucks in New York. Yeah, arguably too many, but yes, there are a lot of Starbucks. Yeah. Also, we have uh Matos here who worked on the API. Yeah, thank you for joining our travel stream. Big fan here. Right back at you, pal. Love that guy. Goes to go up for the H&M. I mean, yeah, right. Exactly. Rainbow was going to be in the comments knowing exactly where Joe lives. Oh no. He's like, I see I see a brick out this window right here and that brick is only manufactured and it's just going to be it's going to be instant. Yeah, he's going to find it. Joe, there's 10 H&M around you in a 30 block radius. Josh covered with a good reference. That's good. I like that. Oh, Josh also had a question. Um, what's your favorite little DX nicity you and the team implemented in the CLI that most people might not notice but was either really fun to implement or slightly difficult? There's so many little things. I think the thing that pops to mind first is when you run anything on the cloud CLI, um it looks at the it checks the git information for your uh local repo and it says is there anything up in cloud that matches that and it automatically picks up the app. So you don't have to select your app like it automatically scopes it down to the app that correlates to the git repo in cloud and that's kind of an invisible detail. you just take it for granted because you're like, "Yeah, I'm in my app. I know. I know this is my app, but otherwise we'd have to have you select the application every single time." And I was like, "Absolutely." It was like the first thing I did. I was like, "We're never having them se like if we can correlate the repo to something in cloud, um, we're just going to shove we're just going to like piece those things together." And if there's multiple, we're only going to limit the selection to the repos that match, right? So like if you for some reason I did because when I was testing I was just like shoving repos all over the place but uh if if you happen to have multiple applications that connect to the same repo for some reason um we'll just limit the selection to exactly those repos. Otherwise if we can't determine at all we'll show you all of the applications and say now you have to choose because we couldn't figure it out from your local setup. But I think that's a nice little invisible detail that most people will probably just take for granted. But we took a lot of care to try to get right out of the gate. So that um it was a pretty seamless experience. I'm with Chip. Uh Chip said thank you. I think everyone should say thank you Mr. Joe Tana mom because that is a great little detail. I like to throw mister in there randomly. Um that's a great little detail to add. It's like during your talk you were like everyone go or go hug Pascal for creating inertia v3. I'm doing that to you but everyone thank Mr. Joe Tannibong. Mr. I feel like a substitute teacher or something like Mr. Joe. Um, actually one of the things that made me happiest kind of you was that I said that on stage and so many people came up to me and said I couldn't find Pascal but here's a hug to pass it on to him and that was like it was so sweet and I really that's so nice. I love I love our community. It's a bunch of good eggs. It's good people. I was sitting back at the swag booth during that and like Taylor was saying there and I was like you said it. You're like everyone go hug Pascal. And I was like, Pascal's going to be like, "Joe, quit telling people to hug me." I know. I kind of lowkey was like, "He's going to hate this." But also, I was like, "I I want people to go." Like, Pascal did a an immense amount of work on allerg and and cares about it a lot and has a really good sense of like what it needs and where it can go and um super talented guy. Love Pascal and uh very grateful for all the work he's doing there. So if you see him, if you if you live in Amsterdam, go not to his house, but if you see him on the streets, you know, go hug him. Introduce yourself first. Make sure there's some context, you know, but yeah, give him a hug. I did hug him and then I did thank him too. I was like, "Thank you for all the work you do for Inertia because it's very exciting." Thank you, Lee. I appreciate it. I did. Yeah, I listen. Sir Pesco. Yeah, we have Mr. Joe and we have Sir Pesco. Yeah, he's definitely nighted which I believe is what that's about. Yeah, sir. Yeah. And then we did get a question we got, so what are we going to build today as a demo, which not really build, but we are going to show off the cloud CLI? Yeah, we can jump into that whenever you want. I can uh I can I can show stuff off. I'm not going to build like an app, but I am going to like ship something to cloud and show you how that works and um you know, show you some of the small details that we put in along the way. Yeah, we can go ahead and share and you've already kind of covered it too, but um the CLI is built on the API. So now Laravel cloud exposes a REST API. It was in developer preview, but now it's in general access. The CLI is built on top of that and this is a first party tool that interacts with that API from your terminal. Um I guess do you want to talk to talk through the conceptual flow real quick of the CLI like it authenticating with oh like from uh from like I don't have it installed to now it's installed and ready to go. Yeah that too. Okay. Oh sorry was there something else you wanted to I thought I guess like the flow of like it authenticates with ooth and then it interacts with the cloud API kind of that as well. Sure. Yeah. So yeah I think so. So um if if you don't have it installed uh you can install it both as like a local package or a global package. I I have it installed as a global package. So it's just you know composer global require laravelcloud- cli um and then it's available to you everywhere on your computer which um is the way that I would prefer to do it but you know live your dreams do what you got to do. Uh but uh yeah once you do that you just do cloud off. It'll bring up um an authentication screen in the web and it'll allow you to check off the organizations that you want to authenticate with cloud. Um and then it'll automatically pick up all of the correct tokens uh from Yep, there we go. From um from that response and save them to a config locally in your home directory. And once you've done that, you're good to go. You can then just start running cloud commands. And the other nice thing to be built in, which I haven't checked since we launched, but I'm fairly certain should work, is that um if you don't run cloud off, anything you try to do, it's just going to it's just going to grab your off in the first round anyway. So that you can just kind of hit the ground running and then it'll continue with the command that you were trying to run. So if you said like if you had an off and you said cloud ship, it'll first off you and then just continue with the cloud ship flow so that it's like, you know, I I was trying to really let people hit the ground running as fast as possible. So, um, yeah, if you're shipping a new app to cloud, I would recommend, uh, if you're going from like I, this is not on cloud yet, I would just write cloud ship. Uh, it'll walk you through, um, exactly what you need to do to to do it. It's a lot of pressing enter or checking things off, and that's kind of it. Um, and then otherwise, you can then interact with your cloud environment however you want. You can deploy if you want to. You can um, run a command. You can list your applications, you can list your environments, you can do you can do anything you would do with the API and it would it's uh it's right there in your terminal now. So yeah, I love that. And then I linked the docs and pinned them. Um this is the docs for the CLI and it does it goes over exactly what Joe stated of what you need to run to install the CLI globally um and all of that stuff as well. But no, that was a great overview of the CLI. Sorry, my question was unclear, but that was great. No, you're good. You're good. See, do we want to jump into the demo then? Show off some of this cool stuff. We're going to We're just going to hope the demo gods are on our side and we're going to do it up. Okay, let's see. I'll cross my fingers. I'm crossing so many fingers right now. Okay, here we go. So, um Okay. Can you see my screen? Okay. So, um, whenever I do, uh, I I have like a a repo, not a repo, directory on my computer called Scratchpad because I, you know, I'm testing a lot of open source stuff. So, I have a raycast that basically allows me to spin up a new Scratchpad really quickly. So, I'll say like cloud CLI demo stream and then it'll just new up a Laravel app um, in the Scratchpad directory. Okay. So, we're going to go like from fresh fresh here. Take two seconds and then we're going to make some modifications to this to show off some of the stuff and then we'll get into it. Boop boop. Also, Zay is helping us with the demo gods, too. He's also crossing his fingers. Thank you, Zayn. Appreciate it. Done. Okay. Oh, I got to do a CD. Okay, so we are there. Let's open this in our ID super quick. Yes, I am going to open something in an IDE. Nobody freak out. I'm going to handw write a little bit of code for a second. Uh, okay. Let's go to screaming. You just can't hear it. Yeah. Uh, this is cursor. I love you, but you make me a little crazy sometimes. Okay. Uh, Leah is and we'll say cool. And then we'll say uh you know I don't know big important thing equals yeser. Okay. So I'm just adding some things that my app needs uh that is not normal to a regular you know an out of the box Laravel app. So we're also going to do our install. You know what? We're on the stream. Let me do PHP artisan so everybody's clear on what's happening. And we're going to install broadcasting with Laravel reverb. Uh, yes, we're going to install this. So, it's going to do this super quickly. Should set up also my npm stuff. Uh, yep. This is making me realize I need to uh aist more things because you were typing R and I was like, what is that? And then I saw you type out PHP Rent. That's why I that's why I switched it out because like I I don't want to type PHBR all the time. I just have R and it uh it rolls through. Yeah, I have a lot of weird little aliases. Although I switched to ghosty recently from warp and like so many things were packed into warp. I didn't make them like transposable. So I need to uh need to fix that. Okay. So we are here in a totally bare code base on my computer. It's a fresh react starter kit. It has got uh Laravel reverb installed and we have some custom AV variables. Okay. Cloud ship. Let's get it up. Okay. We must ship. we must ship. So, we're going to do this to my own organization. This is not a Git repository. Now, I have the GH CLI on my computer. So, if that's detected, it will offer to do this all the way up to the top. So, basically, uh yes, I would like to create one. We're going to go in mine. And so, it automatically picked up from the directory like this is probably what you want for the repository name. Uh I want it private. Uh I want But you can only access Go ahead. I'm sorry. I was going to ask, you can only access like this part of pushing it up to GitHub if you have the GH the GitHub CLI right now. Yes. Uh it just makes it like so much easier to interact with GitHub that way. Um so yeah, right now GH is the only way, but a lot of people have the GH CLI already. Um but if you don't, it'll basically stop and say, "This isn't a git repo. We can't actually ship this to cloud right now." So, but if you have GH, it'll walk you through this if it's not already a git repo. Does that make sense? Yeah. No, that makes complete sense. I don't know if I have it and now I'm like, "Oh, I'm downloading it after the stream." Yeah, defin is amazing. It's great. Okay. Do you want to add commit and push? I do. Sure. First commit. Open one password's jumping in the mix here. Okay. Yep. Yep. Yep. Great. Now we're into the shipping flow. So, if you are if this were was already a repo, this is where you'd start at the application name. So, it's guessing the application name from the repository name. We're going to say, "Yep, that's fine." You get to pick your region here. Uh we're going to go with Ohio. It's creating the application. Call Ohio. Great. Now it's saying, "Hey, we notice there are some things in your envirl env. Do you want to add them?" And so you can check these off or you can say, "No, I don't care, but let's add both of these." Okay, so we're going to add it. And then we're going to say, do you want to do theuler? Do you want to do you want to enable hibernation? Looks like you might need a database cluster. I see inertia is installed. Do you want to enable inertia SSR? And I saw that reverb is installed. Do you want enabled websocket cluster? So, we're going to just do all of these. Hibernate after. And you can you can go up and down to decide how long. We're going to stick with five minutes. Uh we'll do CLI testing. Sure. Uh we'll create a new database. Uh we'll use this is an existing cluster that I have in my account and we'll just use main. So, it's basically just auto setting this all up for you. So, it says like, "Okay, great. Here's your link to the dashboard. Do you want to deploy right now?" Sure. Let's deploy. This is our first time ever deploying this application. Do we want to edit and build the deploy commands before we deploy? So, you can do that right here from the terminal. So, this is this is the deploy command. Yep, that looks okay to me. Uh, we do actually want to do this. So, it's going to update that. And now we're deploying. So, we're going to grab Joe bomb there. There. So, it picked up the application in the environment from the repo and the branch. It said like this is the repo and the branch that you're on connects to the environment branch that you're on. So, off we go. We're going to fix this organization thing in a minute. I'll show you how to do that. uh because I don't want to be prompted for the organization every time I run something on this. But it would be very we're I'm working on fixing this, but I'd have to look through every organization you're um attached to to find a repo to find it. Just it it just got a little too uh query heavy. And we're yeah, we're going to fix that if we can if we can. Um but I'll show you a a workound for this in a second. Um so we're we're building our command. You get live output here. So, as it goes, um, it'll show you what step it's on. That first deploy always takes a little bit longer than the other ones, but it shouldn't be too bad. I mean, I love the ASI art, too. Like the to the cloud, and then the first one's like we must ship. They're so good. A little a little bit of fun. A little bit of fun in there. Those are only on the like orchestration level commands, so we're we're not putting that out in like the Karate stuff. Um, come on buddy. You can do it. I bet you I think we're going to be two minutes. I think we are. This is the exciting part of the stream where you just watch the terminal for output and see, you know, what it says. I love it though. I love it. So, I do too. I guess like a sidebar while we're waiting for this is how did you become the like terminal guy? How did you become the like twoy guy? Um I ask it like is like oh let me just deploy. But so uh let's just go back to this and then I can answer that question. The uh so basically here's your deployed URL. Uh we do want to open the site in the browser and it's waiting for the DNS to be fully resolved because it's still it's a fresh site so it's it's taking to take one second. And while it takes a second, um, it it was because of prompts. Uh, Jess made prompts. I was already sort of like in parallel working on something that was prompts like on my own. Jess made a way better version of what I was making. Uh, there we go. And our that's that's our application. And so if you ever want to do that again, you can say cloud browser and and we're going to fix this in a second. Okay. And it'll just open up. So it knows what environment you're on. It knows what application you're on. It just opens right in the browser. Now let's fix this organization thing for a second. You can say cloud repo config. Mhm. And you can specify for this repo. This is the Joe tannon bomb organization and it's going to and you can specify the exact uh one and it's going to shoot the the one that is most likely up to the top for you. So now every time you do this, it's going to first look at the repo, see if there's a repo level config. And I think if I recall, where is it? Uh yeah, lsla cloud, right? So that's where this config lives. So it can travel with your repo. Um and it's just storing like the the UU ids of these uh of the organization and of the application. So now when you do this, it references the repo config first and it no longer prompts you for the organization like it'll just do that. And so you can say cloud dashboard or just dash because you could do partial stuff here and it'll open your cloud dashboard for this exact app in the right environment right here. So this is everything we just deployed. Yeah. So um let's see we can also do uh let's see command what is it you get autocomplete which is fine. Let's see. PHP artisan route list JSON. And now it's running this on my on my cloud. Boom. This is the JSON. Not very copyable, but guess what? Copy. I can't see because of this share thing. So, if you do this and say copy output, except you have to spell output, right? Um, spelling's hard. And then you say, you know, route list JSON. Again, because this is a local CLI, we can do local CLI stuff, which is cool. So that's our output, but now it's in our keyboard. It's in our it's in our uh uh keyboard. Clipboard. Clipboard. Yowza. Okay. So if we uh No. Format. No. Format document. Great. So look, we have the entire output of that command automatically copied to our clipboard, ready to go. So, we put a lot of little like nicities in there. Um, another thing I like is like, so if we go back here, um, cloud, not cloud, command list, and we're going to pop out here a little bit. Great. So, there's this like data table here, right? So, you can um choose things, you can search for things, although I don't know how useful the search is because trying to find something unique here in this table. Um, so you can search for things and then get the details of that thing right from right exactly from that data table. So we built a lot of like custom CLI components um that might make their way back into prompts in one way or the other um for this. And so yeah, there's a lot of there's a lot of nicities here. Um I can show you something that we might might ship but I don't know if we're going to ship. Uh, so I can tease I can tease a maybe something. I don't know if you want to do that. Do you want to do that? Let's do it. Okay, whatever. We only live once. Uh, let's do CD herd scratchpad and I'll go to ship for swag. Okay, so this is going to be using my local cloud CLI, not the not the one that's published. So, it's going to be cloud local. I I preface this by saying I don't know if we're going to put this out there. I think the likelihood is high. No promises, though. So you know whatever cloud local tinker. So you can just write PHP code anything you want and then submit it and it'll run that in your cloud environment. So it's running that in my ship for swag which is something from layer kind of environment. Now this is all well and fine. Oh wake up. Oh maybe it was hibernating. You can do it. Maybe it is. I mean, it is hump day, but you can do it. Jet lag. We'll see. It had jet lag installed and it so it was Oh, buddy. Come on. Maybe it's shy. It's cuz we're streaming always when you're live. Local dash. What are you doing? You waking up. Oh, this isn't Oh, am I not on a tail skill? Ah, this isn't dev. This might be a tail scale issue. I just realized. Oh no, we got the we got this. Oh, this is a really bummer demo. Oh, come on. A I was so excited to do this. Okay, let's try again. Maybe it just got a little weird. Echo. Hi. Yep, sure. Oh, this is such a bummer. Come on. Oh, man. I was going to show more cool stuff, but if this basic thing isn't working for some reason, the demo god. Well, this is a bummer. It should be doing its job and it's not. I mean, but you got so many compliments about the ask you are and about how Okay, great. Yeah, we'll let this sit for a second and see if it see if it wakes up. Mateo, this is running off of Deb. So, what's that? Matteo said, "Is it my fault?" I was actually thinking about messaging him right now and being like, "What did you push to Dev?" No. All right. Uh, we have people self-inccriminating. Florian's like probably my fault to be honest. Florian, I don't even think you've touched this stuff, have you? Blame everybody except for me. That's That's my policy. That is I'm just hoping it wakes up because it would be so fun to do this, but it's just not doing it. Okay. What is the possible issue? Don't worry about it. Well, we'll leave this on for a little bit. Other stuff. Um, yeah. What else can we do here? cloud list we could do um what else can we do that would be exciting I mean this is everything you can do uh ship dashboard completion so you can get uh tab completions for so you basically uh if you said cloud complet I can't see because of this share thing cloud florian earlier you can hit hide you see where it says stop sharing you can hit hide to the right you can totally hit hide yes can you still see and then if you can't unshare later, just let me know and I'll remove your Okay. Uh, so yeah, you can basically uh set up autocomp completion for all this stuff. Oh man, I was hoping I'd flip back and it was working. That's annoying. Uh, yeah, the big thing is like really the shipping and now you can just sort of like interact with your application however you want. Like this is all just like stuff you do with the API anyway. Um, yeah. So, I don't know. Let's see. Uh, you know, cloud background process create. Perfect. Perfect. Right on stream. Okay. Demo gods are not on my side today. We are not We are not doing it. Okay. I think ship was a good enough demo. We can talk now. Yeah. No, that was great. That was great. Beautiful. Now, just back to mine and Joe. Or do you want to bring it back on stage? Okay. We're just gonna stop the demo for now. It's not on my side. we got a shift though. We got an application from nothing. Not even a git repo to something. So, we'll we'll call that a win. Um, clearly still a bug to fix there. All right. Still working on that. Not push back with the peer pressure. He's like, I am here to see AI deploying your app. Push back. The demo got buddy. You want me to get an agent involved right now? Come on. I mean, I can try. Let me let me do it off screen for a second. Let me see if it'll do it. Um but I'm not now I'm not feeling so confident. Uh let's see. Um new chat say deploy this app to cloud. Let's see if it does it please. No, the demo was great though. The one you did was great. And anyone who live stream should know that these things just happen when you're live. Does not reflect on the CLI or anything. It just happens. Yeah, these things these things happen. Yeah, it's it's getting all it's getting fun actually. Let me see if I can do it with uh maybe Claude knows better. Claude. Yes, sure. Okay. Deploy the deploy. Got to be able to type deploy this app to cloud. So, I don't know why, but you saying like it's in your keyboard now, and then after you pointed it out, I just I couldn't stop laughing about the keyboard thing. Wait, it's in my keyboard now? What do you mean? Do you remember you were um typing something? You were showing the copy the copy thing and you said, "And now it's in your keyboard." Oh, yeah. It's in my keyboard instead of clipboard. Yeah. Yeah. Okay. I can share. So, basically, I This is not working exactly as I'd like it to. I'm not sure. It's really not not my day clearly, but I said deploy this app to cloud. It is now deploying this app to cloud. For some reason, it's still showing output. I don't know why it's thinking it's interactive, but you know, these are little little things we need to fix, but it is deploying. It was able to do that. Um, and it's bopping. It's it is bopping. Um it should be showing JSON and not uh not this output but you know hey you know best late it's deploying we take what we can get. It's deploying but you know all this stuff this is um this was working a couple days ago. So now I have to figure out why it's not working but um you know this is a this is part of like the early software but it's still it's still it's still good. We're still um still refining, still seeing how people use it out in the wild. So, yeah, we're excited about it. And I I use it all the time now. It's the way I typically interact with cloud. I I'm very rarely in the dashboard anymore. I'm just kind of like firing off stuff from the terminal. So, um yeah, we're very excited about it. Yeah. No, I think it's great. And you also used it at Laracanu because um like Joe said, we had a ship for swag booth at Laru. Oh, yeah. where you would fork a repository on GitHub, one that um Josh Siri created, and then you would deploy it to cloud and you have to like go to the site to test it and the pieces were kind of like a little disjointed for it, but then you showed up at the booth and you did it all through the cloud CLI, which I think was like a really cool experience. I think if people were using their phone that's like um a slightly awkward experience because you're dealing with GitHub on the phone and doing you know it's a little bit weird but yeah I just showed up I forked the repo I pulled into my computer and I just said cloud ship and I was like up on that screen very quickly. I think like when you think of that and think of what Floren was able to do with his um bot with the API and then what Taylor was able to do in his demo at EU, it just shows how much having the cloud API and CLI and like general access now like unlocks for people. Yeah, we we want to make it as easy as possible to get what's in your mind to on your computer to up to cloud, right? like we we want to like make that cycle very smooth and and and let you go as fast as what you're thinking, right? So like Laravel already has like all the batteries included, all the infrastructure, all that stuff in there. So it's like that's a great starting point. Build your app and then just hit cloud ship and like let's get it up on the web. Let's get it to a public URL. And and I don't think there's an easier way to do that than just running cloud ship on your terminal. If somebody has a better idea, I'm very open to it. But uh yeah, we want we want you to move as quickly as you want to and really like grease the wheels for you for sure. No, it looks great because like the cloud u the cloud UI itself is fantastic, but seeing you do the demo you did, I'm like, "Oh man, I can do all of this in my terminal. Like I don't I don't have to go to the UI. I don't have to guess like what tab what's like what tab I have to go to for the ENV, which is intuitive. The UI is great, but just like realizing I don't have to leave your friend there. Yeah, for sure. Um, but no, I mean it's it's it's also just less context switching, right? You're like, "Oh, I forgot to I mean, I forgot to add this background process." And you can just literally do it right there in the terminal without having to like fire up the browser, go through the whole process. You can just and and the CLI is aware of uh what org, what app, and in what environment you're on. So, um it all gets picked up automatically and just kind of works. Except for that bug I have to fix. But I think that's like the more people use it, right, the more we can find stuff like that and keep iterating and fixing it. I mean, it's been out a week. You know, these things these things happen. I'm not I'm not stressed about it. It's going to be it's going to be great. Yeah. Okay, good. I didn't want you to be like, "Oh, no. It didn't show." Like, no. This stuff happens to me all the time on live. Even on our like 12 hour cloud stream, I was trying to like vibe code an app and I was running into npm issues and it's because I wasn't in my herd folder. So, it wasn't even like an issue with that. It was just like right my brain. You would think after 12 hours you'd just be totally locked in, but yet uh you know somehow you were tired. How dare I? How dare my brain? Like come on. Someone said, "I love the CLI and looking forward to see the Terraform provider." Okay, Terraform provider. Good to know. I don't know if that's a discussion for something else that somebody had, but I that is not something I'm familiar with, but I don't know either. But I'm glad you love the CLI. Uh oh. Um, there was a question. Hold on, let me get to it. There was a question in our discord actually earlier about the cloud CLI. Okay, I can get to it. Course now I have to open up Discord which always takes a hot minute. Oh, that was kind of quick. Okay, someone said, "Using the Laravel cloud CLI, is it possible to only authenticate with read per uh with read permissions? I want to give my AI access to see settings and read logs, but I don't want it to change my thing or change anything." Um, I know uh I don't want to promise anything at all, but I know that that has been something that's been brought up. So, uh, like tokens with, uh, different scopes. And so, I know that's on our radar. Um, I do not know, you know, what a timeline would be or if it's even ever going to come out, but I do understand the need for it. And, uh, that's more of a cloud team question. I know that there's a little bit of a gray area between we're showing off the cloud CLI, but I'm not actually on the cloud team, but um, yeah, I am aware that that's on our radar and that question has come up before. So I'm sure it's something they're thinking about. So Gotcha. So it's not something that's currently possible. What's that? So it's not something that's currently possible, but something on the correct team radar that people would want kind. Yeah, it's been brought up once or twice since since EU. So yeah. Gotcha. And then trying this tinker again and it's it really doesn't want to go. And it's really just a massive bummer cuz I was like really ready to go with it. All right. As soon as we end the stream, it's going to work. It's going to work. It's going to absolutely work 100%. Oh, I wonder if it's because uh Oh, I can't see it because of icons. Where is my Keep going. I'm just I'm just mumbling to myself like an old man. Don't worry about me. I don't want to interrupt your no your flow over there. Um nothing going on up here. Nothing to interrupt. Uh that so much. I will talk loud to myself and I'll say stuff like what am I thinking right now? And I'll be like I'm I'm thinking nothing. There's nothing up here. Yeah. Just just mumbling. Just doing some mumbles. Um I know you said you use the cloud CLI pretty much um all the time now. Are there any specific workflows you have with it? Like do you have any automation set up or anything that uses like the API? I don't have automation setup. Um I use it because I do I I en I enjoy the lack of context switching. I I like staying I'm already in the terminal all the time. I just want to kind of stay there. And so it's really easy for me to just, you know, um check on the last deployment or like um I I mean honestly like I've been pushing things up with cloud ship a lot because um I'm deploying like a lot of test apps on like either dev or or or production to just test things out that we're working on. And so you know the cloud ship is really great. Cloud deploy is funny because it's almost one that you're not going to reach for a lot because most deployments are just totally automated. But when a deployment fails, that's when you would you would say like, "Oh, I've I fixed something in the deploy script just like, you know, redeploy it." And uh if I recall, I I believe if you adjust the deploy script, it'll offer to redeploy. I might be lying about that, but we we've tried to put in these little like common sense things that it's like, "Oh, you're editing the deploy script. There's a non-zero chance you might want to deploy. We should just offer that to you." So, um, yeah, I haven't set up automation so much as I I just enjoy doing it right there from the computer and not having to hop into the UI to do the whole thing. I especially like that it just like picks up all of these sensible defaults automatically and it just makes it like way easier to uh to spin things up. Um, yeah. I mean, sometimes I even like use it to just like shortcut creating a git repo because the flow is already built in there. So, I'll just like get halfway through ship and then be like, "Well, I got the repo now. We'll just kill it until I'm actually ready to ship it." But, um, you know, it's it's a nice sensible flow. So, it's it feels uh it feels good to use. No, I really like that because it seems quick, too. Whereas, now on the 12-h hour stream, I was trying to deploy something to cloud and I was like, it's not even on GitHub yet. I only have five minutes of the stream left. Get on GitHub and then cloud. And now it would be super quick. Exactly. And and it's it's those like it's those little stumbling blocks that prevent you from saying like I I could just do this right now if not for X. And like I was like how do we how do we eliminate just those little tripping points, right? Because you're right, as soon as you go this isn't even on GitHub yet. Like I just I don't even want to do it. I'm just like all right, I'll just do it tomorrow. But like if you can just hit cloud ship, GH is on your computer. We got you. We'll do it for you. No problem. Yeah. And I feel like that's a big unlock for people who are like not traditionally a dev or trying to get into vibe coding and like programming now that AI enables them to kind of totally like ship things, you know, like build the things even if they don't fully know how to write the code themselves. Having that where it's like, hey, this isn't on GitHub because that might be a step they're not used to. Like I forget sometimes to put something on GitHub and I have a lot on GitHub, but someone who's newer to per you might forget and having it like pick up on that and be able to tell you is like really nice. Yeah, my whole my whole job is to try to make things easier. So if uh you know if anything feels hard, hit me because I would love to make it easier. Yeah. That's the whole game. Uh, Florian said, "Shell history is enough." Okay, Florian. Okay, sure, man. Neoim, by the way. What are we doing? What are we doing over here for Florian? Probably. Yeah, he definitely 100%. 100%. I'm trying to think if I missed any questions. I don't think I did. If anyone has questions, feel free to throw them in um too. I know there was a comment about your computer earlier. Vlad Vlad had said when you were like trying to do the demo. Vlad Oh, wait. No, it wasn't. Yeah, it was Vlad. Vlad said, "Joe, consider buying real computer. That one seems slow." Which I think was a Mac. Come on, Vlad. Come on, man. This is like a I actually don't know what this is. What is M about this Mac? It's an M3. Yeah, it's an M3, dude. Like, what are you talking about? That's good. We're good. We're good. It's good. Maybe I'll upgrade my internet at some point. How about that? Maybe that was the problem. Slow. And then you got a heart. Will I give you the heart? Oh, wait. It's supposed to be this, not this. This is This is an infinity. This is a heart. That looks like you're looking through binoculars. Goggles. That's that guy trying to locate where you are looking at like that brick in the background. They only make those walls on the, you know, No, I'm just kidding. Yeah, it's going to locate you. Exactly. Um, let's see. I think we answered all the questions, though. That was a great demo of the of the CLI, and I truly mean that. That was a great demo of it. It makes me want to go ship something with it because I I've still been using the UI, and now I'm like, I could be so much faster. So much faster. Yeah. Especially because it puts you through the whole flow of like even the deploying part of it if you want if you if you if you want to do that and it's like to to end that whole process with like I've got a fully functioning app that's deployed and up on cloud is like feels I the goal is to make it feel magical and I think I think I think we're I think we're there. I think we're there. I don't know. You y'all tell me. I don't know. It feels good to me. So I'm I'm curious if it feels good to everybody else. Um, and I do want to mention that if you run cloud ship via your agent, um, obviously that's not interactive, so you don't get to select all those things. So there's sort of an opinionated setup that is the, um, uh, I believe we we calibrated it to be like the cheapest default setup that you could have based on your app's configuration up in cloud. So like we turn on hibernation, we turn we like size everything down to like you know the most reasonable versions of all of the instances. And so uh if you're not going through that interactive flow and you just tell your agent like ship this to cloud, it'll it'll it'll make some choices for you that then you can like adjust in the future if you ever want to. No, that's a great call out. Um, I guess like we start wrapping up, is there any other like tips or unlocks or certain things um I guess people should be aware of or know when using this with AI agents? Like are there any tips to like work better with the cloud API with an AI agent? Uh I have found that and we're working on how to specifically uh address this but I found that like I have skills that tell uh the agents like when I say something about cloud I'm essentially telling you to use the cloud CLI. So if I ask you to take an a like you kind of just just point them to the cloud CLI and at that point the agent's really good at saying like list the commands what command cor correlates with what they're asking me to do like that flow ends up but I do find that I need to sort of just like point it in the CLI's direction and say like hey you have a you have a tool called cloud on the on my computer like that's what you should be using whenever I say interact with cloud. So whether you put that in your guidelines, whether you put that in a skill, you know, it's it's up to you where you want that to live. But I have found that even just that little sentence that says like I'm saying something to I'm saying to do something in cloud. I have a cloud CLI. Just go ahead and use that. It it then can navigate that very cleanly because it does uh largely correspond to API endpoint. So it knows how how that works. But that would be my one tip. Does it No, that's a really good tip too. Um, do you have to like pivot the docs as well? Like did you have to like copy in the docs or you just told it like hey I have a cloud CLI and from there it was good to go. Yeah, it's usually good to go. What it what it typically does is when you ask it to do something, it'll first do cloud list to see what all the commands are. And so um and then it'll very quickly whittle down to like oh uh there you know they want the application details that's application get like it because everything is named as it corresponds with the cruddy version of the of the name. So it's very guckable. Does that make sense? Said yeah. No, it made sense. Um because I was wondering that if it needed the docs or if it could just do cloud list and see everything and then figure it out. Yeah, it just runs cloud cloud list or cloud help and it it's able to see That's nice. And then pushback said we'll fix this. Yeah. Yeah, we're working on it. We're working on it. Um I know that we're shipping skills with the CLI. I think we're I think it's already in there, but um I don't know how that works from a global composer install perspective. So, we may need to just like uh you know work with boost to uh check for global install stuff as well. I'm not really sure how it's going to work, but I have faith in he'll figure it out. That does give me a question. I don't know if you know it. Do you know if after you have the CLI in like globally or whatever if um you do boost install if it would prompt you to download that skill or do you need to like go try to bring it in yourself like some of the CLI skills cuz I know if you have certain things like Fortify or whatever set up it will like prompt you and say like hey you have Fortifi do you want to install this skill? Uh to my knowledge right now, if it's a local, if you're installing the CLI as a local package, it should pick up and offer to add that skill for you. Um I don't know if it works on the on the global package yet, but uh that is something that we we are working on now. Yeah, that sounds good. And we did get a question. This one's more cloud specific. that was about for a large scale CRM with high database activity. How does Laravel cloud optimize cost compared to traditional VPS or Laravel Vapor? Um, which to that I'd say it might be worth reaching out to our sales team to kind of talk more about that and how you could like optimize costs on Laravel Cloud. Oop, sorry. And that would also be a really good question for our cloud office hours which the next one is next Friday. Okay. Unless you I do I do not have the answer to that because uh um I I'm a user of cloud but cloud is not my world in terms of like um know knowing it at that level right now. Yeah. I just want to highlight that to answer. And then here's our enterprise page where you could out the form to get in touch with our sales team who could answer more in-depth things um about cloud as well like how it would work for your use case, how you could optimize prices with it and stuff like that. They can get more into the specifics. Um Florine said, "Gonna update my open claw skill to use the CLI now that it's released." Let's go. Good man, Florine. Yeah, good man. Florian and Flowbot. His bot is not called Flowbot and we all call it Flowbot. And he's like, I spent so much time naming it just for everyone. What's it What's it called? Do you know? What's the name? It starts with an A. I I don't think I could pronounce it right now. And I can't remember the whole name. I'm sure he'll Yeah. I love how I'm just like, it starts with an A. That's it. That's all my brain. Abot. Abot. I think it's AE something. Yeah, it's not Metallica Vlad sadly. Good guess. Um, for everyone Yeah, good guess. Uh, for everyone who wants to learn more about the cloud API and CLI, here are the docs for it. I'm going to do it one link at a time. So, here is the link for the API. And then we also have the docs for the CLI as well, which is CLI. CLI words are hard is what Joe demoed today. Um, so if you want to learn more about the CLI as well as like see the installation um command that he mentioned in stream of you get set um how you get started with the CLI. That's all in the docs and that is here here at uh cloud.lair.comdocsappi cli the slashes. Yeah. So today we demoed the laral cloud CLI which is using the API. Both of those are available for general access now and they launched last week during laru. It allows you to access your Laravel cloud infrastructure through your terminal and just kind of unlocks that workflow to allow you to ship faster than ever on Laravel Cloud. And we had the lovely Joe Tan to demo that for us. The demo gods were a little mean, but it was a great demo regardless. A little give, little take. You know, it wasn't wasn't totally bad, but it could have been better. Yeah. Yeah. We'll we'll iron out this shows. This just shows in the future that like this isn't pre-recorded, right? So, anytime we have a demo that goes great, it's happening live. So, this just helps those feel better. Yeah, exactly. Do you have any like closing statement you want to make about the CLI or the I love building CLIs. So if you have suggestions, improvements, uh definitely report bugs, we're accepting PRs. Like it's all I I love building this stuff. I I deeply love building CLI. So um this was a bit of a passion project, bit of something a lot of something we actually needed. And I'm really happy with the way it came out. I know we saw a couple bugs today, but you know, we'll get there. We'll figure it out. We'll we'll iron it all out. And um yeah, I'm excited it exists now. And I think it makes the workflow significantly easier uh to get things up into cloud and to interact with cloud. So, no, it's very very exciting. Like I say that sometimes I'm like it sounds like I'm not excited, but it's generally very exciting. I promise. Um for people to report the bugs, would they go to the cloud CLI repository? Yeah, I go to the GitHub repo uhcloud-cli. Um, and you can you can report report bugs there. I did go and find that link. This should be okay. Larl Yep, that looks CLA. Yep. So, if you notice any bugs or there's anything you'd like to be added to the CLI, go to this repository, open up an issue. Is that the best way? Uh, yeah, open up an issue. Better yet, if you want to open up a PR. Um, and either way though, we'll we'll see it and we'll we'll check it out. And for people who want to find you um off of I guess not just on GitHub to tell you thank you Mr. Joe Tan and Bon for this where is the best place to find you? Uh well if you're Raindrop you already know you already know where I am but uh no you can find me um Twitter Joe Tannenbomb. You can find me on blue skyjoe.codes. You can find my website at joe.codes. You can um I think that's about it. I don't know where else I'd be. The one of those two places, one of those three places. And if people see you on the street in New York, should they go up and hug you like like you said to do Pascal in Amsterdam? Say hello, say who you are, introduce yourself, and then I will gladly accept a hug. Yes. Yeah. Okay. Okay. Um I only threw you under the bus because you did that with me. Always accept Always accepting hugs. always accepting hugs for passion. And here is Joe's Twitter for those who want to follow him on Twitter. It's the same one he mentioned. And yeah, thank you so much for showing up today, Joe, doing a lovely demo for us and um talking about jet lag. This has been Coming soon, Laraveville Jetlag. Yeah. Yeah. This was just like the spoiler stream for that. Yeah, exactly. Exactly. It was just the Easter egg inside the screen. The stream. Um thanks for having me, Lee. I appreciate it. It was a lot of fun. And for anyone uh who wants to find more about these things, go to the links that I mentioned already. We will be doing a stream tomorrow as well. That stream will be with Aaron Francis and Zuzanna to talk about the road to speaking at Laracon. So, kind of answering questions about how you get into speaking at conferences or more specifically Laracons. So, if you're interested in speak at conferences, make sure to tune in to that tomorrow, which I believe is at 10:00 a.m. Mountain time, but I will be posting that. Um, I'll be scheduling that today. So, you will see it on our YouTube and LinkedIn today, and you can go ahead and hit the notify button as soon as that is live to be notified when we go live tomorrow. But, thank you all for tuning in, and I will see you tomorrow. Bye bye.