DEV Community: Lagoon

Lagoon v2.26: Enhanced User Experience and Platform Reliability

Lauren Morris — Fri, 27 Jun 2025 11:42:15 +0000

This release improves how you interact with Lagoon through better email notifications, easier navigation, and important infrastructure updates that make the platform more reliable and secure.

Better Email Notifications

Lagoon now sends you emails when important stuff happens:

When you're added to an organization or project
When your SSH keys change
When your role permissions change

You can turn these on or off in your user settings. The emails include your organization's branding if configured.

Improved User Experience

Organization links in project views - Easier navigation between org and project pages
Better download tracking - We now log who downloads what files (useful for audits)
Enhanced email preferences - More control over which notifications you receive

Platform Updates

RabbitMQ updated to v4.1.0 - Better message processing and reliability
Keycloak updated to v26.2.5 - Authentication improvements and security updates
Amazon S3 library updated - More reliable file storage and handling

What This Means for You

You'll have better visibility into what's happening with your projects and organizations through improved notifications and navigation. The infrastructure updates provide a more stable foundation for your applications.

Beta Features for Select Customers

This release includes some experimental features for cross-project service sharing that are available to select customers in beta. If you're interested in testing these capabilities, reach out to product.

For technical implementation details, check the full changelog.

Lagoon v2.24: Enhanced Developer Control with Modernized Infrastructure

Lauren Morris — Fri, 14 Mar 2025 12:34:12 +0000

This release of Lagoon strengthens the platform's core infrastructure while delivering powerful new capabilities that give developers and organizations greater control over their environments and workflows.

Platform Modernization

Updated Database Compatibility

API and Keycloak services now support both MariaDB and MySQL 8 databases
MariaDB remains the default internal pod database
Foundation laid for future managed database service integration with Lagoon Core

Core Technology Updates

Keycloak updated to version 26
Golang upgraded to version 1.23
NodeJS upgraded to version 22
These updates improve security posture and ensure compatibility with modern dependencies

Enhanced Developer Control

Improved Environment Variable Management

Enhanced security for environment variables in hosted environments
Added ability to delete variables (previously required unsetting or support intervention)
More intuitive variable management experience across interfaces

Organizational-scoped Environment Variables

Organization admins and owners can now add default environment variables to all projects
Centralized configuration management for multi-project organizations
Accessible and manageable through the UI

Enhanced Cronjob Controls

Set maximum duration for cronjobs to prevent runaway processes
New concurrency limits to prevent identical cronjobs from overlapping
Improved reliability for scheduled operations

Operational Visibility

Extended Audit Logging for Platform Owners

Comprehensive audit logging now natively available in all Lagoon installations
Accessible exclusively to users with platform-owner permissions
Expanded event capturing provides deeper insights into system activities
Logs now stored directly in the database and queryable via GraphQL
No longer requires OpenSearch for access to audit information

Improved Task Management

Task system now offers feature parity with the builds system
Durations displayed in the UI for better tracking
Quality of Service (QoS) implementation in remote controllers automatically distributes tasks
Prevents overloading and resolves concurrency issues across projects

UI Enhancements

Copy functionality added for project and environment name breadcrumbs
Easier integration with CLI or GraphQL tasks
Organization-level variables now manageable directly via the UI
Streamlined navigation and information access

Looking Forward

These improvements support Lagoon's evolution as a developer-focused application delivery platform. By modernizing our infrastructure components while enhancing developer controls, we enable organizations to maintain complete control over their deployment processes while ensuring platform stability and security.

For detailed technical information, view our full changelog.

Lagoon v2.23: Enhanced Enterprise Controls & Platform Stability

Lauren Morris — Tue, 31 Dec 2024 14:40:25 +0000

With this release, we strengthen Lagoon's foundation for enterprise deployments through improved platform management capabilities and enhanced security controls.

Enterprise Control & Security

Streamlined Platform User Management

New platform-wide role management capabilities eliminate need to access Keycloak directly
Enhanced user search functionality supports filtering by email, ID, and role
Introduction of platform-organization-owner role enables granular access control

