Skip to content

chore: minor fix to always use VNC #482

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

Merged
merged 1 commit into from
Jul 13, 2021
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
chore: minor fix to always use VNC
  • Loading branch information
Katie Horne committed Jul 12, 2021
commit d7a205503fa685a29b2dc71b6e5db6f46fd7fa13
8 changes: 3 additions & 5 deletions guides/customization/vnc.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,9 @@
---
title: Virtual Network Computing
title: VNC
description: Learn how to set up a VNC in Coder.
---

This guide will show you how to set up a virtual network computing (VNC) system
in Coder.
This guide will show you how to set up a VNC in Coder.

Coder does not have a specific set of VNC providers it supports. Coder will
render the VNC, as long as it is installed on the image used to create the
Expand All @@ -13,8 +12,7 @@ workspace.
## Step 1: Create the Dockerfile

To begin, create a Dockerfile that you'll use to build an
[image](../../images/index.md) with a virtual network computing (VNC) provider
installed.
[image](../../images/index.md) with a VNC provider installed.

Be sure to set the `HOME`, `USER`, and `PORT` environment variables in the
Dockerfile:
Expand Down