 Ben Jackson and he will tell us why we should open Soros R. Hopefully. Can everyone hear me? Yeah, sweet. Yeah, so I'm going to talk a little bit about AMAZY and why we opened up the Lagoon platform and a little bit of the challenges we face and stuff along the way. Go to slides. So a little bit about me. I've been a systems engineer for about six or so years. A little bit of programming and Arduino Raspberry Pi, like tinkering and just hacking in general, and laser cutting and 3D printing stuff. So if you went to our little booth, the little display that's holding the leaflets, I actually cut on my laser cutter. So I'm going to talk a little bit about the benefits of open sourcing your work, the challenges, and then a little bit of a recap of our experience after open sourcing the platform. So we'll start off with a show of hands on who uses open source software. So we'll start with Drupal, Composer, MariaDB, Redis, Nginx or Apache, PHP, and then the Linux in general. Cool. So we'll agree that open source is everywhere today. It could be in your TV at home, or if you've got a Toaster that's connected to the internet, it could even be on that. It could be pretty much anywhere. What about who's a contributor to an open source project? Awesome. And it's really good to see people contributing back to open source. I know most of the time people don't get any praise or any money from doing any of that work, so it's really good to see that you can create value just from contributing back to any open source project, whatever that contribution is, like documentation, whatever. So talk a little bit about Amazio. So we built Lagoon, which is a hosting platform, mainly for Drupal. But you can also run WordPress or Node, pretty much anything that you can containerize. You can run on the platform. We're part of the Amazigroup, which is a larger net of companies. So there's marketing and metrics and that sort of thing. The core team for Amazio has done hosting services for more than eight years, like combined or even longer, probably from all of the skill in the team. We really know how to do high traffic sites and high performance sites and what preparation needs to go into to maintaining them. We're a completely remote team as well. So I'm in Canberra, but we've got Scott in Perth and Blaze and Tom are both in New Zealand and Sean as well. And then we've got people in the US and in Europe that look after the different time zones. So we've got follow the world sort of support. And we can do either hosting in cloud, so in AWS or Azure or something, or also on-premises if you've got your own. Lagoon itself does a lot of things when you want to deploy. So you can deploy from a local environment, build everything locally, and containerize it. And then when it goes into Lagoon itself, it does the same process. It'll build and create the containers exact same way. So what you deploy locally should deploy the exact same way in the cloud. So one of the Michael, our CTO, said, from the beginning in one of the blog posts that they looked at the whole ecosystem of how Drupal sites are hosted. And it troubled us to see that most of the time when you're building open source software, you can see everything. But the hosting layer is usually proprietary and you don't have visibility of it. So you can't see what's happening within that layer. So if there's some security vulnerability or something, you may not know about it because you can't really see that. You can't probe it. So you don't know what's actually happening out of the hood. So yeah, having an open platform means that you can see that sort of thing. So we'll have a look at a conventional hosting stack. You've got the content management system, or in this case, it'll be Drupal. Then we've got the hosting platform where we don't really know what the secret source is. Then you've got PHP, which is open source. EngineX Apache, MariaDB, and the rest of it is all open source. So you can see it. You can modify. You can do whatever you want. When you get to the hosting platform, it's sort of like, eh, what's going on there? But then with Lagoon, we open source the hosting platform. So everything is fully open source. If you want to have a look at how we deploy the images, you can do it. If you want to look at the varnish configuration, for example, you can do that and see all the work that's been put into previous deployments and the configuration that's there. And everything is all there, and there's nothing to hide. So if there was an issue with somewhere along the way and you wanted to figure out what was wrong, you can have a look. So if you wanted to run it yourself, you could just download it, deploy it into OpenShift, and commit back and help push it forward. There's always plenty to look at. It's completely open source. So all the Docker images and how they're built, so all the components that you would use to build your containers locally for your hosting, they're all open source. They're all built and maintained by us as well. All the configurations for the images are all available to download and modify, and you can add to them as well. So you don't need to necessarily build ours. You can build your own. Again, the varnish configuration is fully available. So all of the work that we put into it for building high performance and high traffic sites, the varnish configuration that's been put in from years of experience is available for you to use and run yourself, and even modify and submit back if you've found something that could be better. And all the build and deploy scripts that are used to build and deploy the environments are available. The testing infrastructure, so how we do all the tests in Lagoon and everything is all open source, and the complete documentation is all available for everyone to look at and have a play with. So one mantra that we always try to go by as well is that if there's an open source tool or product that can do something that we want to do, we'll use that rather than trying to reinvent the wheel. In one example is that we use Keycloak for the authentication on our platform, and Keycloak is an open source project that allows you to do single sign-on across the platform. So you can log in to the dashboard and view your projects, and then via that same authentication infrastructure, you can go to the logging and you have access to all the logging for your projects. Because we didn't want the burden of having to reinvent a whole single sign-on solution when somebody's already done that, just so that we could make the product even better. But we've also had discussions like, your code's open now. Isn't that insecure? And the answer is sort of like no, because we sort of apply the principle of many eyes where you've got a whole bunch of people looking at your code, and those people can see if there's a vulnerability or if you're doing something a little bit silly, similar to how Drupal do security. The more people that look at it or have an incentive to look at your code and think about security components, the more secure that code can get, which is exactly how Drupal do security. The other ones are always around by big enterprise customers where they might sign a contract with a vendor and the vendor will say, our software's secure and bug-free. And it's like, well, they can say it's bug-free and secure, but it's software and it can still crash and nobody can see and tell that it's actually secure unless they get in to that closed source. But with Open Source, you've got that many eyes and people that want to use it and are using it, they can go and have a look at it and find vulnerabilities and let you know. And also with Open Source software, there's some places out there like the, I think the Europeans have the FOS, which is a bug bounty program where you can actually earn money for discovering bugs and exploits and then submitting them and helping progress things better. So we'll talk a little bit about some of the good things about being Open Source. One of the best is that everything happens in the open. Everyone can see what you're doing and what you're working on. And a lot of the features that can come through that are dictated by where the project's heading and what custom features are needed. So if a customer needs something specific, like the backup system that's in Lagoon was needed by one of our bigger customers. So we started implementing that backup solution and now it was so successful that we've rolled it out to the rest of the clusters. So all of the customers benefit from that backup solution now. Other ones are if you've got an issue where you've rolled out some code and now suddenly something's happening in the cluster or in one of the platforms two or three times a day, you go, oh, maybe we've broken something there. You can have people submitting issues and saying, I think you've broken something here. You could have them help discover stuff. Then you've also got maybe some documentation's a little bit out of date. They can help and people were more willing to contribute in that sort of way. We also get some customers helping other customers in GitHub. So someone might raise an issue and say, hey, we've got a problem doing X and we need it to do Y and some other customer goes, hey, have you tried doing this instead to get you to Y and then they're like, yeah. And it's like, great, they've helped themselves and we didn't need to do anything. So yeah, there's a lot of benefits from working in the open. We've also got a public roadmap where in GitHub where you can see what we've got earmarked for next releases and that sort of thing. And we've also publishing blog posts where with information on where the project's heading and what's coming. We've also had people saying, it's really cool that you've got Lagoon but it would really nice to run it on like vanilla Kubernetes because currently we only really support OpenShift. So we're currently working on actually being able to deploy or run Lagoon on vanilla Kubernetes. So it's cool that just like any customer or anybody in general can just say, hey, we wanna do something with your project but we need to be able to do X to do Y and then we can talk to them and collaborate and see how we can make that happen if it's possible. And it also leads to more interaction. So there's a lot of tickets always coming through and a lot of chat that's always happening. So we can really communicate with a lot of customers on how we solve problems and help them out. And sometimes it feels like, even though we're remote it feels like we're in the office with those people helping them with their problems directly. I think there's a couple of people in here that I've probably spoken to quite regularly and it definitely feels like we've been in the same room just talking. There's also some challenges having an open source. One of the biggest ones is when we actually open-source Lagoon was that it wasn't called Lagoon. It had, well it was called Lagoon but it had amazing IO all over it. And someone was like, it's cool that you've open-sourced your project but there's a company name all over it. Shouldn't it be an open-source project rather than your company's project? So yeah, we did a finer replace on the entire repository, changing amazing IO to Lagoon ran the test, the tests all passed and merged it and then that was it. So now it's an open-source project called Lagoon. You also have people saying that it's like, they raise issues and it's like, hey, you should do this instead of that. It's like they try and dictate where the project should go. And that can be a little bit difficult to work with sometimes. So we usually try and work around that by saying, hey, that's a great idea. Maybe you should write it down, say how you want to achieve that, how you think it should be done, how it should behave. And then we can try and work together to come up with a way to actually implement that and see if it's something that everybody would want or could benefit from. And then sometimes it could be that it's not even that big of an issue and nothing comes of it. But then if you've got someone that's got real proof of you should be doing it this way because of X, then we'll definitely explore that and collaborate with them. Some other things that not everyone wants to have their name in the open. So some customers will say, we want to raise an issue, but we don't want to have our name in GitHub or we don't want to have our company associated with the issue in GitHub or whatever. So we can do those issues for them and for security stuff as well. They can email us privately and we can work to solve security issues. Or if it's just a general that they don't want their name in the open, then yeah. And the other thing is you need to think about your code a lot more. You can't just implement a small hack and go, yeah, it's a hack. That's great. And then put a comment that says hack to solve X. Submit it, because then you've got everyone looking at it. So you've got to be a little bit more thinking about what you're actually putting out into the open to make sure that somebody else can understand that change or if it will impact anybody else. So yeah, a bit over two years ago, we open sourced lagoon and what did we find? We've found that people actually want to use it. It's exceeding our expectations. You can found customers kept saying everything is open source, everything in our stack can be looked at, everything can be audited and that they can change it to suit their needs. So then they can help make it better and that's really cool. And we're hoping to keep that going and have more people involved. We've got weekly pull requests that are coming in and closing. Carl is referenced in every other talk that I've been to so far. So Carl's done some pull requests and they've been merged in, which has been really good. So yeah, just having people being involved in trying to push the product further is really good. And no contribution is too small. So if you identify an issue or want to flag an issue that you think needs some attention, don't be afraid to do it. No one's going to buy it or have a go at you or anything. Just it's good to start discussions and get things going. So if there's an issue and people need to know about it, don't be afraid to raise them and implementing new ideas or new features and stuff, start a discussion because there might be a bunch of other people that want the same thing. And if you don't say it, it's not going to happen. So yeah, definitely start talking about stuff. And if you find some documentation that's wrong, like submit a PR, a typo, like I think there was a PR for a one letter change one. So it's just like, yeah, straight in. It's like, stuff like that. It just helps everyone at the end of the day and everyone will benefit from contributions. And one thing to ask yourself as well is if anyone else could benefit from any work that you've done if you just open sourced it, if you wrote some code that helped you out of a sticky situation that someone else might find useful which could save them hours or days of pain, maybe you should open source it. Like other people can benefit from it because maybe one day your code could be the shoulders that other people stand on. That's it. Thanks. We can do questions if there's any questions. I wasn't going to, but I guess you can try it. I can. Under shaved bacon. Yep. Well, yeah, so Unix is open source. Yeah, the Mac itself isn't Darwin is not, yeah, but the code that Darwin's built off is. So it's the same like, well, it's the same with like OpenShift and Red Hat. You have enterprise and free versions and they both have, you know, you've got the open source version of Red Hat and that's called CentOS. And it's basically same for same. And they use the same Linux code under the hood. So, hey, I couldn't know. Yeah, so, because I've got OpenStack at home. Any other? Nope. Cool.