FAQ - Docker Extension

Common questions about using the Livecycle Docker Extension

What is the difference between the Livecycle Docker Extension and Ngrok?

The Livecycle Docker Extension is integrated with Docker and provides a smoother experience for Docker users. Consistent URLs, private environments, organizations, and Google/Github authentication are supported out of the box. The Livecycle dashboard provides debugging capabilities that include log inspection, shell access, and container inspection. Lastly, integration with the Preevy CLI allows you to create preview environments for Pull Requests - remote ephemeral environments that can be used when your development machine is offline.

Which frameworks and languages does Livecycle support?

Livecycle is language and framework agnostic. It works with anything that runs in a Docker container.

What security features does the Livecycle Docker extension offer?

The Livecycle Docker Extension uses a secure SSH tunnel to expose your local development environment using Livecycle's tunnel server, which is only accessible using HTTPS.

You can enable private URLs to restrict access to your environment.

How do I get started with the Livecycle Docker Extension?

You can get started with the Livecycle Docker Extension by following the steps in the Getting Started section of this document.

What makes the Livecycle Docker Extension different from other tools?

Livecycle Docker extension is integrated with the Preevy CLI and the Livecycle managed service. Using the Preevy CLI, you can provision remote ephemeral environments that can be used in addition to sharing local environments. This functionality can also be used in your CI pipeline to provision preview environments for Pull Requests. The Livecycle managed service adds additional layers of management, collaboration, review, and debugging on top of shared environments.

Is using the Livecycle Docker Extension free?

Yes, the Livecycle Docker Extension is free to use.

Does Livecycle have my access to my/company data or code?

No, Livecycle does not have access to your data or code. We just do tunneling. The building and running of your code is done on your machine or cloud.

How do I get support for the Livecycle Docker Extension?

Join the Livecycle Community on Slack to get support for the Livecycle Docker Extension.