# Example: List platform owners
query allPlatformUsers {
    allPlatformUsers(role: OWNER) {
        email
        platformRoles
    }
}

Enhanced Authentication

Improved email authentication handling across cases
Modernized client authentication implementation
Public/private key handling refinements

Platform Stability

Infrastructure Updates

RabbitMQ upgrade to 3.13
Enhanced build failure visibility across interfaces
Improved database transaction handling

Developer Experience

Streamlined local development configuration
Enhanced testing framework
Expanded documentation coverage

Looking Forward

These foundational improvements support Lagoon's evolution as an enterprise-grade platform. By strengthening our core infrastructure and security controls, we enable organizations to maintain complete control over their deployment processes while ensuring platform stability.

For detailed technical information, view our full changelog.

Keeping Your Lagoon Dependencies Up-to-Date: A Developer's Guide

Lauren Morris — Tue, 29 Oct 2024 13:15:02 +0000

As developers, we understand how challenging managing dependencies in development can be. As Lagoon users ourselves we want to help you stay current with package updates ensuring you have access to security, performance, and new features.

How to Check for Application Updates

The simplest way to check for available application updates is using your package manage commands

Composer: composer outdated

Yarn: yarn outdated

Python Pip: pip list --outdated

Ruby Bundler: bundle outdated

(Notice the theme here! Your package manager of choice probably also includes this functionality too!)

This command will show you if you're running an older version and what updates are available.

Automating Your Update Workflow

Although you can check updates manually, automated tools deliver the biggest productivity benefits. We recommend implementing an automated dependency manager to handle this for you. Some popular options that our team has tried and tested include:

Renovate Bot- Free Community Plan
Dependabot- Integrated with GitHub
Violinist- Free Version available, only supports PHP/Composer

These tools can:

Automatically detect new package versions
Create pull requests for updates
Integrate with existing CI tooling
Include changelog information in the PR
Maintain your desired update schedule

Understanding Lagoon Updates

Uselagoon Images

We wrote a blog post a couple of years ago about this - check it out at https://dev.to/uselagoon/moving-lagoon-to-semantic-versioned-docker-images-57d0. We recommend pinning to specific image tags if your project is under constant development and you’re using automated update tools. If your project has infrequent development, using the :latest\ tags is usually a better option to avoid inadvertently exposing yourself to vulnerabilities.

Drupal Modules

Our Drupal modules, such as Lagoon Logs are packaged through the Drupal.org package system, and updates will be notified through the UI or via composer show\

Drupal Integrations

Our Drupal integrations package, like other components, follows semantic versioning practices. Each release is documented on GitHub with detailed changelog information and published to packagist, making it easy to understand what's changed and whether you need to update (hint, you likely always need to update!).

Lagoon Tools

The tools we manage to help with Local Development are also updated regularly:

Lagoon CLI - available on Homebrew for Mac&Linux, as a binary and as a Docker Image
Lagoon Sync - currently only available as a binary, but we’re working on the others
Pygmy Stack - available on Homebrew for Mac&Linux and buildable from source

We usually recommend running the most recent versions of these tools - and are always on the lookout for any bug reports or improvements.

Lagoon examples

From time to time, we introduce new thinking into our example repos - either to take advantage of newly-available functionality in Lagoon, or to reflect a change or update in best practices. You should keep an eye out for these changes from time-to-time, and look to see what you can incorporate into your projects. Note that there is no automated way to do this, so it’s back to side-by-side eyeballing!

Best Practices

Pin your dependencies to specific versions for predictability
Set up automated testing to run when dependency updates are proposed
Configure your chosen update tool to group related updates
Review changelog entries before merging updates

Getting Started

To begin automating your dependency management:

Choose an update manager that fits your workflow
Configure it to watch your Lagoon-related packages
Set up appropriate test automation
Define update schedules that work for your team

Remember, while automation helps, it's still important to review updates before applying them to production environments. The goal is to make the process more efficient while maintaining control over your application's stability.

Staying current with updates helps ensure your applications remain secure, performant, and feature-rich. We encourage you to explore these tools and find the workflow that works best for your team. Your success as a Lagoon user matters to us, and we know that managing dependencies is just one part of your development journey.

