In-Flight Collaboration With The Livecycle Docker Extension
Tags: docker, productivity, development, collaboration
Published: 2023-10-04 12:05:33

### TL;DR
- We've launched our new [Docker Extension](https://open.docker.com/extensions/marketplace?extensionId=livecycle/docker-extension)! Developers use it to share local dev environments and get feedback MUCH earlier in the SDLC. We invite you to use it and benefit from it.

- We're also inviting everyone to join our [Slack community](https://community.livecycle.io/) focused on developer collaboration, developer experience and anything needed to get started with Livecycle.

### Software developers hate context switching
For software developers, context switching is a buzzkill. And context switching into past tasks is even worse. Getting A DM from your PM that starts with “So, about the feature you worked on two weeks ago…” is never good news. 

It means not only pulling your head out of the code, and out of the flow - but also out of the present and into your past self - the person who designed “that feature”, built it, tested it and fixed it, and knew all about its countless, beautiful, intricate details. 

But that past self has been gone for two weeks now. So to deal with this issue, you’re going to have to find a way to conjure them up. And you can expect this to bring you extra work, because it’s becoming rapidly apparent that your two-weeks ago past self was a moron who couldn’t code properly, and couldn’t document to save their life, and they built embarrassingly broken stuff which the “present-you” has to fix right now.

### There's gotta be a better way

But what if I told you there’s a way to ensure that you get that message about the feature from two weeks ago… two weeks ago? 

What if your your past could get the feedback they need while they were still in context. This would allow your present self could keep their head in the code and in the current flow.


![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/e0wvqhozzxt2n5idz7ic.jpg)

Well, if this resonates with you, then you’ve come to the right place. Because here at Livecycle this is what we do best. 

We cut the feedback loop short by allowing you to share your work while you’re still in context. Using Livecycle, developers can share their work with whomever they want at any point in the SDLC and get instant feedback in context. This ensures that issues are raised, understood and addressed ASAP and not two weeks later.

### Livecycle's multiple workflow entry points

Livecycle supports multiple entry points into your development workflow:
- Our OSS CLI tool, [Preevy](https://github.com/livecycle/preevy) provisions [preview environments](https://livecycle.io/blogs/the-magic-of-ephemeral-preview-environments/) on your cloud provider or [Kubernetes](https://livecycle.io/blogs/preevy-now-supports-kubernetes/) cluster
- [Preevy](https://github.com/livecycle/preevy) also integrates into your [CI pipeline](https://preevy.dev/ci/overview) to convert your pull requests into easily shareable ephemeral environments
- And now, our new Docker Desktop Extension allows you to do the same for your local development environment

### Share local dev environments instantly with the Docker Extension

With the launch of the Livecycle Docker Extension, teams working on dockerized applications can shift the review process much farther left than ever before. Changes, bug fixes and new features can get reviewed instantly without the hassle of staging environments or CI builds.

![Livecycle extension](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kqke02joj9kptv8gkbdb.jpg)

The ability to share local dev environments instantly has many useful applications. Here are a few to illustrate the value it can bring to you and your team:

#### In-Flight UI Reviews

One of the most common use cases is enabling collaboration between developers and non-technical stakeholders early in the workflow. Using the Livecycle extension, you can get instant feedback on the latest front-end changes you’re working on your machine.

By simply opening a tunnel and creating a shareable URL, you enable anyone on the team to use a browser to securely access the relevant services.

So designers, QA, marketing and management can all see the application and use built-in commenting and collaboration tools to leave clear, actionable feedback. And since everything is in context, you’ll be able to communicate quickly and fix issues MUCH earlier in the development lifecycle.

{% embed https://www.youtube.com/watch?v=OC1QOx_tpmk %}

#### In-Flight Debugging

Another common use case is enabling developers to work together to review and debug code changes as soon as possible.

With the Livecycle extension, you can instantly share any front-end or back-end service running on your machine.
By simply opening a tunnel and creating a shareable URL, you enable your team to use their browsers to securely access these services.

Your teammates can now see real-time logging, catch errors and execute commands in a terminal, so you can collaboratively fix issues MUCH earlier in the development lifecycle.

{% embed https://www.youtube.com/watch?v=_grdYVad_cM %}

These are just two of the many ways in which the extension can bring you fewer headaches and a better developer experience. So be sure to try the [Livecycle Extension](https://open.docker.com/extensions/marketplace?extensionId=livecycle/docker-extension) today! Also, now we have the [docs](https://preevy.dev/integrations/docker-extension) as well.

Getting started with Livecycle Extension video:

{% embed https://www.youtube.com/watch?v=lb2nsFk9mRE %}

And, you're also invited to join our [Slack community](https://community.livecycle.io/) focused on developer collaboration, developer experience and anything needed to get started with Livecycle.