DEV Community: Alanna Burke

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.

What's New With Lagoon: Deprecations and Upgrades + Release Notes

Alanna Burke — Fri, 29 Mar 2024 23:13:57 +0000

We’ve recently released our upgrade and deprecation policies, and wanted to spotlight them, along with a new home for our release notes in the documentation.

Releases

You can now find each release of Lagoon in the docs, in a new Releases section. The notes will include any important information, including deprecations and upgrades for that release.

Deprecations

Deprecations will continue to be announced in releases, and tracked in the release where the deprecation occurs. They’ll include a rough timeline (for example, we plan to deprecate X in 3 months or in the next release). You can find deprecations for each release in this section of the docs, along with our deprecation policy: https://docs.lagoon.sh/releases/policy/.

For example, looking at the release page for v2.17.0, we have the following deprecation info:

activestandby task image
This release introduces a new active/standby task image that does not require the use of the dioscuri controller. Dioscuri is deprecated and will eventually be removed from the lagoon-remote helm chart. If you use active/standby functionality in your clusters, you should upgrade to lagoon v2.17.0 and update your remote clusters to the version of the lagoon-remote helm chart the v2.17.0 release says to use (see release notes for v2.17.0)

API Harbor support
Support for Harbor in the API will be removed in a future release. If you currently have your core installation with Harbor support, you should move to using the integration within lagoon-remote instead. See the documentation here and read the section about Harbor.

Harbor 2.1 and earlier support
Support for Harbor 2.1.x (chart version 1.5.x) and older in lagoon-remote will be removed in a future release. You should consider upgrading Harbor to a newer version (currently Lagoon supports up to v2.9.x (chart version 1.13.x)), following any recommended upgrade paths from Harbor.

Upgrades

We have also published our upgrade policy, which you can view here: https://docs.lagoon.sh/releases/policy/. Each release page will also include any needed upgrades. For example, in v2.15.2, you can see the following upgrade on the release page:

This release was superseded, and the 2.15.4 release is recommended to be installed instead.

Our general policy is that you should upgrade to each minor version before you upgrade to the latest version.

You should check all upgrade requirements and deprecation notices for all versions as you upgrade.

An example of our suggested policy is as follows:

Currently installed v2.14.0, planning to upgrade to v2.17.0
Upgrade to v2.15.0
Upgrade to v2.16.0
Upgrade to v2.17.0

We hope this information is helpful in your management of Lagoon! Is there anything else you need to know? Hop in the Lagoon Discord and let us know!

And don’t forget our 2024 Community Survey! Tell us how the Lagoon community can best serve you.

What's New With Lagoon: Build Warnings

Alanna Burke — Fri, 22 Mar 2024 02:27:29 +0000

Nobody likes dealing with broken builds, so we’ve tried to make it easier with Lagoon. Lagoon now has the ability to identify potential issues with the build, and highlight them as warnings without failing. This is also a way for the Lagoon team to inform you of pending deprecations and changes to functionality. For example, if we make a change to a setting in lagoon.yml, and there’s something you need to change, the warning will mention it, so you’ll be able to change it before it becomes a breaking change. You’ll still want to resolve these issues ASAP, but they shouldn’t stop your build. If you’re not sure how to resolve them, as always, you can reach out to your Lagoon administrator or the Lagoon community.

Here's a screenshot with an example of a build warning. You can see that the log will have a tag indicating that the build was “Completed with warnings,” and when you expand the log, you’ll see the warning message. Message text will vary depending on the warning, but this gives you an idea.

At the bottom of the log, you can also see how many warnings were in the build:

We’ve also updated our docs with some common issues, so take a look at Lagoon Build Errors and Warnings and Common Docker Compose Issues.

We hope this makes your workflow smoother! Let us know by chiming in on the Lagoon Discord.

And don’t forget our 2024 Community Survey! Tell us how the Lagoon community can best serve you.

Introducing a GitHub Action for Interacting with Lagoon

Alanna Burke — Thu, 07 Mar 2024 03:47:09 +0000

https://github.com/uselagoon/lagoon-action

We're excited to announce the release of the Lagoon Action – a GitHub Action that allows you to integrate with Lagoon, making it easy for you to automate your deployment workflows and manage Lagoon environments directly from your GitHub repository.

Currently the Lagoon action allows you to:

Deploy branches and PRs
Upsert environment variables

Taken together, these two features open up a range of new deployment strategies on Lagoon.

For instance, Lagoon only presently responds to a subset of GitHub webhook options. Now, with the Lagoon action, you’re able to run your CI processes in GitHub itself, and instead of having a webhook call deploy your environment, you can choose to deploy only if the CI process passes.

Getting Started

Getting started with the Lagoon Action is straightforward. Add the action to your GitHub workflow, configure the required parameters, and you're ready to automate your Lagoon deployments. Check out the GitHub repository for detailed documentation and examples.

Requirements

To use the Lagoon CLI Action, ensure you have set up a GitHub Actions secret containing a private SSH key with the necessary permissions added to the Lagoon API. This key will be used for authentication during the deployment process.

We’d love to know if you use this and how it helps your workflow! Hop in to the Lagoon Discord and drop us a line!

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

Lagoon Local Development Environments

Alanna Burke — Fri, 01 Mar 2024 22:55:08 +0000

When working with Lagoon, you have a variety of options for your local development experience - we want you to use whatever works best for you!

Lando