If you come across any awesome tools, please let us know!

Lagoon v2.21 released

Toby Bellwood — Tue, 17 Sep 2024 05:28:24 +0000

We are excited to announce the release of Lagoon v2.21.

What’s New in v2.21?

This release includes a series of new features and enhancements to improve user flexibility and security.

Deprecating Unsupported and Unmaintained Images

Unsupported or unmaintained images may have unresolved vulnerabilities, creating security risks for customers. Deprecation ensures users migrate to more secure, maintained versions.

There are now warnings in the Lagoon UI and Docker Desktop. We will continue to post the warning and while at this time we do not intend to remove out-of-date images, we could potentially block builds in the future.

Lagoon users take heed: we cannot guarantee compatibility with potentially broken builds forever. It is in your best interest to keep your code up to date, and action any build warnings that Lagoon detects.

Warnings can be viewed in Docker Desktop, via a docker inspect command or in future releases of Lagoon, highlighted in a build.
If the image has a suggested replacement, it will be mentioned in the warning.

Example:

To learn more please read further here in the Lagoon documentation.

Multiple Volume Mounts

By supporting multiple volume mounts per pod, a single pod can access multiple persistent storage locations, which is essential for enabling more applications, frameworks, and languages to run on Lagoon. This feature boosts Lagoon’s ability to run diverse and complex setups within a single pod architecture.

Path Based Routing

Path-based routing within an environment means that an ingress can direct traffic to different services based on the request’s URL path. This enhancement, which allows routing multiple paths to different services within the same ingress or namespace ultimately improves flexibility, scalability, and simplicity in how traffic is managed across multiple services in an environment.

Base Image Refresh

For projects that use custom upstream images, there is now additional functionality that forces Lagoon to check for a new image automatically on every build, just by adding the lagoon.base.image: label to any image in the docker-compose.yml file and setting the value to the upstream image you want to check.

Upgrade to Keycloak 24

This upgrade ensures better security, performance, and usability for managing identities and access. It will also give Lagoon greater support for authentication methods, and you can expect to hear more from us on this in the coming months.

Conclusion

Our latest release is a commitment to enhancing and improving Lagoon and the user experience. These updates are designed to help our customers manage their environments more effectively and securely.

Additionally, we are working with users to understand the importance of maintaining your code base and fixing errors. Together, we're building a more robust, efficient, and user-friendly platform that empowers your development process.

Upcoming Lagoon CLI release v0.30.0 - there's a lot of changes!

Toby Bellwood — Thu, 15 Aug 2024 20:55:47 +0000

Lagoon CLI v0.30.0: Breaking Changes and New Features

We are excited to announce the upcoming release of Lagoon CLI v0.30.0 next week. This is a significant release that introduces several breaking changes, as well as some powerful new features. We want to give our users advance notice of what to expect, so you can prepare your tooling and workflows for a smooth transition.

Pinning CLI Versions for Stability

As Lagoon CLI has not yet reached a stable v1.0.0 release, occasional breaking changes are necessary to improve the tool. With v0.30.0 introducing multiple breaking changes, it has the potential to disrupt scripts and automation using the CLI.

We strongly recommend pinning a specific version of the CLI in your tooling. This allows you to control when you update and adapt to any breaking changes. If you want to test the latest lagoon-cli version locally before updating, you can always build it from the source: https://www.github.com/uselagoon/lagoon-cli.

Overview of Changes

The release notes will provide a full list of changes in v0.30.0, and the docs will be updated when released.

Here are some key areas to be aware of in advance - we've tried to cover most of the main items that have changed:

Configuration Updates

amazee.io customers using Lagoon CLI should update some configuration values to use the latest DNS/hostnames:

graphql: https://api.amazeeio.cloud/graphql
hostname: token.amazeeio.cloud
port: "22"

SSH Host Key Verification

SSH connections will now attempt verification of the host keys of the ssh endpoints, you may see messages like this in your output (it is logged to stderr)

