 Hello everyone. Welcome. Thanks for coming along. I think we'll kick it off. I think people have stopped coming in So my name is Cameron. I work for Acquire. I'm a solutions architect and today I'm going to be talking about the developer tools that Acquire offers as part of its Managed hosting service Acquire cloud and some of the other tools around that And I am going to act as though I am a CTO or a technical leader at a company who understands technology Encoding and the command line, but maybe isn't quite as familiar with Drupal and with Acquire tools So like hopefully like some of you are I'm also going to pretend to be Acquire support So when you see me with his hat, I'm a different person That'll all come out in due course Okay So setting the scene it's a Thursday night My developers are all away at Drupal con Barcelona, and I've got tickets to go and see secret cinema I'm going to dress up as a X-wing pilot, and I'm going to have a good time. Everything's quiet at work. Nothing's going wrong I'm feeling good We've got a few things coming up next week, but for now everything's fine So I want to get out of here by five today, you know, I want to make sure everything's working Then my boss comes around the corner He says there's something wrong with the site and you need to look at it And there's no way that you're leaving this place until it's fixed And this is how it makes me feel Okay, so I'm going to go and I'm going to look at the site So let me just open up my browser here Sorry guys. I just have to close them PowerPoint here for a second Technical difficulties Now I've got it bookmarked. So let me open it up and see what's happening here Okay, so obviously I don't really want to have a work role Sitting on the top of my site. It seems like one of my developers has left a nice little present for me Before they went away and I'm going to have to figure out how to fix this So what am I going to do? Well, what I did know is that when Acquira brought us on to the platform I attended the onboarding call and They gave me access to the platform So I've got a login I can look at things and what I need to do is get in there Figure out how to edit the code figure out how to test the code and then obviously push the code live So the that route rolls gone from the site so Let's check that out. Shall we? so I go to the Acquira site and I open up my login and this is the page that I see So as an Acquira customer we get production and staging and development environments by default And I can see here that The developers left something for me And what I want to do is check this locally So I don't want to edit it directly on the server because there'd be dragons But what I might want to do is grab a copy of the code work on it in my local environment so another thing that was offered to me as I Was onboarded to Acquira was something called Acquira Dev Desktop And so if I open that up What we see here is a local development environment that integrates Apache and MySQL and PHP But it's also integrated with a lot of the Acquira cloud tools. So it's aware of Acquira cloud in my hosting It's aware of the repositories that sit behind Acquira cloud and I can interact with that directly from here So in this case as I'm logged in and I've got both of my sites hosted in Acquira cloud I Can see that each has a dev stage and production environment So what I want to do is bring the code down to my local machine so that I can work on it So if I look here, I can say with the local workflow. I want to pull from the cloud development environment And if I click here, I can say I'm going to pull down just the code We're not too worried about the database and files from now. I'm fairly confident that it's just an error in the code So if I click this big shiny button here Dev desktop will handle All of the stuff around get to do with my SSH key You know connecting and take where cloud pulling from the right repository and syncing so I've got a local environment And then I'll have a copy of the site running locally. So if I click on this We should see Site booting up and running locally so Now I need to edit that in my development environment. So I open up my IDE And very quickly when I look at this template file, I can see that There's a big issue here This is a an embedded iframe with a youtube in it. That's not what I want. So let me go ahead and delete that and I'll just That looks good. Okay Pop back into the dev desktop and now what I want to do having edited it locally is push it all the way back up Back into the aqua cloud so I can test it so that if it looks good, I can then push it back out to production So in this case, I'm going to use the dev desktop and I'm going to push to the cloud And I've only edited the code So I'm going to push that up Only push the code up not the rest of the components of the drupal site You can also see that This little Set of options here allows us to control some of the aspects of the cloud directly from the dev desktop So I could clear the cache or I could run update php. Whatever that means And that'll all happen as a result of pushing the big shiny button So we'll sync up with aqua cloud and I'll get a little window which Is a look in to get so if I don't want to learn get I just want to work with that within a friendly environment. That's kind of safe and sanitized I can do that completely within dev desktop So I select all the files that I want to commit And if you understand version control, this will be very straightforward, but I'm going to add a message and say removed vandalism Add the message so that means that the next developer that comes along to see Whatever my changes will will have some idea when they look at the log about what I did So I hit commit and this will synchronize my local code right up to development And as I said, dev desktops instructed aqua cloud to clear off the caches so that when I go and check the site to see that It's working We should see everything as new. We're not we're not reading a cache copy of the of the page So Time to test If I jump back into safari Let's have a look here. I'm going to open up my Development environment and so this is not exactly what I was hoping to see What I'm seeing is a white screen of death now. That's not What I hope to see so let's just summarize where we're at so I think locally with aqua dev desktop I edited the code better worked Then I pushed the code up to dev for testing Now that I've tested it I see a white screen of death So what I want to know is how can I actually debug the site, you know, I it's not my local machine How am I going to find and read logs on this crazy big system that I don't know a lot about So having a vague memory of what I was told during the aqua onboarding and having a poke around the documentation I remember that there's something called log streaming which allows me to see The logs in real time On the site on even environments and you know, see if any of the requests that are making are actually kicking off errors Or at least writing logs To the logs on the aqua cloud So let me show you How that works Okay So when I do a little trick here now, here's my white screen of death And I'm going to move that over to the right Here's my aqua workflow And I'm going to move that over to the left Now if I open up the logs It'll open up the UI that you saw in that little gif It's a little bit squash, but I think you get the idea And within that I'll be able to choose between those environments that I showed you in the workflow page before so development staging and production exactly as we discussed And I can also choose Which logs I want to show So I'm going to go ahead and choose all the ones that seem to look like they might give me errors So patch error, php error and Drupal watchdog So if I go back to My white screen of death And I refresh the page Let's hide that You can see that immediately we've got a php error. So just to confirm that I'm going to Refresh that again And yes, so we are seeing a php error So let me just dig a little bit deeper So you can see that We've been able to see the log in real time as I've been viewing the site and we've got a message that's kind of useful So it says cool to undefine function each Which is in My template file And it happens to be online too Okay So I'm going to try and Fix that so Back to my template file On my local machine, of course And you can see that online too Which is here. There's got some php code which I probably should have been more careful with And it doesn't look so good. So let me remove that Save it So I think I've fixed up That particular error Now while it was cool to be able to use git within Dev desktop, I'm pretty comfortable with git on the command line Um, so now that I know that aqua cloud does work with git I'm going to try and do that instead of working with them that little ui and dev desktop. So if I Jump back into my dev desktop environment and I click here I can open up a console So I'll just make that a little bigger Great So straight away, you can see that dev desktop has been giving Us all the environment variables that are required to work with triple On my local machine, and I've also been changed into Directory locally, which has the code that I've been working with So let me just check the status of that code So I can see that the particular template file I've been working on is modified So if I just check what's been modified So yes, that big minus with the red Text is right. That's what I want gone. So let me commit that So I'm going to go git number at that and I'm going to say Minus m Fixed syntax error or some similarly useful message So that's committed That's good And now because git of course is a distributed version control system. I've actually got to push it up So that it's available on aqua cloud and to my other developers. So git push And that is what we want to do. It's been pushed up. You can see that dev desktop has set it all up for us so that I've got a distinct Version control repository that's hosted by aqua and that's what I've been interacting with on the cloud Coolies, okay, so if I jump back into Safari and look at my workflow We should see that that code Has been pushed up and we should be able to see that also in the log So yeah, just as I clicked into there that had finished And that's my little commit that I've made You can see that I fixed the syntax error. That's the message that I've given And if I click into the details, I could see, you know, if anything had gone wrong during that code commit the other thing I could do is Look at notifications of other things that have been going on from other users But unfortunately because everyone's in Barcelona having good time. There's nothing. It's just me So if I look at the dev site, does that look okay now? Yeah, it appears okay. There's no white screen of death. There's no rick Astley. So now I'm feeling pretty good Like I've done it So what have I done? So I managed to view the logs on the Acre environment in real time. That was handy Then I fixed the issue locally, which is a pretty simple fix And instead of committing via the desktop, I actually fixed it from the command line client Which is something that I'm more comfortable with So now I've got the slightly more scary Job of actually deploying it out into production and fixing the issue for good So let's look at how we might do that Okay, back to safari Just have to because of the way the screen set up here. I have to keep closing the power point where that's okay Back to safari. Okay So we're back to our little environment management console Now within that we've we've spoken about dev stage and prod within each of those we've got the code The files and the database now if you know Drupal, you know that those are kind of the three main components that make up a site But because I'm going to do a deployment and because I want to be able to back out of it if something goes wrong I need a point in time backup that I can go back to if there's a major issue So how do I do that? So if I click on this little down arrow here, I have an option I have a few options, but the one that I'm most interested in backing up the databases So I do that Then get a list of all the databases we have deployed on this site And I'm going to back those all up And again, we get another job kicked off in the task list, which will be logged And that I can see who did it and whether anything went wrong during that So once that's done, what I'm going to do is actually deploy the code and currently the code That sitting on master is what I actually want to be in production So how do I do that? So one of the ways that I can do that is by just simply dragging and dropping it from one environment to another So if I just grab the code from here Drop it down on to production At the cloud or say to me, hey, I see that you're doing a deployment Can you please provide a commit message because I want to know what you're deploying and why so that when someone else comes along They've got some idea of why you did it. So I'm going to say removed Vandalism hit deploy And as always this will kick off a job in the cloud and the code will be deployed. You can see that the production has now got a state of deploying And we've got the task running And of course, I've kept the backup so that means that if this does go wrong, which I hope it doesn't I can back out of it. So we'll just wait for that to roll out. We can look at the log Great all done. And so we have some detail there about what's going on. I don't want to get too much into that But obviously you're taking care of business. So Now is the moment of truth. I am going to actually Test it on production. So I'm going to go to my little bookmark here Open up production Looks good No vandalism So happy days So let me just Have a look and bask in what I've done for a minute So I deployed to prod using workflow tools and I have a backup just in case And fundamentally I got the roll gone and the bug is fixed. So I'm feeling pretty good The immediate need that my boss was needling me about is is out of the picture But what I Don't want is to then be interrupted later on because my boss has found something else So I know that aqua's got some monitoring tools. It's beginning to all come back to me. So I'm going to go ahead and use those to check for systems and whether there's any security issues Which might lead to some more vandalism Whether there's any performance issues, which might lead to downtime or a slow site And then we do have a spike coming up next week. So I want to make sure that we're prepared for that So aqua insight. Okay. What is that? Let's have a look So if I close down this show again and jump back into safari again Okay, so I'm back in my my interface And on the top here at the top level menu. I am going to choose insight instead of cloud The site's working. So I don't need to do any work on it immediately But I do want to check the monitoring to see what's happening So what this shows me is a bunch of metrics around and tests around things like performance, security and best practices Now my overall score rule is 45 percent, which is not great And I can see that there's some red alert issues here, which I'm going to have to have a look at Overall performance is not terrible 14 out of 20 issues resolved, but security and best practices aren't looking so good I can also see the uptime of the site over time and you can see there's a couple little blips there where we've Deployed that white screen of death code, but generally it's looking pretty good And it's actually working quite quickly under 500 milliseconds for the most part So my developer left me a few notes about how I might actually deal with security updates And I've also got some notes here Uh the aqueous provided basically to give me an overview of what the actual issue is and and how to go about looking at solving that So let's have a look I need to do this and I've got these notes here that I'm just looking at from my developer So Back to dev desktop Now I know the code's up to date because I've just deployed it And I'm going to open up another console And what I'm going to do is use this tool that my developers recommend to call drush, which is the Drupal show and From my interaction with aqueer. I know that they allow me to control the sites on aqua cloud directly from the show using drush Using some things called aliases and that's the notes I have So first thing I'm going to do is check for security updates with my little notes from my developer. So here we go Drush update. Oops, not the db the code please security only So this means that drush is going to go away and look at drupal.org And check for which security updates are available And sometimes this can take a little bit of time But I'd rather it took some time and got the right security updates then it worked quickly and broke my site, right? But it does have to check every every module to make sure that there's something or not something So while that's running I might just create a new branch to work on So let me open up yet another sorry Open up yet another Console And I am going to Create a new branch. So how do I do that? Good check out minus b for branch security updates And I'm going to put a date on it to be a good citizen 22nd of september 2015 Great I'm just going to check on my updates still running. Okay cool okay, so In the meantime, I am going to push this branch up to our staging environment so that I've got the environment in a state that's ready for me to Test cool. So how do I do that? Now? This is very much good stuff, but we have full and native support for git on a quick cloud. So Let me push up this new branch Okay, so that's been pushed up to a quick cloud My update still running And if I jump back into the cloud I'm going to deploy that tag into product onto the staging So that I've got a place to test that code when it's ready. So Before when I deployed a some code into an environment, I actually dragged it from dev into prod this time around I'm going to specify exactly which particular git branch I want to be deployed. So In this case, I've got this little little icon here if I click that Um Equicloud is going to read my git repository and see all of the bits and pieces that are available. So I'm going to choose this security updates branch I'm going to just check that name Yep Deploy that So that now when I push code onto that branch, it's going to go directly into my staging environment While that's running, I'm also going to grab the latest copy of the files in the database from production So that I know that when I'm testing it, I'm testing against the most recent copy of code Sorry of content from production. So In much the same way I deploy code, I can deploy files And databases from production down to stage Which is going to make that as close as possible to Production, which is obviously a lot safer for testing So hopefully my long running update is finally finished. It has Great. So I can see in this case that I've got one, two, three, four updates available And I can also see that Trush has given me a nice message that a backup is going to be kept. So although I've got a version control Get out of jail free card. I've also got a backup that Trush is keeping for me. So that's handy So I say yes, I want those and Trush is going to go ahead download them Apply them over the top of my existing modules in such a way that they apply cleanly and I'm not having to clean up Errant files that have gone all over the place So once that's done, I'm going to push it up to production and I'll be able to run Some database updates. Cool. So I've applied pretty cleanly The cache has been cleared out. Everything looks good So once again, I'll do my git status. You can see lots of things have been changed Over 500 files. So I'm just going to go and add all of those because I can't be bothered figuring out exactly which ones and I'm sure it's fine All those are in Great git commit minus m My message is going to be added security updates for modules All done and now once I'm happy with that I'm going to push that Right up Great. So that's been pushed to my security updates branch as you can see here And if I jump back into safari and refresh The workflow we should see that they've been pushed out You can see that they're being pushed out right now and that's just completed as we've been watching So that's great But my notes from my developer also say that I need to run database updates because those Code updates might have made changes to the database which need to run. It's a real true policing So I'm going to go and do that now The other thing I know is that I can use drush to interact directly with Aqueer cloud from my command line So I don't need to log into servers and so on. I can just let aqueer's tooling handle that So what do I want to do? So I want to run drush. That's the first thing but the next thing is the special Name that I have which is my Unique name for my environment So this is a unique name which I've got in notes Which is referring to my particular environment on aqueer cloud and it represents an alias file which Contains all the ssh settings and so on to interact with that I could interact with the development environment by putting that or I could do staging by putting that suffix Or I could do prod by putting that But I want to interact with staging so I'm going to do that and I'm going to say please update the database for me So if I do that This is going to connect into aqueer cloud and say oh great. No database updates are required at all So I can be pretty confident that given that I use the most recent database from production And I pulled down Pushed up the most recent code from the security updates that we're in a good shape that it's going to work on on prod as is so What I'm going to do now Is I am just going to do exactly the same thing in production It's going to be very obvious that um for the next person who comes along That I deployed some security updates on the 22nd of september And I can run those those database updates in exactly the same way That I did on staging So what have we done? So we downloaded some security updates We tested in staging And we ran any required database updates that were on the aqueer environment as well as locally and so on And we also got it out to prod so I'm feeling pretty good about that That means that we're pretty up to date And I feel like I might be able to leave on time today, but The other thing that was happening in the In that Insight reports that there were outstanding performance issues, which I don't really I'm not as confident on how to deal with so What I'm going to do Is talk to a queer support They're a big team of Drupally people who know how to work with Drupal a lot better than I do There's a lot of them They're available 24 7 they speak a lot of languages They're spread across four continents and they've got about 250 plus years more experience with Drupal than I have So How do I actually deal with them? How do I get them to help me? Let's give that a shot Once again jump him back into safari This time I'm going to click on the help link Which is going to give me access into the support ticketing system So I want to create a new support ticket So I'm going to click the big orange button And I am going to say that it is a Drupal application support issue As opposed to say a platform issue or another type of issue And I'm going to say the urgency is high So we do have a spike coming up that we know is likely to put a lot a lot of load on the server But it's not critical. My site's not down. Everything's still working, but it is high urgency. So Let me just Write a little summary here So we've got a spike expected this weekend and We have a big spike in traffic expected this weekend and my devs are away Insiders reporting that there are some performance issues and I'm worried That we won't survive Could you help Okay, so this is where as if I'm not wearing enough aqueous stuff already I put on the stylish hat And I suddenly become aqueous support staff All right, so Let's just clear off all this stuff So I'm the aqueous support guy. I have received This ticket And I want to help this guy out. So what do I do? So the first thing that we should know about aqueous support staff is that they have access to customer sites And they have full access to both the code and the actual running application So obviously that's a very sensitive thing to have the ability to do So what we need is some kind of way of centrally managing that and what we do at aqueous have a thing called a bastion server Which means that all of our authentication goes through a group of central servers that are centrally managed So we log into that server with three-factor authentication And then should we need to remove rights from someone or give rights to someone we can do that from one place Instead of having to chase them all across the internet So as aqueous support, I'm going to log into that. I'm going to put in my password I'm going to generate a one-time token And once that's done, I should get a nice message saying I'm logged in And the bastion connection is active. So that means I'm logged into a server somewhere in america Which is managing my authentication So What I could do is aqueous support is I could go into insight and look through the report directly But because we kind of see this stuff a lot of the time and because You know, we we know How to fix a lot of these issues directly without having to kind of reference the detail and insight I can just run it from the local machine So what I'm going to do is run If I just clear that out the aqueous hosting toolkit And if I can remember I think it's dc Barcelona d7 Demo is it? No, let me just get the name there That one dot production And I am going to run a lightweight audit So kick that off and this is going to go through and do what's called static analysis of the site Which means it's going to check a lot of the code and the configuration without actually bootstrapping the application So you can see what we have here Is a very quick and Easy to scan report which shows the things that are looking good on the site And the things that are not looking so good So this is fundamentally the same data. That's an insight. It's just presented in a different way, but What I could do is actually support is I could go back to the client and say hey, these are these particular issues You should go ahead and fix them or we can just fix them ourselves directly So it really depends on the client's preferences But you know, we can dig in and find these very common issues that we see quite easily So we have a lot of tooling that's like this. This is a very simple one to show Sometimes the issues aren't quite as simple You know, this this is stuff that you can very quickly see and very quickly fix Sometimes we need to dig a lot deeper into customer code to figure out what's slowing things down or Limiting scalability so on So one of the things that we offer for a lot of our customers is The option to use xh prof now if you haven't heard of xh prof. It's a application performance monitoring tool that was Actually written by facebook say there's a lot of php And it digs right down into your code and analyzes it at function level So this is not for all Acquire customers. It's only those who want to have it enabled but in this particular case This customer has had enabled so I can click in And I can see a summary of the performance right down to the function level You can see where some of the time is being spent in memcache and php in my sequel And if I wanted to I could dig right down To a very fine grain level and I'm not going to give a Big demo on how to use xh prof because I don't really know how to use it that well myself and it's very complicated but I can dig further and further down into Every single function and see How much time they're taking how much memory they're using and so on And that's very useful if there's something a particular page that seems to be running for a very long time We also actually offer to all of our customers new relic, which is effectively the same thing But it's just a little bit friendlier. And so again customers don't have to have it But they might want to have it and it's just the case of enabling it on the Acquire environment You can see that as an Acquire support staff. I have access to a lot of those particular sites so for example druple.com I can dig in and see exactly the same thing. So it's exactly the same model of being able to dig down to the function level Cool. So that's code analysis The last kind of thing I want to show you that Acquire support do is In their support role is to look more at the Server the underlying servers. So I'm just going to clear that one out And I am now going to Obviously that was a little shortcut I'm going to run a report against The server that is running the production site For the last week so I can set a time frame in this case. I'm just going to do the last week So if I run that We will see a report open up Which will give us very fine grand detail of how each particular server in the stack is running And that is all fed from Nagios data, which is kept centrally in our monitoring tools But this is just put into a way that makes sense For a customer to be able to read as opposed to a long stream of logs So we summarize the hardware in this case is two balances in a single server And as we see we can dig into particular features CPU load Memory use and so on And so all of the things I'm showing you are very detailed and complex But that's part of the service that we like to provide should we need to dig into this level of detail cool Okay So So What had support handled and I'm going to take the head off and go back to being a punter and not a support staff member So what does support do so we ordered the config in the code to make sure that things were performing correctly So we did a light audit Excuse me. We also looked at server stats and we Dough very deep with xh prof Support was also able to notify the cloud operations team who haven't really spoken about but they're the kind of backing and people Who are monitoring all of the servers In our in our cloud and they will know now that there's a spike coming up So should they see a whole lot of traffic suddenly coming out of nowhere? They know it's not a DDoS attack or something like that So it just gives them a little bit of extra context for should they need to spin up additional servers or react And in another way to cope with that spike And that means that I can feel like my mind is at ease There's an upcoming spike. I don't need to particularly worry about it myself. I'm not directly responsible for it I've got support So My boss is happy. He says it's not bad. He's making this face And even though it's Thursday afternoon. He's still asking me about Drupal 8 He's a pain So what do I want to say about aqua and Drupal 8? So first thing is that we're absolutely ready for Drupal 8 everything that you saw here is supported in Drupal 8 Including you know insight the drush instrumentation and so on if I jump back into My developer tools my dev desktop you can see I've actually got two sites here Our d7 site and I've also got a d8 site I can open up The workflow for that by clicking this button Hopefully I haven't been logged out because I'm on a different network No, that's the wrong one. Let me just open the d8 one And you can see exactly as we had with the d7 I've got the d8 and Exactly the same instrumentation But with additional support for some d8 features. So you can install d8 and go go for it Show you that running We have a nice d8 site. I'm all logged in. I've got the nice d8 Interface and I'm happy days. So as a quick example, let me show you what I might do Now as you may or may not know d8 is not quite out yet So what I want to do is install the developer module for Drupal 8 Because that's something I could use to help me to debug my Drupal 8 site, which is still In development and still relying on the or waiting on the release candidate to come out. So I'm going to use drush version 8 this time and I'm going to download the develop module So I can see that that's been Downloaded and I've been told which path and which modules are available I'm going to create a new branch. So I'm going to go check out minus b Deval for d8 or something not the best name, but that will do I'm going to check the status You know, I'm going to add in the new module Well, hello, okay commit minus m added Deval now push that up Probably be told to go away. I have been so I'm going to set the new branch On a queer cloud And again, we pushed out And we're enabled No problem So If I jump back into my workflow In exactly the same way I can Deploy Deval for d8 Hit deploy And out we go So we support drush 8 on the actual cloud environment as well A lot of the stuff I've been doing here is local, but we have full support for that if I was then to For example Enable the module Enable I'll do it in the drip late site to show you actually I think that might be better Open up the site Go to extend and search for develop I'm going to enable develop in this nice little module and that will Be installed within drip late and ready for use And that's all done I then go back I can start mucking around with it and breaking things And there's develop you've used it in drip will see but it's much the same thing But obviously for drip late Great So To conclude what have we done? And I Will take questions just in a second after I've gone through this so Utilized fdesk top we managed to fix an error the Not only was there the the bad vandalism, but we also fixed An error in syntax by reading the logs in real time then deploying that to prod Uh, we used aquia tools to monitor site performance and configuration Then I was able to install the security updates deploy and run the database updates with drush on aquia cloud directly I've also been able to get in touch with that aquia support who helped with the performance and scaling So I have got that handled for me, which means That I can go Away to secret cinema and listen to goldie dropping some metalheads tracks And have a good time and be relaxed And that is it But if you do have any questions I'm happy to take them. We've also got david here from our products team who is involved in Some of the future work that we're doing In the cloud generally but specifically also around drip late. So if you do have any questions feel free to ask So the question was around deploying drip late to aquia cloud and having some issues with that via dev desktop Did you want to If you are having particular troubles like that Feel free to come down to the booth and there'll be people that can help you Okay, sure Yeah, like as I say come down to the booth or post a support ticket and we can help out Yeah Any other questions? No, okay Thank you very much It's quite Yeah, that's quite a it's very kind of Without any special new stuff, it's kind of a difficult demo to give off it. Yeah, absolutely Okay There's a good branches for tags You'll have, you know, for the first insight Which in the master always was one of the employees in one of the iron wells for There's no It should be but there is kind of some conventions So yeah, that's how it's Typically we have master Whatever you release in this release We also have customers that have a whole bunch of different And we have a great bridge So we use them all around the world Yeah, yes, and we will see But if you have more the moment One on one Yeah, yeah, yeah, yeah, yeah I think that one on the time Of course it's just me, you know Working on the site, I work with A sister organization That, you know So it was an idea So yeah But So what comes to make when you Decorate on The question is Without The That's not The tower Which To get So Nice My question is Without using those The desktop itself Is there a method to create A bridge To Look different Absolutely Yeah, it will be both Sorry With the tower With the tower Which I don't know Is it like To Look at that Up Always Right Right Yeah Yes Yes Yeah Well On the The On the Yeah This is why we're here. So if you want to get a point that you can comment on, it's interesting for you and we can help you out. That's a bit of a cruise. So I wouldn't get it to my question. Okay, children. So one of the things we think of as an ephemeral, it's like your opinion can change. So you can have, um, push x's to this stage and you can hit it. But not to the right, for example. So you either want to hit some x's, or push the right this one between me or push the x's. So you can do all sorts of finer grained stuff from there. So we do quite a lot of next things. One, two, three, four. Yeah, Tim, Tom actually just was a bit stunned that we only have one point. You're doing it a few times in the section. Yeah, I don't know where that, I mean, sometimes I never know where the misconceptions come from. The key thing is we stick them all in with reality. So you would know about, I mean, DevTools is being explored, but Dev Desktop is getting more developers, that's great. It's like an entry level drug, though. Yeah. And, you know, Drupal VMs just come out with matching engine x, with one, two, and this red hat is important. So essentially, you can spool up your Docker container on anything you want. And then import your Acquio, Drush, Areses, and have a really great developer experience from there as well. Yeah, I mean, that's the problem with that whole given that this is nothing new for us. Yeah. We've seen some of the shows a lot of screenings, right, but it's what we like. Yeah, you've got the diagram that showed, I wasn't even beginning, but the show diagram just says this is what we're about to go through here at the A-State. No, it wasn't. But he, because we wanted to do it in a particular context. It's the idea. Yeah. So that's sort of, like, sort of, kind of, Yeah. Yeah. I would have wanted to show someone that, and I wouldn't have wanted to show someone that. It's not that much. Because you're right at the level of people you are, when you get connected with. But I think that's a lot, like, every quarter presentation that says, here we are in the process. Okay. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah. Yeah.