Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: remove duplicate livecycle extension FAQ section #407

Merged
merged 1 commit into from
Jan 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 1 addition & 55 deletions site/docs/docker-extension.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,58 +105,4 @@ Now, you can observe that the environment is successfully deployed to AWS, and y

## FAQ

<details>
<summary>What is the difference between the Livecycle Docker Extension and Ngrok?</summary>

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.
</details>

<details>
<summary>Which frameworks and languages does Livecycle support?</summary>

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

<details>
<summary>What security features does the Livecycle Docker extension offer?</summary>

The Livecycle Docker Extension uses a secure <a href="https://livecycle.io/blogs/preevy-proxy-service-2/" target="_blank">SSH tunnel</a> 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.
</details>

<details>
<summary>How do I get started with the Livecycle Docker Extension?</summary>

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

<details>
<summary>What makes the Livecycle Docker Extension different from other tools?</summary>

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.
</details>

<details>
<summary>Is using the Livecycle Docker Extension free?</summary>

Yes, the Livecycle Docker Extension is free to use.
</details>

<details>
<summary>Does Livecycle have my access to my/company data or code?</summary>

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.
</details>

<details>
<summary>How do I get support for the Livecycle Docker Extension?</summary>

Join the <a href="https://community.livecycle.io" target="_blank">Livecycle Community</a> on Slack to get support for the Livecycle Docker Extension.
</details>
See the [Docker Extension FAQ](/FAQs/docker-extension).