Warning: Permanently added 'ssh.us2.amazee.io:22' to the list of known hosts

You may also have an old host key saved in your known hosts file, if you encounter an error that contains the following

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!

You’ll have to remove the old host key from your known hosts file manually (http://ssh-known_hosts-ignore-temporarily)

Flags Standardization

All command flags have been changed from camelCase to kebab-case for consistency. The short code/aliases have stayed the same

--autoIdle is now --auto-idle
--gitUrl is now --git-url
--productionEnvironment is now --production-environment
and more...

Flags related to OpenShift have been generalized:

--openshift options now use --deploytarget instead.

Binary 0|1 flags for enabling/disabling features now use true|false: - --autoIdle 0 becomes --auto-idle=false

--deploymentsDisabled 1 becomes --deployments-disabled=true
and more...

Streamlined Output

Some commands (get environment, get project and list deploytargets) have had their output tables streamlined. In these cases, a new --wide flag will display additional fields in the output.

Command Structure Changes

The structure of some commands has changed, particularly around organization-related functionality. Refer to the documentation for an overview of the new command syntax.

Described below are some of the changes to be aware of if you're using organizations,

lagoon add organization organization becomes lagoon add organization
lagoon add organization project becomes --organization-name flag on lagoon add project > Don't forget to add this flag if you work with organizations
lagoon add organization group becomes --organization-name flag on lagoon add group > Don't forget to add this flag if you work with organizations
lagoon add organization deploytarget becomes lagoon add organization-deploytarget
lagoon add organization user becomes lagoon add organization-administrator
lagoon delete organization organization becomes lagoon delete organization
lagoon delete organization project becomes lagoon delete organization-project
lagoon delete organization deploytarget becomes lagoon delete organization-deploytarget
lagoon delete organization user becomes lagoon delete organization-administrator
lagoon list organization organizations becomes lagoon list organizations
lagoon list organization projects becomes lagoon list organization-projects
lagoon list organization groups becomes lagoon list organization-groups
lagoon list organization deploytargets becomes lagoon list organization-deploytargets
lagoon list organization users becomes lagoon list organization-administrators

Log Streaming Support

Lagoon CLI v0.30.0 introduces support for retrieving and streaming container logs. It allows for truncating and following logs for services and containers, similar to SSH commands.

This feature requires support from the remote cluster and will be progressively rolled out to amazee.io clusters in the coming weeks and months.

Embrace the Change, Get in Touch

We're thrilled to bring you this powerful new version of Lagoon CLI. While the breaking changes may require some adjustment, we believe the improvements in consistency, capability, and performance are well worth it.

If you have any questions or need assistance with this transition, don't hesitate to reach out to us - either in the Lagoon support channels or via your existing support arrangements. We're here to ensure your Lagoon experience remains smooth and productive.

Get ready to take your workflow to the next level with Lagoon CLI v0.30.0!

Lagoon 2.20 Released!

Alanna Burke — Tue, 30 Jul 2024 23:48:41 +0000

Find out more on the amazee.io blog:
https://www.amazee.io/blog/post/lagoon-v220-release

And read the release notes here:
https://docs.lagoon.sh/releases/2.20.0/

Sail:onLagoon!

Alanna Burke — Thu, 20 Jun 2024 18:53:40 +0000

Laravel users, we’re so excited to announce the launch of Sail:onLagoon!

If you’re familiar with Sail, you know it’s a quick and easy way to spin up a Laravel site. And now it’s fully integrated with Lagoon, allowing you to spin up a Laravel site configured for Lagoon quickly and easily.

Check out our demo video to see how quick and seamless Sail:onLagoon is:

And read more in the documentation here: https://github.com/uselagoon/sailonlagoon

This is also just the beginning of Lagoon’s relationship with Laravel! Historically we have given a lot of focus to Drupal, and now we are working to grow our support and expertise in the Laravel space. We’re reaching out to you because we want to become a part of the Laravel ecosystem. We want Laravel users to help us drive our efforts, so we’d appreciate it if you could take a few minutes to fill out our Laravel user survey: https://forms.gle/96cQHNQL6gKF3gZ78

You can also check out our Laravel example: https://github.com/lagoon-examples/laravel-example-simple

Questions? Want to learn more? Join us on the Lagoon Discord: https://discord.gg/te5hHe95JE

LagoonCon Portland 2024 Recap

Alanna Burke — Wed, 15 May 2024 20:11:57 +0000

LagoonCon 2024 was held on May 6, in the Hyatt Regency across from the convention center. With registrations flying in through late Monday afternoon, we were pumped for a great event!

We were off to a great start with people so eager to attend that they showed up almost an hour early. The attendees mingled, enjoying drinks and appetizers while the room buzzed.

At 7 PM, Toby Bellwood, Lagoon Product Owner, warmed up the crowd, and gave an introduction to Lagoon and amazee.io. He introduced himself and gave the order of the evening.

Lagoon Recap, Roadmap, and Positioning

Toby gave an overview of what Lagoon does and why it’s great for both devs and ops. Then we got a recap of what Lagoon has done in the past 12 months. Here are some highlights:

Focus on security, with more permissions for platform admins, less reliance on legacy tokens.
Keycloak updated to v17, and then v21 - required major refactoring
Implemented Organizations
Brought a lot of self-service functionality
Build image overhaul, better logs, customization, start of the Go migration
Lots of component, dependency and version updates
Changes in the internal image build, test and deployment systems
Individual environment services - gives us a good building platform for “Insights”
Documentation reorganization and documenting upgrades and deprecations better

Some other notable achievements this past year:

DDEV Support for Lagoon! Check out the webinar from February: https://www.amazee.io/local-development-with-ddev-and-lagoon

Legacy (Ruby) Pygmy finally deprecated! pygmystack/pygmy all the way now!

So what’s coming next for Lagoon?

Lagoon Retention periods - using Lagoon to define how long to keep backups, stale images etc - represents not only a cost saving, but a security improvement.
Lagoon Resource requests - allowing a Lagoon administrator to set specific scale/redundancy parameters for projects.
Lagoon Labeling standards - providing stable, reliable Kubernetes labels to allow Ops teams to build functionality on top of Lagoon - metrics, logging etc.
UI v2 - work on the next iteration of the Lagoon UI.

Keep an eye on the Lagoon blog, socials, and Discord to be the first to know when new features are released!

Highly Technical Content Meets Private LLM: Insights and Lessons Learned

Our next talk was from Christoph Weber, Solutions Architect and Sr. Product Extension Manager at Pronovix with Justin Winter, Business Intelligence Engineer at amazee.io. Pronovix builds developer portals, and hosts them on amazee.io.

This project was Inspired by Michael Schmid’s demo at LagoonCon 2023.

The introduction of a private LLM solution and demo of a simple implementation sparked the idea to prove the solution on very complex, highly technical content that is sourced from the real world.

The idea was a private LLM chatbot fed with highly complex technical developer documentation for their client’s developer portal. Ansys, their client, has extensive documentation that is very complex but gives very little context. Privacy was also very important, making amazee.io a great choice for the project.

For the proof of concept, the scope was limited to one client library package, a DPF C++ Client Library. They were working with raw HTML produced with Doxygen, migrated into Drupal. It was ugly, but it worked! Getting the right data was crucial to getting good results. As with everything in computing, garbage in, garbage out.

Justin joined in to discuss some of the implementation hurdles. He talked about the multi-step process of splitting Markdown into chunks, and then processing each chunk with a custom prompt to extract questions/answers, themes, and keywords that then get converted into a vector database. These chunks of text can then be searched when a user asks a question by finding stored text that has a similar semantic meaning, as defined by the embeddings of both the question and text chunks. This is known as Retrieval Augmented Generation (RAG), and can dramatically improve the results of LLM output.

He then demonstrated how this data is used to build a chat interface.

Justin asked a basic question that queries the documentation directly and receives a response. He then asks a more detailed question that requires the AI to understand the data. Finally, the chat generates a code example for implementing the library we’re discussing.

He explained that If you can feed the LLM the context it needs to answer questions, that’s where the real magic is. He also recommended that we think of Chat GPT not as a chat bot but as a search vector. The answers it gives are only as good as the data it has.

This project was done using Llama 3 and Grok LLM.

If you’re interested in the AI space, stay tuned for future offerings from Lagoon and amazee.io!

Why an Open Source Hosting Platform Makes Sense for the Open Website Alliance

Next up was Bryan Gruneberg, CEO, CTO, and Co-founder at Workshop Orange, and Consulting Solution Architect at amazee.io.

He gave a compelling and passionate talk about the Open Web Alliance, its goals, and how an open source hosting platform like Lagoon aligns perfectly with the goals of the alliance.

Bryan introduced himself and Workshop Orange and set forth the goals of his talk: that open source projects deserve to have open source hosting (and that Lagoon is a great choice).

What is the Open Website Alliance?

The Alliance has been founded to facilitate collaboration between Open Source Content Management System Projects (specifically Drupal, WordPress, TYPO3, and Joomla) to drive education and advocacy around open source benefits and principles. Essentially, it’s a community of communities.

The open web is more than a technology - it is a cause

The open web is built on freedom. Anyone can learn, build, and advance. It is defined by decentralization - no single person or entity controls the open web. It thrives on inclusion. Anyone can have a home on the open web, regardless of their background, identity, ability, wealth, or status. The open web requires participation - it is a shared resource and a shared responsibility, sustained by deliberate choice and collaborative effort. It exists for empowerment. The open web is fueled by the desire for information, connection, and progress, and strengthened by individual rights to choice, privacy, and security.

Bryan walked through the points of the Open Web Manifesto and how Lagoon stacks up.

Must be designed to protect - not exploit - personal data and public discourse.
- With Lagoon being fully open source, you can run your own platform or hire a company to run your own platform, controlling data and discourse as you see fit, instead of having to pick a hosting company whose values might not align with yours.
Must enable the next generation of innovators & entrepreneurs to compete.
- Scalability and Flexibility are key. Many hosting providers only allow for a couple types of applications on their platform. If you can put it in a container, Lagoon can deploy it, and scale for any level of traffic.
It must be resilient to a changing world and not controlled by a select few.
- There are only ~4 major Drupal hosting platform-as-a-service offerings. When it comes to WordPress, almost 1% of all websites are hosted on Automattic. That’s not a lot of variety. As a fully open source platform, organizations are empowered and even encouraged to run their own platform-as-a-service with Lagoon.

Bryan wrapped up with an excellent question to think about:

If you buy into these values, embracing a fully open source hosting platform is a logical conclusion.
If your CMS is open source, your tooling is open source, and your contributions are open source…
Shouldn’t your hosting platform be too?

Lagoon Updates and a Hybrid Roundtable

To wrap up the evening, the Lagoon team joined from far and wide to introduce themselves, what they’re working on, and gave a few demos of exciting features being developed for Lagoon.

Matt Swann: UX and UI Updates

Introducing Lagoon UI v2! Matt gave us a sneak peak into the upcoming update to the Lagoon UI. Focused on simplicity and functionality, there are many new user-friendly features. Users will find quick access to common tasks, and overviews will give more information at a glance.

The UI is managed via Storybook, and a Figma design library is available for the community, which we’re excited about. We have fostered a culture of testing and evaluating the UI, creating a roadmap of continuous improvement. If you’re interested in being a UI tester, let us know! Reach out via email at ux@amazee.io or matt.swann@amazee.io.

UIv2: Problems Tab

UIv2: Deployments Tab

UIv2: Environment Overview

Davit Darsavelidze: Lagoon UI development improvements

Davit has been working behind the scenes on making UI development easier. Here are the highlights:

UI Component Library

A full set of React components, combined with NextJS to make atomic development of future UI functionality more straightforward.

Cypress Testing for the UI

Introducing a full Cypress test suite into the UI, and configuring both GitHub actions and local development environments to ensure all development retains functionality, improving iteration speed.

Full Storybook support for the UI, connected to Figma

Similar to Cypress, a development enhancement to allow faster design to code process, and improved testing/QA/iteration cycles.

Blaize Kaye: Lagoon Ecosystem/Insights Updates

Blaize has been focusing on our Insights suite, which allows users to see a variety of information about their project in the Lagoon UI. Here’s what he’s been working on:

Lagoon's Insights feature categorizes valuable data into "Facts" and "Problems," aiding portfolio management.
Automatically gathered during scans, Insights are processed within Lagoon, facilitating efficient issue identification.
Custom Insights enrich the system by reporting portfolio-specific information, simplified by recent enhancements.
New mechanisms, like in-cluster service endpoints, streamline interaction with the Insights API.
Posting data to Insights APIs is straightforward, allowing seamless integration with various tools.

Blaize has also developed a Lagoon-Remote service for Insights, making it simple to add an Insight.

Alanna Burke: Lagoon Community Updates

Alanna gave a quick update on the Lagoon community. A major highlight has been the Lagoon Discord, which is growing and thriving - make sure to join if you haven’t yet: https://discord.gg/te5hHe95JE

We are still trying to figure out what works best for the community when it comes to community hours, so please fill out the community survey and help us help you! https://tinyurl.com/lagoonsurvey

Alanna also highlighted some of the documentation changes in the past year. We’ve done some reorganization to make it easier to find the content you need. We’ve documented the new Organizations features, added a section on how to Lagoonize your site, added a list of client libraries, and all releases are now listed in the docs. Check them out: https://docs.lagoon.sh/

Our community updates wrapped up with a plea for contribution - we’d love to have everyone contribute, whether it’s directly to the Lagoon project, a supporting project, documentation, or to our biggest need: examples! Lagoon can support just about anything, but we need folks to help us out by setting up and Lagoonizing sites in various applications, frameworks, and languages, so that we can add them to our list of examples. If you’re interested in contributing in any way, check out our contribution docs and say hello in the Discord!

Ben Jackson: Build deploy tool iteration, DBaaS Controller redesign, Lagoon Machinery

Ben works on so much of Lagoon, it was hard for him to pick just a few things to talk about! He gave some updates on the work that goes on behind the scenes to make Lagoon tick.

The build deploy tool was initially built in BASH, and is now being rewritten in a component-styled architecture that allows for implementing individual bits in stages.

Build logs are now more easily parseable, and have added smarts for warnings, errors etc.

A future development to keep an eye out for is more composable builds - quicker and more efficient builds will only build selected services, hot-reloading where applicable, allowing for variable-only updates.

The DBaaS controller was a much-needed overhaul, built in partnership with the amazee.io platform team. The DBaaS controller provides Lagoon environments with their databases, but it had a number of limitations - it’s non-updatable once deployed, database targets are hard to auto-select, and it can’t be adapted for other scenarios.

Finally, Ben talked about how he and Chris have been working to refactor Lagoon Services and the Lagoon CLI in Go, using best practices and ensuring that modules are reusable. They’ve taken this rewrite as an opportunity to ensure that everything is done the right way, resulting in clean, concise code.

Brandon Williams: Lagoon and Community

Brandon talked about “eating our own dogfood” - performance tuning for Lagoon core on amazee.io infrastructure resulted in updates to the mariadb images so that everyone can benefit.

Brandon has also been providing a lot of community support in our Discord, and spoke about how we are seeing how community members are benefiting from our years of support and Lagoon knowledge, as well as helping one another - which is exactly what we want to see in our community support channels!

As Toby mentioned, Brandon has been working with DDEV to get native support for Lagoon. DDEV is now a great option for anyone using Lagoon. Read more in the DDEV docs if you’re interested: https://ddev.readthedocs.io/en/stable/users/providers/lagoon/.

Chris Goodwin: Internal-services-test, Lagoon CLI & UI

We needed something to test the wide array of services that Lagoon supports, but what was the best way to do it? A gigantic mega-project with every possible option? No one wants to maintain that. So the team figured surely we could find a way to do this in Go.

Enter internal-services-test, an application that tests itself. It uses Go modules for the individual services, and depending on the path the router users, triggers an action on a specified endpoint - storing and retrieving data. This application is then used in Lagoon-core testing, Lagoon image testing, and sample projects, and it couldn’t be simpler.

Testing Redis

Testing Storage

Testing Mongo

Testing Solr

Chris has also been working on the Lagoon CLI, refactoring the codebase, adding support for Organizations, and aligning the CLI better with the API. He’s also done some work on the Lagoon UI, adding CRUD functionality for project and environment variables, and allowing for new environments to be created in the UI.

Adding an Environment in the Lagoon UI

Managing Organizations in the Lagoon CLI

Managing Environment and Project Variables in the Lagoon UI

As you can see, the Lagoon team has been busy! It was a great way to wrap up the talks at LagoonCon.

Wrapping Up

After the talks, we had some time for networking, and a lot of attendees were really excited and already brainstorming new projects with Lagoon.

This comment from Jeffrey McGuire (Known as jam in the Drupal Community) really summed up the night:

I’ve been in open source since 2005, and I've never seen a presentation like this, and you’re walking the walk that you’re already talking. I’ve never seen a company/project say “we do this well and this well but we’ve got this problem and we’re working on this” and this whole - it’s so open, and it proves that what [Bryan] said, is really true, and it’s possible, so thank you.

Thanks so much to everyone who attended - we hope you had a great time, and we hope to see you both in the Lagoon Discord and at the next LagoonCon!

Lagoon at DrupalCon Portland 2024

Alanna Burke — Thu, 02 May 2024 00:03:57 +0000

Heading to DrupalCon Portland next week? Make sure you say hello! Here’s where you can find us!

LagoonCon will be on Monday, May 6 at 6:30 PM at the Hyatt Regency - make sure to register, it’s free! We’ll have great talks from Lagoon Product Owner Toby Bellwood, Christoph Weber, Solutions Architect at Pronovix, and Bryan Gruneberg, CEO and CTO of Workshop Orange, followed by a roundtable with the entire Lagoon team!

During the week you can find us at the amazee.io booth, where we’ll have some great swag if you like plants or pets - or stickers - so come by and say hello! If you’re using Lagoon or interested in learning more, we’d love to meet you.

Lagoon Community Manager Alanna Burke will be sharing our love for pets with her PetOps Lightning Talk, “Keeping Your Pets Safe with Technology,” on Tuesday, May 7, 2024 at 2:45 PM in Hall C.

She’ll also be hosting a BoF on “Ethics in Web Hosting,” on Monday, May 6 at 2:30 PM in G129 at Table 1. Join in for this important conversation!

We’re looking forward to a great week of open-source fun in Portland, and we hope to see you there!

Announcing LagoonCon Portland 2024!

Alanna Burke — Fri, 12 Apr 2024 23:16:21 +0000

If you're heading to DrupalCon or in the area, don't miss LagoonCon 2024!

We invite you to join us at LagoonCon and learn more about:

What Lagoon is
Why it’s changing developers’ lives
The benefits of open source application delivery
How to upgrade your hosting and application delivery strategy
How to contribute to the Lagoon project

Who should attend?

Anyone who wants a better delivery experience from start to finish. From CTOs, developers, site builders, project managers, and product owners – especially if you’re working with decoupled and composable architecture. If you want to learn more about the benefits of a delivery platform like Lagoon, we’d love to have you!

Date: Monday, May 6, 2024
Venue: Willamette 1 Room, Hyatt Regency Portland at the Oregon Convention Center
Time: 6:30 PM – 10:00 PM PDT
Cost: FREE with Registration

Learn more about the schedule and speakers and register for free today!

Pygmy Announcement

Alanna Burke — Wed, 03 Apr 2024 23:31:46 +0000

If you’ve been using Lagoon for a little while, you’re probably familiar with pygmy. The original version was written in Ruby, and is now officially deprecated! If you’re still using it, we highly recommend you install the latest version of pygmy, which is now written in Go, or use one of our other local development environments.

Are you using pygmy? Let us know! Chime in on the Lagoon Discord!

And don’t forget our 2024 Community Survey! Let us know how we can best serve the Lagoon community.