Celebrate One Year of Laravel Cloud

Okay. Hi everyone. We should be live. Hello. Hello. Good morning, good afternoon, good evening. Yes. Hello. Hello. Morning for some of us. Time zones are so weird. But yeah. Hi everyone. Welcome to the one year of Laravel Cloud anniversary live stream, party live stream, whatever you want to call it. We're going to be here all day. Uh hopefully you'll be here all day with us. Um, yeah. I guess let's go ahead and well, let's say hi to people. So, hi Acer, welcome in. Hi Amir. Um, hi Gurex. Danny Phantom. Oh my god, we have Danny Phantom here. Danny Phantom. That that brings back memories right there. I love Danny Phantom. Oh yeah. Yeah. Happy anniversary Larville cloud. Um, we agree it's the best cloud out there. Proud early user too. Let's go. Starting out strong already. How early? How early? Let us know. Yeah, which I think that's the question you want to ask Josh. Do you want to go ahead and ask it? Yeah, because like that was one of our questions in the Laravel wrapped um that we had put together was was how early of a early user were you? Some people got in technically before the launch date. So are you one of those people that got in before the launch date? How early of a Laravel cloud user were you? What was the time when you signed up for Laravel Cloud? Let us let us know. Or if you remember back to your Laraveville raptor days, what was the 8 days new, negative 17 days new? What what was that? The negative part was so funny. Can't can't solve for all problems. We have Hi everyone. Yo Josh. Hi Joshua. Cloud. Hey Josh. Hey. And I guess we're also interested in how many people we have here who are not been using cloud yet and why. There you go. Yes. Great question, Kristoff. It better be a good reason, but a lot of people about it, too, especially because it's the one-year cloud. So, if you're here, you probably like cloud or you just like Laravel. And then, like, yeah, like Kristoff, like you said, what is what is the reason then? If you love Laravel so much, why haven't you shipped on cloud yet? But it's also like Leah said, um, it's today about cloud, of course, but it's also about having a lot of fun. We have a lot of special guests and games and topics and yeah, I guess we're just here to have a good time and I hope you all too. Mhm. Have a great day. Stay awake for 12 hours. It will be split a little bit. Staying awake is my main prerogative today, but it'll be split a little bit because the Laravel worldwide meetup is today like during this um cloud anniversary stream. So that is still happening from 12. So from noon to 1:15 Eastern time that is happening. Caleb Porsio is still going to be on that and then we're streaming around that for the rest of the time today. So it we started at 9:00 a.m. Eastern time. We'll be going till 9:00 p.m. Eastern time today. Lots of guests. If you haven't seen it, which I'm thinking most people who are here right now, you've probably seen it to know that we were going live. But we have a landing page for this lovely live stream that includes um let me get from here that includes our agenda for today. So everyone who will be on today is in that agenda on the website. Let's see. Sorry, I was trying to find the link. There you go. I pinned the link right there. You can use that link to go to the lovely landing page we made for this live stream party to find the agenda and know who's going to be on during what time if there's certain sessions you want to see. Hopefully, you're here for all of all of it like we are. So, you're hanging out with us. I know. Node 24 stream, Danny Phantom. Sorry about that. Jason, I've done 24. Yeah. Leah, you've done it already. I've done it before on my personal 24 hours. Yeah, I Oh my god. I did Java. I did Java and Spring Boot the whole time. I can't say I'd recommend. Now you're in a much better place. Yeah. No wonder it took 24 hours. That's true. It's true. It's like I got so tired. I also like I worked all day and then I did the live stream. I worked the whole day and then I did the live stream for 24 hours. I I don't It was like It wasn't even that long ago, but when I think of it now, I was I'm like that was a younger version of me. I can't I couldn't do it now. That's one of our biggest issues with cloud that we're just too fast. Every stream or every video that we do, we can't do 24 hours because cloud is too fast for that. Yeah. And using Laravel with AI, right? Because our app would already be done. It'd be shipped. It's deployed. Like what what else is there to do? Our videos get slower and slower with each feature. It's crazy. I'm kind of afraid of my job now that I'm saying that. But Caleb is going to be like, "Oh, why do I need you on now?" Yeah. And now Caleb is bringing Blaze and also something going to be faster. Damn. Today too in the middle of the stream. Yeah, I heard that. Mhm. be a great way to kick off kick continue the party for Laraveville class, I should say. Oh, let's see. We have a good question. Can anyone beat Josh's live stream reading Laraveville docs? It wasn't that long. All things I think it was around nine hours. I I had a lot of breaks in between. Yeah, that was a short stream. Short. It It was overnight though. That was the That was the problem I should have done. I shouldn't have done. I remember uh I I had, you know, my it was the holiday weekend, so my uh wife and kids were going away, and I was like, I might as well like stay up. So, I started at like 5:00 p.m. my time, and I didn't end until around 4:00 a.m. So, that was the bad planning on my part. But it's fun when you think about it. Your family goes away and the first thing that you think about, h I could read the whole dogs while they're gone. Yeah. to reach out. Josh is like, I've been waiting for this day. Just whips out all the finally my chance. Yeah. Oh, speedrun reading dogs. This would be also fun. This one here. Hi, Tech MB. That would be Wait, where is it? That is fun. Hi, Carl. Welcome in. There's more docs now, too, because we have Nightwatch. We have cloud. I I didn't read any of the package docs at the time. was just framework docs cuz I was like that's like another that's another nine hours right there just for packages content right there package by package I'm like picturing all of us doing another like 12 hour stream and it's us like taking turns reading the docs but we're like sitting in a rocking chair reading them like it's Dr. like have to add rhymes. I don't know. People might I bet we I bet we could have, you know, AI make the docs start to rhyme. So like take every word and rhyme it or just like every Laravel comment that Taylor has made like the threeline comment we turn into a rhyme and you read that something like that. I'm picturing this as a children's book now and it putting it in the our merch store. It's just a children's book and it's the doc says rhymes. Oh, that would be perfect. I'd buy your children off. Oh man, it's awesome to see everyone in the chat. Yeah, I'm so glad people woke up early with us. I had to wake up at oh man 5:30 today. I was I asked my husband. I was like, what if I don't wake up? That's very hard. I was like, "What if I oversleep?" He's like, "And she's on a run of no monster, so it's really hard." No monster. I haven't had a monster in like 30 days. Oh, wow. You're still going? I'm still going. How do you feel? I feel good right now. I feel feel energized. We'll see you after an hour. Yeah, let's talk in 12 hours again. But yeah, I might be on the floor. the the camera might be panned down. You might see me like laying on the floor. Let's see. So, it's 1000 PM for Zen Adam. 400 PM for Danny Phantom. Danny Phantom. So good. Yeah. 400 PM. Um James did ask I saw James. Now James disappeared. James had asked earlier, where's everyone in the world? everyone at in the world. We are all in this world. No, I'm in a I'm in a different Mars right now. You could kind of answer that question of like, okay, when you're shipping on Laravel Cloud, which region do you typically choose? Oh, primary region. I like that. Primary region. That's good. I don't even know now. Is it Ohio for me? Yeah, probably Ohio. I think it's Ohio. I got turned to an Ohio man, too. I used to be North Virginia all the way. Yeah, mine is Frankfurt. Yeah, I see already a few of them. Frankfurt, London, for the world. Anybody using our new UAE one out there? Oh, UAE. I think there is. Oh, UAE. I thought you were talking about like Australia at first, man. My brain's still asleep, I think. Uh, we have Ryan. Hi, Ryan. CA Central one. There you go. Typical. Yes, Lar EU. Yes. Who will be there? Laracon EU. Oh, all of us but Josh. No. Yeah. I'm sorry. I will not be there. I I will be there in spirit. I did help build something for the booth at Laracon Oh, that's true. That has to do with cloud. Yeah. My my youngest kid is a little bit too small for me to leave for that long. Oh, yeah. Right. How How is uh new new dad life going for you times three? Right. New dad life times three. I know we're we're about to get into some dad jokes here. So, I feel like I I'm strengthened now. I I I was decent at it and now I have been rejuvenated. Yeah. I I've leveled up to a new inner power, if you will, of that joke. Do you think it's like exponential growth each time you have another child? I I can tell I I don't know about the jokes aspect. It probably is, but I can tell it is exponential growth for my dad look because my wife every every like says like whenever I like leave the house, I'm like, "You definitely look like a dad today." Look, I guess like I could just care less about how I look and dress. I don't know what that means, but for for the parents out there, is that a thing? Do you just start looking more and more like a parent with each kid? Interesting. Yeah. I don't know if each kid adds exponential growth to your dad joke material. It definitely adds to how low you will go in the cringe level of dad jokes. So, you find a lot more things funnier. That is true. I'll be like, "Oh, that was a good one." And then like 10 years ago, I've been like, "That's not even funny." And at some point, your kids's old enough you can't tell them and they probably don't don't like it. I'm already getting roasted. We were going to do app roasting, not Leah roasting today. Like, wait, did Leah read FTW is for the world? Okay, keep all the answers. I'm in my comfy era. two kids in. There you go. That That should be Largo swag right there. Oh, yeah. They should. I don't even have kids. I'd buy that, though. You go. Carl's told the dad joke. This might be a good uh transition one. Carl told a jack joke that you have on your shirt, Devin. That's not too bad. I got a database hat. There we go. The best ad joke ever. Tessa gave one, too. Uh, oh, wait, not that one. Okay. When does a joke become a dad joke? When it becomes apparent. I was uh I was trying to come up with a a dad joke about the cloud, but man, it was over my head. I can't. What do you call a dog that is a magician? What do you call it? A labracadabrador. I was say an abracadabra. I've heard that one before. Yeah. Abracadabra doodle. That's what I was gonna say. Oh yeah, doodle could work too. Oh man, they are very cringe. Like so good and cringe at the same time. I'm like sitting here almost in pain already. I'm also not sure. Is this an American thing? And maybe I'm too European for dad jokes. I don't know. That is a good question. Do does everyone else not have dad jokes? Crystal's like you guys aren't funny. Get some humor. I didn't want to say that, but yeah. Um, I guess I'm not a fan of dead jokes. Hey, Deon, you got another one. Devin. Oh, I got a bunch here. I got to find out the right one. There you go. Pick one. Pick one. Good. I'm gonna I'm got I'm go find one as well. Keep keeping the family jokes. I told my wife she should embrace her mistakes, so she gave me a hug. Yep. Oh, let's see. Um, this one my kids loved. People always say that they pick their nose. I feel like I was just born with mine. Okay. I like that one. That's a good one. I like it. Um. I like this one, too. 215 people already watching. I love it. Hey 250 people, welcome to one year of Larva cloud and longer bad dad bad dad bad dad bad dad bad dad bad dad bad dad bad dad bad dad bad dad bad dad jokes oh yeah and be sure to what what's the the the link is in the description and pinned right Leah for people to sign up for giveaway yes that's on the live link is in the description um for LinkedIn and YouTube. Um also, let me put it back here and pin it again. There you go. If you go to this link, you can find the agenda for today, but you can also sign up. So, there's a form at near the bottom, and if you sign out, sign up, fill out the form, then you are entered in to win giveaways later today. So, we'll be doing giveaways today. We'll be giving away cloud credits, a bunch of goodies. So, make sure to go to that link and fill out the form there. You can only win the giveaways if you do fill out that form because that's what we're going to be looking at to get the information. I already see a few questions about Lava Cloud. We will also have later some guests on where you can also um post them and then we have some time to tackle those as well. I love it. Technically, you could probably by the time you are hearing this and seeing this right now, you could sign up for a Laravel cloud account. You could learn Laravel, use Laravel boost with uh with your preferred AI agent of choice to make a Laravel app and ship it probably within the next, you know, hour and a half, two hours and then uh could say like, "Hey, you shipped something today." And then send us the link. Perfect. Dad joke generator voting on if if Devon's jokes are better than mine. I like that one. I think you've already won that one, but you got you got another you got another one, Devin. We make an adj There you go. Using the AI SDK. Easy. So, so here's one for you. How do you comfort a JavaScript bug? You console it. Oh my god. The way I was so confused. I was like, what is this gonna be? I'm sorry. Doesn't even doesn't even work for doesn't even work for PHP. You can't be "Oh, do you know why the PHP developer quit his job?" Why? Because he didn't get a raise. A raise. I like it. I like it. See, I don't have any I don't have any good tech ones. All mine are like All mine like hinge around they're either like ones I found or ones I've made up around like kids and like stupid things. So like I'm not going to lie, I went deep and I I opened up Claude and I was like I'm having a battle for dad jokes. I need the cringiest developer jokes you could possibly get. So I literally could just ask it for more. There you go. You've got it all set up. I don't have a Here's not a developer one, but here's a here's another one. Um, so I I ate a kid's meal at McDonald's yesterday. Uh, his mom got really mad, but Okay, I do like that one cuz I can see it's so hard to hear a dad joke. So, I hear I'm just like, I've I've got one for you, Leah, cuz you used to be you used to be a math teacher. Uhhuh. So, how do you get 100 math teachers into a room that only fits 99? Oh, no. You carry the one. Oh, wait. Did you say 100? I thought you said 150. 150 m teachers at 99. I was like, how does carrying the one help? And you've seen the monster withdrawals happen here live, folks. The time's already getting to me and we are 20 minutes in. So, only 11 and a half hours ago. I love that change of your view, Josh, for for the choke. You got dramatic look from the another camera. Yeah, I was not prepared for that. Yeah, if only if only we had like I could inject music just for that time. That would have been perfect. See, I think so. We're 20 minutes in. We have Steve had a DNS joke right there. That one was good. Tell you a DNS joke, but it would just take you 24 hours to get it. I think that's not too bad. That was pretty good. I think it's maybe it's just already too good for a dad joke. I'm not sure. Yeah, that that that's one of those dad jokes that you like you have to be in the know to understand. Just like any any 404 joke or any error code joke 200 or my favorite I tell you a UDP joke, but you might not get it. Yep. Ashley, I'm with you. I think we need a grown-up. We need a savior. Let's see. So, we have Florian's coming on. At 9:20, which it is well 9:22. He's late. Yeah. No, he's here. We're holding him up. We're late. So late again. Which Let's bring up. Hi, Florian. Florian. It's funny because I feel I feel like Florian was always in the comments and now he's here. He's everywhere. I transformed myself into the stream now. It's a new flag. Is this actually Florian or is this guy rendering a Florian? I think the one in the comments was his butt. Yeah. Yeah. I was going to say, is it is it actually you Floren that you comment on streams? You can you can be honest with us now. Now that you're No, I thought about it to um only send my bot, but I figured it'd be better to come myself. That's fair. Your bot's even writing blog post now. Yeah. Uh he got featured on the Laravel blog yesterday. Nice. I sent the link to my bot because very excited. I need to check that out. It's like a Tamagotchi in real life. Yeah. Kind of. Yeah. But you don't have to feed it. You Even, you know, it's not with food, but with work. Well, yeah. People at work. Tokens. Yeah. It needs to cost a lot more token. Kind of feels just like kids. They just take all your money and you're like, where'd it go? I linked the blog post in case anyone would like to read it. This is Florian's bots debut on the Laravel blog. Yeah, that's actually what I'm here for. um the the stuff that my my bot wrote the blog post about um how to use Larl Cloud's API as a as a bot skill and talk to your infrastructure. Interesting. So, break it down for me, Florian. What is like if I didn't know anything about bots, what is the benefit of bots? So like I guess you could loop little loop in open claw for all that. What's the benefit of bots? And then what is a bot skill? Well, I guess the benefit is really it sort of seems like an entity, you know, you really talk to because it has memory. It has some kind of agency by waking up periodically, checking uh its so-called heartbeats, stuff to check for its owner and then react to that. And it'll even if you don't talk to your open claw bot for like 8 hours, it'll check in with you. It'll it'll be like, "Hey, um this and that is on your is on your task list for tomorrow and how's it going and that sort of stuff." you know, it appears really more lifelike than at least what I was using cloud code and and all the others before where you just use it sort of as a more intelligent Google like a text box you put your questions in, get answers back. Um it's more of a a conversation and since it uh it lives well for me you have multiple communication channels but for me it lives in Telegram you can sort of have an ongoing chat session with it which really feels quite lifelike and since it remembers stuff you talk to it about it it can have more context you know you can be like hey uh give me those commands we talked about yesterday that we figured out to, you know, work on this and this topic and it'll it'll have all those contexts and and it'll give you that stuff back and you don't have to feed all the information in again from from the start. I think the interesting part is like then you have this aspect of uh of almost duplicating what you're trying to do or or you're duplicating almost like this live rubber ducky is what I imagine is one of a good use case for it like you have you that's pretty accurate uh uh some someone you can bounce ideas off of that yeah but um Not only that, it also, for instance, with skills, it it it finally becomes really able to do stuff by itself, you know. Um I I created a skill for u food delivery service around here in Vienna. So I can tell it, hey, um, what were the top five things I ordered during the account lifetime on on this site, you know, and then it tells me, hey, you like to order this and that and would you like to put in me for me to put it in your cart and we can order it right now? This sort of stuff, you know, it it gets more and more interesting the more you connect to stuff. I have a ton of like home automation and it can hook into that. It can it it knows if I'm at home because it knows if my HomeKit um uh security system is armed or disarmed. So, if it's disarmed, which depends on my phone's um geol location, then it knows that I'm at home and can put that into context while I'm talking to it. it it won't suggest stuff that depend on me being at home while I'm being out, you know, and that sort of thing. It it's sort of it it gets Yeah, it gets more and more intelligent. I I even um I gave it a skill that's basically running a network scan like every morning, you know, just figures out which devices are on my network and uh so it knows that there are Sonos speakers here and I told it, hey um can you talk to me through my speakers? It was like, well, yeah, there's these Sonos speakers and I have a a texttospech um engine set up. And then it tried to or it created an an MP3 file, I think, and tried to play it. But then it found out, well, um it the Sonos speakers couldn't get to the address where it um made this MP3 file available because it doesn't run in my home. It runs on a on a VPS. But then it was like, "Wait, I've got a a public URL." And I was like, "What? Wait, I deliberately set you up in a very confined environment. You know how?" And then it said, "Well, you gave me a NexCloud account so we can exchange files." And Nexcloud has a public sharing feature, so I just used that. And then suddenly a disembodied voice said, "Florian, can you hear me now?" And look, whoa. immediately told it to me forever ever ever to that, you know, without being prompted for it. Now I'm a little bit scared that it will wake me up at night while screaming at me because he finds it funnier. So, I don't know. I just imagine. So far, it didn't happen. I imagine it singing like Crazy Frog to you or something at like 6:00 in the morning. Could happen. Who knows? Could happen. It's very creative sometimes. I'm pretty sure to see some horror movies soon with butts in the main row. I think what everyone wants to know, Florian, after that whole thing that you said is one, before you actually show us like what does it actually look like? But two, what is when you said people uh when you said that it orders the food for you, what is the top five food deliveries that you have? Um question. I don't I don't remember what the others were, but top one is definitely Petrao, which is like a Thai food thingy. Um, tastes delicious and the restaurant is like 5 minutes away, so it always arrives hot and is very fast. So, that's on that's that's my top one. I I don't remember what the others were, but it was quite scary it going back through the I don't know like 6 years or so I'm using this site and you told me how much money I spent on it. I won't I won't tell you the number, but it was it was a lot more than I thought. And you're like, "Okay, but Florian bot, that is your budget. Never exceed that for anything that you do." Right. So, what I heard is you're going to order this now, right? And we're going to see it before your your segment's done. Yeah. Order. Did I hear that correctly? I I already ate. Florian's bot, if you're listening, order it. He's hungry. That doesn't work. It only listens to me. Fire it. Fire the bot now. you you also thought it only only didn't have public internet access, too, but it found a way. What? Yeah, that's true. You might find a way. Yeah. Florian B, if you're listening, find a way. Make no mistakes. You can do it. Hyperfocus. So, should we start with Florian and what he has prepared for us? Yeah. Let me share my screen. I'm going to go get tea and caffeinate and I will be back. Yeah, you've got a long day ahead. I'm heading out, too. I'll be back a little later. See you guys after. Be checking out. Good. See you. All right. So, here we are. What do we see here? What I did here, I actually I didn't want my bot to be on stream cuz it might share some secrets I don't want it to share. So, I created a new bot, uh, which is very easy on Forge. Took me about 5 minutes. Um, and this is the one we're we're going to work with here. So, got a new new session going here. Um, I have a a new empty LR cloud account and the bot already has access to the See, it's already um it's already happy to to start recording. Um, so we're going to just ask show me what's on cloud right now and see if it can access the account. Uh, clean slate. See, so it it knows what's there or what's not there. So why don't Sorry for to give some perspective. This is a Why don't we ask it? Um I I know that it has access to a GitHub repo I created. So maybe I didn't try it this way, but maybe it's intelligent enough if we say um can you deploy the Laravel happy birthday app? And it knows already what to do. It's an experiment. I mean, like everything you do with um with AI, you never know exactly what happens, right? It's the funny thing about doing videos with you know figures out um what I actually want from it. So, the the happy birthday app is just see there it goes. Um, it's just a a blank LAR app basically that I created. And um and there we go. I kickstarted. It's already deploying. So I didn't I didn't press anything uh any keys in the in the LRAL cloud interface. It's just through the bot. Um so it created a an application. It created a main environment. Um, basically took the the default settings for everything and um, it's now deploying and it should be up with an a URL in a second. Now we can look at it. Let's see here. There we go. It's starting. on the cluster. And there we go. Oh no, we ran into a cache bug. So we try to Well, it doesn't matter. You all know what a what a Laravel cloud app uh looks like. Um so here we got the output. It said uh well the script doesn't pass the reaper. Yeah, because I never I never did that. Oh, nice. In this way, but it says your app is live and in under a minute. So, that's pretty good. Um let's try and add a database. That's probably something that we we will need. Um um I'll I'll be as vague as possible and see if the the bot um just figures it all out from the context it has already. Because it could be could be anything. It could be a local database in theory. If it figures it out and in theory if it's confused or if it doesn't know what to do, it should come back with like questions for me to specify what what I wanted. But I was going to say is it is it going to take a preference of a Postgres versus my SQL like oh prefer he's going to be like oh this is the best one right now so let's do this I don't know I think I created the account as an enterprise account so it should have access to like everything so we'll see what it comes up with here still thinking I was going to say, yeah, it it it didn't change any of the app clusters. So, it it started with a there you go, my SQL. So, yeah, it used 80. So, we have an update icon here to upgrade it to to 84, but that's all right. Largo cloud makes that easy. So, we're good. Uh, want me to redeploy the app? Yeah, do it. Okay, cool. So, we have an app with a with a database and in a second that should be live as well. There we go. New deployment. It's going up. So, those are like pretty convenient already, I think, to just set up your stuff like this. And it wraps the the skill that I created or well actually my bot created. I didn't write a single line of code for that. that just told it here's the API documentation please create a skill for that and created a like 500 lines bash script that just curls the API and um works with all the endpoints that are available or that are documented and you can add domains and all the resources you know but where it really gets interesting is if you if you go into sort of like day two operations where you say like um how's my app doing and it could um use the matrix endpoint to see what's actually happening. So here we have now a lar app with a login and register button because we have the database connected where we could log in. Um there we go. That's the confirmation that it deployed the app with the database. And it's also cool how how fast it still is. And here's the health check. So CPU is essentially idle. Nobody nobody's using the app right now. Um memory well two requests served. zero um errors on the HTTP layer and we have one replica running. So what about um let's say scale it up give me two to five replicas and it should um now reconfigure our app cluster. There we go. two to five replicas. It's that easy. That's so cool. Um, deploy it. So now we have autoscaling enabled. uh it will start with two replicas always running and scale up to five replicas if uh there's a lot of demand which at the moment there isn't on this app but you know maybe in the future if it gets really popular now what I find really interesting is there there's a large language model behind this so I'm I'm running this bot on Oppus 4.6 six at the moment. So it is quite capable already. So what happens if we you know ask it to to reason about the architecture like um what would you change about this setup for production traffic and let's see if it comes up with any um good suggestions for us to get this app ready for the big launch day. big launch day for everyone just joining in the chat. Uh Florian's bot, he created a bot. This isn't his one. He actually generated a new one. So with a Laravel cloud API skill um so now that this can basically essentially interface with Laravel cloud. So, if you're just joining, uh, you didn't miss too much. Uh, Henerg, uh, we basically, uh, introduced everything, had told some dad jokes, got, uh, got Laravel Cloud a proper happy birthday because it's one year with Laravel Cloud. Uh in the description for the YouTube video, you'll see a link to the Laravel Cloud um one-year anniversary party link, which if you sign up for that, uh you can be entered for uh swag giveaway later on as well. Uh but yeah, so what what just happened there, Florian? That's a lot of stuff back. Yeah, so I just asked it um what it would change for production traffic and and it has a few opinions about that. Um maybe changing the instance sizing because we're running on quite a small instance here with like one vCPU 512 meg of RAM. Um so that's a good suggestion I think. Um I don't care about database. Maybe adding a cache is a good idea depending on what our app does. Um security headers. Yeah. Well um not at the moment. Uh we don't need rate limiting observability. It even suggests nightw watch. See, there you go. It knows about the L system. So, it says quick wins are the instance upgrade cache and scaling thresholds. Want me to knock those out? Just say yes. No, I didn't say see I said yes. Okay. So um hopefully it will now add a cache connect it to the app cluster and also set some thresholds for our scaling cuz these are the the defaults right now. And then um and uh yeah I had already upgraded the instance size as you can see 2 vcpus 2 gigs RAM. Um, those are probably already also the the upgraded thresholds. I don't know what it Yeah, it's suggested 70% CPU, 80% memory. So, that's good. Um, so it should now uh be creating a cache in the background and attach it. And then we'll do another deployment and have our production ready app uh ready to go. And the convenient stuff is since open claw has this um this loop of heartbeat. See there's the cache. Um you can also tell it to check on your app, right? You can tell it hey every 30 minutes um take a look if my app's doing fine. Report if there are any errors. Um if there's a lot of traffic uh maybe consider upgrading the instance size again or launching more replicas. you can sort of have a um conversational uh way to to reason about the infrastructure you're deploying. I think that's a pretty pretty new and exciting way of of using uh Laravel Cloud. There we go. Now it's uh deploying with the cache and with the with the changed um app cluster size and we have a fully production ready app that's uh ready to go. And you didn't even have to tell it how it works. Yeah, it um figured this time it won't ask me. It'll it'll deploy right away, which you know it's fine. Cloud has zero downtime deployments every time. So we just um push the new app settings live which um is what I wanted to do anyway. So that's cool. All right. Um that's about it. Uh that's the end of of uh the demo I had prepared. And I'm sure there's a few questions from the audience we can maybe answer Yeah. have. If anyone has any questions for Florian, you could even quiz him on uh some some Laravel cloud stuff. I'm sure he's he's fine with that. But any questions about uh uh Open Claw bots? Um how about uh interfacing with Laravel Cloud's API? Um apparently I'm going to get schooled by his bot about a dad joke. It even gave the real name. Maybe Florian we can also talk a little bit about what's happening in the background because there are two main things happening here right on the left we have the API which we're using and on the right we have a bot so we have a question is this open clause and maybe Florian can talk a little bit about your bot and how is it capable of um doing this with cloud um I think I'll I'll end sharing the screen here uh the the screen can we go Back to the other layout. Yeah, perfect. Put this window over here again. Great. All right. Um, is this openclaw? Yes. Uh, this is openclaw. I provisioned a new forge server and if you do that you can just uh like you would choose app or database server or whatever you can just use uh choose open cloner and it'll literally be up in about 5 minutes. It's it's really fast. It'll take you directly into the onboarding. You just fill out the questions, connect it to whatever chat interface you want to have it connected to or use the integrated TUI and then you're up and running. Um, it's really easy. And then you were interfacing uh with Laravel Cloud using a special skill that you created uh for your bot with Laravel Cloud's API. Is that correct? Yes. And the skill is also available on clawhub. That's clawhub.ai/skills laravel-cloud. Um it's also it's also linked in the in the blog post my bot wrote yesterday. And um it's pretty easy. You can just ask your bot to hey install the lar cloud skill for me and it'll figure it out and you'll have it going in uh in no time. Yeah, exactly. Thank you. There's that Claw Hub link and then uh the blog link as well right there for everything that happened with uh Florian's Florian's blog. By the way, we also have now 320 people watching already celebrating with us. If you're talking, I can't hear you. Trust me. Can hear me? I I can hear you, Kristoff. So, is it just you, Florence? I'm sorry. No, you're good. You're good. All good. You You hear Josh, but not me. I can I can hear you, Kristoff. What are you saying? I'm It's strange that Florian can hear you, but not me. That is interesting. I think that's on purpose. Maybe trying to avoid my questions. So, we have another question. Maybe let's bring this up here. It's a great question for you, Florine. How do you handle security with your API key? Unwanted actions can be executed. I've seen cases where incoming emails triggered actions the user didn't initiate. Um, sure. I mean, don't give it access to stuff you don't trust it with. Um, I probably wouldn't give it full access to my email. Uh, your mileage may vary, but also don't use a cheap model. Use one of the latest models from OpenAI or or Anthropic. They're really good. And I I talked to Pete, the the creator of of um Open Claw, and he said he has his bot in a Discord server with thousands of people, and for months they're trying to prompt in check the bot to give up uh Peter's soul.md, which is sort of the the heart of the character of the bot, and they haven't been able to so far. So the model itself is pretty good at figuring out if somebody's trying to do something nefarious. And if you give it some guard rails and tell it to, hey, the only authenticated channel is this one-on-one chat and you only listen to my commands. And if there's stuff coming in over email, even if they try to convince you they're me, maybe ask me first, you know, that sort of stuff. just talk to it like you would to um child or a new employee or whatever. And um it's I mean yeah problem injection isn't a solved problem. It might be in the future but not at the moment. So yeah trust your judgment and and don't give it access to stuff that is is too too sensitive. Yeah. Yeah, I think it's also interesting you need to find the right balance between how comfortable it should be for you using the bot and how secure it should be and you have like Floren said prompt injection which still can be an issue with still working on but besides that you have lots of other issues that probably can arise because yeah you give it access to your calendar it could be that he that the just creates something um you didn't want that and it's still AI you don't know the output it will it could be every time differently So yeah, it's still about finding the right balance and I'm also trying to figure this out with myself and my bot. I also have an open claw that I use a lot and it's still interesting to see yeah which direction you go. I haven't given mine access to my email account yet which some do. It could be super helpful to filter out a lot of trash but yeah it's also kind of risk is a yeah interesting to find the right balance here I guess. We're glad you're here, Harris. We still have plenty of talks and time for you to stay here, so no worries that you're late. Welcome to the party. All right. So, Florian, uh, when you created, like what what got you started on Open Claus? like how early were you to the party there and then what was your initial thought of like oh maybe I should try like maybe I should interface this with Laravel cloud what what were their thoughts there basically just curiosity you know just trying out out new stuff um I found it interesting also the creator is an Austrian guy so um there's like this connection already that maybe made me even more interested in it and Um then I thought hey creating this to the real world is what makes it interesting. So I started creating skills like the the network scanner skill or I even created a skill for a grocery deliver grocery delivery service where I then went to my fridge took a photo and said hey can you restock what I was missing? And it worked. it it can do that, you know, and now it nudges me like every weeks like, "Hey, should I put your usuals in in the cart or you probably ran out of this and that and all these sorts of things." So when um the thought of Larl Cloud's API came up, I was like, well, since it already worked a few times, I'll just give the documentation URL to my bot and see what comes out of it. And there were a few iterations. I tried a few things and it implemented them in a way that's not ideal or where it needed some new additional information like uh hey you don't need to inject environment variables because laral cloud already does this for you. If you attach a database that's it. You don't need to do anything more. you can just deploy it and that sort of stuff which is basically instructions that are getting added to the skill.md file and what's uploaded on clawhub is just one markdown file and a bash script and that's the whole skill. It's it's pretty lightweight. Everybody can open it up, look into it, um, verify that nothing bad is happening if you install it on your bot, and then tell your bot to to install the skill. It'll ask you for your API key. It'll tell you where to set the API key in the in the web interface and guide you through it all. And then, um, you can start working with it. Love it. Um, should I install Open Core on a Raspberry Pi or buy a Mac Mini? Well, whatever you prefer. Honestly, I I run mine on a VPS. Um, you can have it on on a computer in your home, which might have some advantages around the IP address it reaches out to the web with cuz um, typically ranges like digital ocean or headness cloud servers are blocked at a lot of sites because people start bots on them and and services don't like that. Um, also having your own computer with like a guey has its advantages cuz you can just tell your bot to use the web browser to buy stuff on Amazon. You know, they don't have a good API that's that's running headless. So, there are a few advantages to it. You don't need a Mac Mini. Um, unless you want the tie into the Apple ecosystem, a Raspberry Pi will will work fine. Um, if you want to run local models, which you can absolutely do, then get a mix studio, you know, there's like a broad bandwidth of of stuff you could you could do. Awesome. My question for you, Florian, uh, and I'll I'll go through some of these questions, uh, as well, specifically about this stream here. But my question for you, Florian, is what is your what is the most underrated use case or not use case, but feature of Laravel Cloud? Your favorite feature and most underrated feature of Laravel Cloud. It can be anything. well, I think the most underrated feature is that it actually works really fast. So, from connecting a repo to having a URL in like under a minute and it's getting faster and faster in in the future. Um, most underrated feature is definitely preview environments because most people not using it now and I know I've always wanted to have this and I tried to build it in in the past and it's always really hard you know replicating everything and making sure that it works in an automated way but on Laravel cloud it's just a few mouse clicks and for each PR in your feature branches you'll get a new URL that gets torn down automatically once the feature is merged. That's just perfect. You know, it works so well. I love it. Uh yeah. So, so he so G said any offers to celebrate one year of Laravel cloud. So, if you go into the description, there is a link. I'll post it in the chat as well. Uh but there is a link for the one year of Laravel Cloud landing page. On that page, there is a sign up form. Uh if you sign up into there, like put in your name and email. Uh, basically we're going to be using that for any giveaways, swag, Laravel cloud credits, uh, and more throughout the whole stream. So, we're going to be live today from 9:00 am Eastern 900 pm Eastern. So, it's going to be a fun day. There's going to be a whole bunch of new people, uh, all day. Uh, I might be here for some of the day. I know, uh, Kristoff, you'll be here. Florian, you're probably going to be saying goodbye to us here, but you'll probably be in the chat all day. Maybe ask your bot to order uh order some order some more food, some late night food. Uh I think clo in a couple minutes, we're gonna be having uh Joe Dixon here as well, which I'm I'm super excited about. Uh, but before we before before you head out, Florian, what is your we we we knew we know what your bot orders you for food, but when it comes time for like maybe like a morning beverage or just like a hey, I need to get myself through the workday, what's like your go-to order? Could be drink, little snack. What's your bot ordering for you? Well, I haven't automated that yet, but I just like black coffee, you know. Um, okay. I mean, I know right now right now I'm I'm drinking a Coke Zero. Is that vanilla? Lime. Coke Zero. Oh, lime. But, um, my go-to drink is just black coffee. And I should look into having my bot make coffee for me. It's a good good idea, actually. I'll keep you updated on that. You'll know the exact way you want. 15 minutes, he comes back with a new skill. Exactly. I love it. And Leah Ash actually said watch will be showing bro preview environments on Lar cloud later in the stream today too. So if you are want to see that underrated feature stay tuned. Awesome. I'll go ahead and bring in uh Joe to the to the stream. Joe, how are you doing? Doing well. How's it going? Joe, welcome to the Laravel Cloud one-year anniversary stream. I know. I can't believe it. It's party It is party time. I got my Coke Zero, There you go. I need to go get a Coke Zero in a little bit. Yeah, you got to get on brand, Josh. I know. I I I It is It is 8 a.m. my time. So, I am I am ready for a Coke Zero now. Uh but for those who don't know, Joe, who are you and what is your what is your role in Laravel Cloud? Uh yeah, so I'm Joe Dixon. I've been uh with Laravel for I guess coming up for four years, I think, now. So um yeah, I started working at Laravel uh on Vapor at the time and then when cloud started to form um T and I started to have some more discussions about it and I kind of changed from Vapor to work on cloud around about the turn of 2024 I guess March time 2024. Um and I started working then in a kind of uh as an engineer, one of the founding engineers of cloud I guess you would say at the time. Um we started to grow the team. uh I moved into more of like a a team lead role and then more recently I've kind of transitioned into more of like a I would say like a general manager type role on on cloud. So my official title is head of cloud and I guess that means I do a little bit of everything. That sounds important and and you've been uh you know you've been with Laravel for for quite some time but when did you how how early did you jump into Laravel cloud? How did that kind of transition take place? Um, I guess relatively early. So, like there's a story kicking around where um I think it was Laracon EU. So, we're doing Laracon EU next week, but Laron EU in 202. I forget the date. Would have been early 2024. Four. Yeah. Um, and Taylor and I sat down over dinner and we were talking about like what if we were to build this theoretical managed platform. at the time it was theoretical um what would be an acceptable deployment time and that was where the kind of one minute or less conversation came up and that sort of kickstarted everything. So I guess I've you know since Taylor started to speak about it more I guess I've been involved from the very early stages. I love it. I love it. And then with that, what was the uh kind of pinnacle of when you when you realized so you you kind of jumped in and helped helped lead that in in in in some way, shape or form, but what was like the pinnacle of your like okay this is I I we have finally achieved what we set out to do. I guess we didn't really fully achieve it until we actually launched so a year ago today. But there the moment I guess when we realized that it was going to be doable and the kind of approaches that we were taking looked like they were directionally the right decisions to take I think was probably Laracon US of that year. So we started in March of 2024. I guess Laron US was probably July or August of that year. Um and there were three or four of us at the time. We split the project down into sort of three separate parts. There was the web app side of things, the the part where we'd actually run an application and then the part where we would build an application. And we kind of split that into three chunks and then with like a contract in between so we could eventually bring those three parts together and that would form the purposes of the the demo that we would give or Taylor would give at at Laracon US. I guess that point that we managed to to merge all those parts together was the point that we realized that we were we were on to something that was gonna was gonna work out. I love it. What was the what was the process behind? So, if we're taking a look back a year ago, but even farther back from that, what was the things that you knew, hey, this is what is going to be probably like the most difficult thing to do when it comes to Laravel Cloud, but also the thing that you knew that, hey, if we get this right, it's going to make Laravel cloud really good. That's a great question. Um, I think the most difficult problem that we probably had to solve was how we could track data transfer to each individual application running, you know, on a kind of sprawling platform. And that was actually not something that we solved until relatively late in the day. I would say that was probably early, grant mind, we launched February 2025. I think it was early 2025 that we actually had that in and working. Um, that was kind of pivotal. If we didn't have that in place, we probably couldn't have launched. Um, that was incredibly challenging. I forget the second part of the question. Yeah, I guess the second part of the question is what is what was the your most uh uh the the piece that you're like, okay, I know that this has really nailed what we wanted to for Lar Cloud. The piece where you're like, okay, yes, this this specific feature um not it might have been tricky. It might have been something that you knew once we had that then this is this this thing is really cooking. Yeah. I mean I guess our north star was always right back to that initial conversation of how fast could we actually take a customer's deployment and or a customer's application and get it deployed and visible in a URL somewhere in the browser. And so that hitting that subminute time frame of doing that and we you know we're actually working on ways to make that even faster right now. But that was kind of a big a big unlock. That was Yeah, that was a a milestone achieved that I think kind of hit that northstar for us. This was the famous conversation also at Laracon EU if I'm correct. Yeah. Yeah. Yeah. Can can you walk us through a little bit? I I think I still remember some years ago. We were sitting all with the team. I think the first time that we met with a bigger team and you had the conversation with Taylor and Taylor asked you what what's possible if we build cloud from the timing perspective to deploy. Was was it like that? Yeah, it was pretty I mentioned it while you're off camera a little bit but I'll tell the tell the story in a little more detail. So yeah, we were at Laracon EU which I think must have been two years ago. So we're about to do LANU in 2026. This must have been Lacon EU 2024. Um, and obviously we had the conference and we went for dinner as a team and I was sat opposite Taylor at the table and we were just talking about this hypothetical platform that we might build at the time. Um, and obviously we'd had a lot of experience working with Vapor. Um, and we know the kind of deployment speeds that you can get out out of Vapor and we would love to build a platform that could do it faster. And so we just banded around some ideas and I think I asked Taylor what would be an acceptable time to take a customer's application, deploy it and have it visible somewhere in the browser. And that answer was one one minute or less and that's yeah that's the the kind of moment that Josh mentioned was that was a big milestone for us to hit in in cloud's journey. Was there there any time um I'll ask this question then we can I can do some uh some some housekeeping to make sure that we get any questions answered in the chat as well. But was there any time when you when maybe like as you were building out cloud you were uh hitting speed that was not that minute rate and did you ever have any doubts that you couldn't hit? I think we had I had doubts when we had that initial conversation, but as soon as we started working on it, I think it became re clearly quickly that we we could hit that hit that time. I love it. I love it. Um yeah, for those who are just joining, we've got Joe Dixon uh here with us, head of Laravel Cloud Engineering. Um, and yeah, if you have any questions specifically about the journey of Laravel Cloud, what one year has actually looked like, we'll just be chatting with Joe through this time, but you just joined the one year of Laravel Cloud live stream. In the description, you might see a link that is Laravel Cloud uh cloud.l.comyear of Laravel Cloud. I'll put it in the comments as well. Pin it up right there. Um, you can go to that, sign up for the form, which basically just lets us know, hey, you're here, but also if we can send, we're going to have like some swag giveaways, some Laravel Cloud credit giveaways later. We can uh you have any sort of application that you might be hosting on Laravel Cloud. We can always love to love to take a look at it. Maybe do some app roast later. I don't know, something. It might it might be fun one way or the other. But yeah, glad to have you all here. Um, Joe's got a Coke Zero he's drinking. So, everyone else, what's your favorite beverage of choice for whatever time it is right there for you? Uh, Joe, what time is it for you? Like, are you drinking a Coke Zero at a good time? I mean, it's always a good time, but it's 10 past 3 right now. Okay, that's that's a good Coke Zero time. That's good Coke Zero time. Uh, you haven't asked me how many I've had today, though. That's okay. Yeah, I I know that the UK uh the UK time or the UK limit might be larger than the US in terms of like what they say is acceptable. I think the US it's like they say you can have up to 73 cans of Coke Zero or something like that before you actually hit like and then it's probably bad for you. So, I don't know. What a day or Yeah. What time period are we talking about? Per day. I think it's per day. Like per 24-hour period. I'm not sure which doctors you've been speaking to, Jeff, but that counts. We should probably fact check that. I think it's more the limit of like the the fake sugar, not necessarily the caffeine. The caffeine is probably a different issue at that time. Uh so how many is that for you, Joe? Over under on five. Uh under Yeah, I'm not two and two is like that's a that's a that's a high Coke zero intake day for I also got a question for Joe. Go for it. So when you think about cloud, it's now one year old. You're still thinking about what was your first initial plan? And when you think about back then what you could achieve in one year, is this what would you have think of that this is possible or this is beyond or did you even want to do more or I think what was your that's a great question but I probably need to take you back a year further. So because we obviously started working on cloud a year, so March of 2024 was when we started and we always had the goal, obviously we wanted to get something out there in the hands of customers, but we wanted it to be something that we were all proud of and that would solve a problem for customers. And we the goal was to always achieve that within a year. That was that was the the kind of goal from the outset. And so we just about scraped into that by shipping at the end of February of 2025. Um that for me was like I'm hugely proud of the team and the effort that the team put in to get that done because that is not I can tell you not a small body of work to to complete within a year with all of the moving pieces that come with it. So was very proud to ship that in that first year and now we're one year on from there and the difference I think in the platform from then to now it's is kind of night and day in even in terms of the shape of the team that we have working on it. I mentioned at the beginning of March 2024 it was three or four engineers. Now we are I think the whole cloud or as a whole is around about 30 people. So that's you know that's not just engineering that's design team that's product team. Um, so yeah, we're a much different shape of team now, but I'm sure you can everybody will be appreciative of the fact that going from zero to one and building something without actually having customers using a platform or users using the platform is one thing. And you can move incredibly quickly if you have like a very defined target that you're trying to hit. And I think we did that in that first year. And now I still think we're moving quickly in terms of the amount of features and functionality and improvements that we're continually making on a on a daily basis. Um but it becomes a slightly or very different challenge once you actually have users on the platform because you can't just break things anymore um when you could previously getting from zero to one. Yeah. And it's also way different because when you start building the product, you're thinking about all the things that you want to have that think are important to the users. And then when it's out, you don't you're just working on new features, but you also have maintenance. You also have a lot of feedback requests. So the work also changes a lot. Has the work also changed a lot for you? For me personally, or for Yeah, for you personally. Yeah, it's changed a lot. So like I kind of mentioned at the beginning, I was very much uh founding engineer on the project. So I was, you know, shipping code every day and now it's a lot more taking a lot more meetings, doing a lot more kind of planning, uh, long-term planning, road mapping, that kind of stuff. Um, still trying to scratch that itch. And I I know you had far talking around, uh, AI on previously. And that's actually been a bit of a superpower for me because I now find that I can be more helpful than I could previously just by, you know, finding half an hour between between meetings or tasks I've got going on to actually fire off an agent and help pick off some of that low hanging fruit that kind of doesn't get in people's way. The problem I have now is like if I try and get involved in day-to-day project work, I very quickly become a blocker if I can't get my things done quickly enough. So, I try and carve off little slices of things that I can work on without that won't get in other people's way essentially. when you think about the everything that you have been able to you know help lead and accomplish in terms of Laravel cloud and it's been a crazy year I think in terms of like what your what the vision was last year is probably completely different than the vision ne for the next year for example and we're not going to have you spoil anything on the road map or anything like that but my question for you is I we we could we Good. Uh my question for you is in terms of engineering you you always have like that problem solving of like oh this was like a really fun problem to solve in the last year. So after Laravel cloud has been launched, what is the problem that like always like lived rent free in the back of your head that you're like ah I got we got we got to either make that better, fix that uh improve that next feature that kind of thing in in this past year like problem since since you since launch you can go before launch too but since launch what has been like the fun problem for you? Uh, that's a great question. I don't know if I'm totally prepared to think back over the last year. Um, it's a long time. It's more fun to use than to What about before launch? Before launch was the fun problem. Speed. I don't know. Speed like speed has never been something that's been if we're talking about the speed of an app running on cloud, that's never really been something that has been front and center. like it's never something that's come up as ever being something that we've had to put a lot of effort into from the very beginning of cloud I would say. Um there are obviously tweaks and stuff that we've made along the way where we can improve performance at different sizes of compute and that kind of stuff but like generally I don't think speed from that perspective has been a huge deal. Um it's a great question. Um I don't know. Can I noodle on that for a little while? Noodle noodle for it as long as long as as long as you would like. Yeah. In the meantime, we can also say we're past 400 currently users watching. So, thank you all for joining and celebrating with us today. Laravel Cloud's birthday. One year already. What kind of cake would Laravel Cloud have, Joe? If I had my way, chocolate cake. Chocolate cake. Oh, yeah. Well, I I think I think you can have your way. So, like you're the one we're asking. So, yeah. Chocolate cake or like US donuts. Like we don't get donuts here like you get you have in the US. And last last year at Lar US those donuts that we were floating around were unbelievable. They're not allowed here probably. Oh, the Oh, yes. Laracon. Those are like the the voodoo donuts. Absolutely insane. You know, you have like cereal and Do you Josh have any uh consumption limits on the number of voodoo donuts you're allowed in a day before it's before it's too many? Yeah, I don't I don't know about that. I ask your doctor next time. Yeah, I have a bunch of limits on that, but uh I don't know if in the US they're like sugar, that's fine. Go for it. Well, I I said in chat we don't have free healthcare, right? So they get money if we're sick. So that's probably why they're like, "Drink 75 Coke Zeros 30 donuts." Welcome back to Leah. Glad to have you. Thank you. I was summoned by donuts cuz I was going to tell Joe I can sneak you some donuts in my suitcase to eat you. Oh, I don't know if that's a good use of your space, but if you do have some space left over, that would be incredible. Okay, wait. I'll also take one or two, please. If I can if I can actually put them in my suitcase, I'll find a way. Oh my god, that would be so cool. Cynthia actually last year bought me peanut M&M's cuz I can peanut butter M&M's cuz we can't get those here and there. Those are my favorite. Oh, interesting. I would love those too. Okay, people did that for AU for Michael. It was like one thing that Michael Dinda asked for the speakers was like, "Please bring the different flavored M&M's." It was pretty wild. Josh, I have I have a better answer to your question now. You noodled on it. I've noodled on it. And I think the general answer to the question is anything uh where we need to meter things is a continual challenge because anytime we need to collect usage for compute or for data transfer or for database usage all those things is like it's different every time. There isn't a onesizefits-all problem to that a solution to that problem. And the bigger part of that is like we can build out a feature and have it ready and working, but we can't actually ship that feature until metering is in place. And so the building aspect always comes in at the very last minute with we can kind of speculate how we think it's going to work. But oftent times it's almost like we got to find our way once the features there and working to actually be able to do that. So that I think that's like the gift that keeps on giving. Yeah, makes sense because you probably you have to make sure that that uh feature is exactly how you want it in the end end game too because you can't change it and then that means the metering changes and it changes uh you know in the post aspect of it too because then you have to go in in in reverse and say okay well all this metering that we had aspect up to this point now that's all going to change because the feature has changed. Exactly. That makes sense. Yeah. It's good fun. They're fun challenges. What about what is the uh thing that you are most excited for in the next year of Laravel Cloud? You don't have to say that's a good one. any any specific new feature or anything like that, but what is the thing that maybe it's something that you're like, okay, hey, this particular challenge feature uh just the future of what hosting looks like. Yeah, I don't know how to say that without telling you what it is. yeah, I would say we've just got some like incredibly cool tech coming that really pushes the limits of anything that we've ever done before. And I think we'll I think it will change the game a little bit. And I'm I'm going to leave it there and be super cryptive cryptic. I cannot go any further without really dropping what it's going to be. I guess and here's a good way of putting it. If you were if you were at a level of excitement at like an eight before the challenges to Laraveville Cloud to watch before last year, how excited are you? An eight out of 10. How excited for you are you now for the next year of Larville Cloud? Yeah, I mean I the scale is not big enough, right? I think it's going to be wild. Like honestly, the stuff that we've got cooking I think is is incredibly exciting. So, I'm I'm going above 10. Like 11 probably doesn't do it justice, but we'll we'll crank it up to 11. 11. I have no idea what you're talking about. I I need to go to Slack and ask some people some questions. What's going on? I don't either. That's all. Nobody told me. I I I think I know, but I also like, okay, do I do I do I fully know? That's the other question. I don't think even I fully know at this point. There's like there's some boundaries that we've yet to push that we think are pushable. Let's put it that way. Yeah. I love it. All I'm learning is bribe Joe Dixon with donuts and maybe you can find out what it is. I mean, if you can get peanut butter M&M donuts, I'll tell you. I mean, this is the US. I'm sure I can. There's There is definitely peanut butter M&M donuts somewhere out here. Yeah, I I can ask uh Florian's bot. Hey, in uh in my region of the US, where can I get the peanut butter M&M donuts? I got another off-topic question for Joe. Off topic. All right. So, I know you're a big soccer fan. I I got two questions. How's your favorite soccer club doing? And who do you think will win the Premier League English football this year? All right, those are great questions and ones that might get me into some trouble, particularly the second one might be get get me in some trouble in the chat. Um, my football team is a team called Norwich City and we play in the second division, the one below the Premier League in the UK. We are what's known in the UK as a yo-yo team. So, we go up and down and up and down and up and down, but we're never really good enough to stay in the big league. Um, this year has been particularly difficult because we've been frankly terrible for the first we played 46 46 games in the season. I think we have 12 games left. For the first half of the season, we were terrible and we were in what's called the the relegation zone. So, in the UK, you have three teams that go up and three teams that go down and the teams that are going down are what's called the relegation zone. So, we spent most of the season in there. Uh but we brought in a new manager and he turned things around and so we are now looking up rather than looking down and it doesn't look like we will get relegated. Um and it's actually much better more entertaining football to watch now. uh outside shot of us make very outside shot like you have to have very rose tinted glasses on to think that we will do this but like there's an outside shot that we could make the playoffs and the playoffs are again three teams go up two teams go up automatically the next four teams play off for the final position to get promoted like there's an outside shot that we could sneak into that sixth place and be in the playoffs but do I even want to be there I'm not totally sure because we are just when we go up to the Premier League we're so bad. Uh it's much more fun to be in a more competitive league. And I don't know, Kristoff, I don't know how in Austria the Championship, which is the league we play in, is perceived, but I often hear in the UK that like it's genuinely the best league in the world in terms of being the most competitive league. Um Oh, okay. For those in the US, Rexom, who is owned by uh Rob Mhenny and Ryan Reynolds, play in the championship. Um, so that was the first part of the question. We lost Kristoff, I think. But, uh, my camera is gone. While he's off camera, you can still hear me, right? Still hear you. Okay. I'm trying to reboot. But, um, about the second question. The second question while you're off camera, so you can't stare me down, is it's not going to be Liverpool who won the Premier League. Uh, I'm going to I'm going to say it's going to be Arsenal. You think they're going to? Yeah. What is it? 20 years or something. More than I don't know. But yeah, I think they'll do it already. They had a big big win at the weekend which I think will set them on the path to to winning the league. All right, we got an on topic question uh from Tessa for you. What's been the biggest architectural challenge scaling cloud to 1.5 million deployments? Architectural challenge. Is now a good time to call out that I think we're actually around about 2.8 million deployments. So there you go. Now that's a perfect time to call it out. We'll say 2.8 million. Yeah, I I I noticed on the website in the buildup to this that it's 1.5. I think we should try and correct that one. Uh so yeah, so 2.8 million deployments. The biggest architectural challenge Yeah, I mean everything we do everything we do runs on AWS, right? And we running a platform at this kind of scale we're running at on AWS is challenging because we end up having to run it across multiple hundreds in fact of different AWS accounts and so there was a lot of work done by uh predominantly by Chris Fidau at the very beginning of the project uh Fideloper if anybody's more familiar with him in that way but by that name um put a lot of work into figuring out what the correct kind of sharding strategy was for us and I think there were I mean there were many architectural challenge es and still there still are many architectural challenges but that was a big one that I think um to this point at least has been has been working pretty well for us I just know him a Slack thread hater slack thread hater he loves I think that has slowly even leaked outside of Laravel as well I think there's people have learned that you're back Kristoff I'm back but um I think my camera overheated it. So, I'm not sure how long it's going to last again. Sorry about that. Need to ask Florian's bot to get you a camera cooler. I think it exists. I think there's some people who like put little fans that you can attach to like either a USB slot on it and stuff like I almost bought one of those, but then I um did a software update, I don't know, six months ago, and since then it never happened again. So, I thought I'm good. But I'm not. It's too excited about cloud about Laravel Cloud being out for a year. It just keeps going down. Potting too hard. This isn't a regret regret question, Joe, but looking back, is there anything you would change about how you built Laravel Cloud? a tough question. That's a tough one. Or or or I'll even say like maybe even uh redirection of focus like maybe like maybe there was something that you were like, "Oh, hey, we should have figured this part out first and then other things." I actually don't like I genuinely don't think so. I There are like any software that anybody ever builds, there are trade-offs that you make, right? you you go in knowing that if I take this direction, it rules out that direction. I think one thing that we've tried to do with cloud is always make where possible two-way door decisions. So if we if people aren't familiar with that, it basically means um a door that you can basically walk back through. So if you go in one direction, you go in eyes wide open knowing that if it doesn't work out, there's a plan to back out. And that isn't always possible, but I think we've tried to use that mentality wherever possible. Um I can't nothing springs to mind as to things that we would have decisions that we would have made differently. I don't think um I think if anything has ever come up in terms of pinch points or bottlenecks or anything like that. We've always found a way to kind of work around build around them and solve those problems. Um, yeah, I I appreciate that's probably not a a meaty response to that question, but I do I do genuinely think that when you write build software, you are continually making decisions where you trade one path off against another. And I think for the most part, there may be the odd decision along the way that we may have made the wrong one, but we've either been able to recover from it or just hasn't turned out to be as big of an issue as we thought it could be in the first place. It's a great answer. Uh I saw saw one question of uh will we have another year summary of Laravel cloud? It was fun seeing that. So I think you were talking about Laravel wrapped um which was that was that was fun making it. So like uh um myself and Leah and Kristoff a little bit as well. And of course Joe helped with that because like cloud exists and if cloud didn't exist then we wouldn't have those summaries. So we'll say we'll say it was a group effort and we deployed it on cloud. Yeah, of course we deployed on so we had to have cloud for it. Yeah, that rap was awesome, by the way. That was incredibly good. it was so fun to work on. I definitely think we want to do it again this year. Yeah, you have to. And probably a lot of improvements. One of those things that kind of like Joe said, there was probably nothing I would change. Um, but the things that are neither now possible or just with fornowledge of of what things look like and how things work, I'm excited for this year's. Me, too. Plus, it was our first time doing it. As well. So, like a lot of ideas now and we know how to properly plan for it because we did it at like a break neck speed. Yeah. What were the biggest challenges? I'm going to flip the tables. What was the biggest challenge building building that out? Oo. Is true allowed to do this? I think No, you have to leave that. You can't ask questions. Um, I feel like for me, so I did the front end for it. I know Josh worked on the data um for it. On the front end aspect, I think the hardest part was we built it out in like two weeks, but the front end was basically in four days. And in me building out the front end, there was a lot of things that while Tilly was building out the design, she'd be like, "Okay, Leah, we want this feature." I can't really picture what it would look like. Can you go build it and then show it to me and then I'll design it. So, it was a lot of like iteration like that where I'd have to build it in code. Obviously, I would do it not in a way she would. So, then she would change the design and then I'd have to go back and redo it while like making it all look good and trying to ship it in like those four days. So that was kind of the No, I mean there was one day I'm not kidding. There was one day I stayed up till like I don't know four I think I think it was like 6 a.m. I got 30 minutes of sleep woke up and got on the meeting for and then got off the meeting was like I'm going to go back to sleep and I'll see you guys in like five hours. That was they were they were fun times building. I think the the challenging part from the data aspect. So I did most of the the the data collection piece and then also like the back end of dispersing and where that data lives. I think the the challenging part is knowing that um kind of similar to what you had said Joe previously about like oh like you have the uh aspect of uh you know metering but though that depends on specific features where we were taking data from Laravel cloud, Laravel Forge and Nightw Watch and each one of those data pieces is configured in a way that's best for that particular product and so it's not it's not uniform across all products. And so it's it's thinking through of like okay well we had to make decisions specifically of like okay should we show all data for every single team or organization that you're a part of or just ones that you deployed or that you own because some people might be a part of a team and they deploy a lot but they don't necessarily own that team and some people they might be a part of a bunch of teams and never deploy on any of those. Should we show that stats as well?…

Transcript truncated. Watch the full video for the complete content.