Lagoon integrates nicely with Lando. If you’re familiar with Lando, this is probably a no-brainer, especially if you expect your workflow to be fairly straightforward. Take a look at the Lando docs and see if it’s a fit for your project: https://docs.lando.dev/plugins/lagoon/.

DDEV

If you’re a Drupal developer, you may be familiar with DDEV, which also has a robust Lagoon integration. DDEV supports a variety of PHP and Python-based applications and frameworks. Check out their docs to learn how to use DDEV with Lagoon: https://ddev.readthedocs.io/en/stable/users/providers/lagoon/.

Watch amazee.io’s recent webinar with DDEV’s Lead Maintainer Randy Fay here: https://www.amazee.io/local-development-with-ddev-and-lagoon

Pygmy

Pygmy integrates very closely with Docker. If you’re anticipating complex needs and use cases, and have the time to gain a deep understanding of how it all works, pygmy is probably the choice for you. Read more about pygmy here: https://github.com/pygmystack/pygmy

DIY

While we don’t necessarily encourage it, you can also use a LAMP/MAMP/etc stack and interact with Lagoon locally without a specific local development environment. Docker and Docker Compose are the only hard requirements, but these will make things work a lot more smoothly:

An HTTP reverse proxy for nice URLs and HTTPS offloading.
A DNS system so we don't have to remember IP addresses.
SSH agents to use SSH keys within containers.
A system that receives and displays mail locally.

What does your local Lagoon setup look like? We’d love to hear from you! 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.

Lagoon CLI Cheat Sheet

Alanna Burke — Fri, 23 Feb 2024 01:11:20 +0000

If you’re a Lagoon user, you’re probably using the Lagoon CLI (if not - check it out!). We’ve got a cheat sheet of useful commands to help you get the most out of Lagoon.

Confirm it’s working

# Test it out
lagoon login

# if using something other than main “id_rsa” use the below to point to private key
lagoon login -i ~/.ssh/path-to-rsa

# Use this command to see who you are logged in as
lagoon whoami

Update project settings

# update project branches
lagoon update project -p [project-name] -b "^([branch-1]|[branch-2])$"

# update project repo
lagoon update project -p [project-name] -g git@github.com:[repo-name]/[project-name].git

# update which branch is production
lagoon update project -p [project-name] -E [branch-name]

# set “pull requests enabled” to true for project
lagoon update project -p [project-name] -m true

SSH

# SSH access is for debugging purposes. Any changes made to files will be lost the next time the container restarts. 
# SSH into Lagoon remote
lagoon ssh -p [project-name] -e [environment-name]

Add / Delete Envs

# Manually delete an environment from Lagoon (will not delete the branch from your repo)
lagoon delete environment -p [project-name] -e [environment-name]
# You can also do this through the UI; there is a button on the dashboard which allows you to manually delete envs.

# To add env: 
  # Make sure the branches are set correctly on your project
  # Create branch
  # Make your first commit on the branch and push to repo
  # If you have your branches correctly configured on Lagoon, this should trigger an automatic deployment of the environment.

Variables

# List variables for a project or environment (alias: v)
lagoon list variables

# Add or update a variable to an environment or project
lagoon add variable

# Add or update a variable to an environment or project
lagoon update variable 

# Delete a variable from an environment
lagoon delete variable

List groups, projects, users

# List groups you have access to (alias: g)
lagoon list groups

# List projects in a group (alias: gp)
lagoon list group-projects

# List all users in groups
lagoon list group-users

# List a single users groups and roles
lagoon list user-groups

# List all projects you have access to (alias: p)
lagoon list projects

Backups, archives, cache clearing

# Get a backup download link
lagoon get backup

# Run a drush archive dump on an environment
lagoon run drush-archivedump

# Run a drush cache clear on an environment
lagoon run drush-cacheclear

# Run a drush sql dump on an environment
lagoon run drush-sqldump

You can check out the Lagoon CLI docs here to see a list of all commands and options: https://uselagoon.github.io/lagoon-cli/.

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

What's New With Lagoon: UI Improvements

Alanna Burke — Fri, 16 Feb 2024 16:59:49 +0000

We’re always working to improve our UI, so we thought we’d highlight some new updates and changes!

Create Environment Button

You can now create an environment from the UI! On the project dashboard, you’ll see the new button.

The environment button is visible on the dashboard.

You’ll be led through the steps to create an environment.

Manage Variables in the UI

A totally new feature in Lagoon is the ability to manage variables through the UI!

From the project dashboard, you’ll see the Variables tab, which will display the variables you’ve set, if any. The UI allows you to view or hide the value of the variables. You can also add, modify, and delete variables here.

View of the Variables dashboard.

Adding a new variable. Adding a new variable.

Logs

You may have already seen this one as we rolled it out a little while back, but we’ve also improved the viewing experience for logs in the UI. Logs are now split into sections, making them much easier to review.

An example of the new logs.

Expanding the log section.

Dark Mode

You can now switch between dark and light mode in the Lagoon UI via a handy icon on the top toolbar! We know what a highly requested feature this is.

In light mode, toggle the moon icon to switch to dark mode.

In dark mode, toggle the sun icon to switch to light mode.

That’s all for now, but stay tuned for more updates about Lagoon! You didn’t hear it from us, but rumor has it that the Lagoon UI v2 is officially in the works. Want to give us feedback or help out? Join the Lagoon community on Discord and say hello!

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