Skip to content

docs(site): Mention template editor in template edit docs #7261

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.

Sign up for GitHub

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 4 commits into from
Apr 26, 2023
Merged

docs(site): Mention template editor in template edit docs #7261

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
98bb615
docs(site): Mention template editor in template edit docs
BrunoQuaresma Apr 24, 2023
c5c13e1
Apply suggestions from code review
BrunoQuaresma Apr 25, 2023
bcecbfe
Update docs/templates/README.md
bpmct Apr 26, 2023
6a853ea
Fix format
BrunoQuaresma Apr 26, 2023
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
Next Next commit
docs(site): Mention template editor in template edit docs
  • Loading branch information
@BrunoQuaresma
BrunoQuaresma committed Apr 24, 2023
commit 98bb615f2fd6ed638639c25f8781d6632fc58bf0
6 changes: 5 additions & 1 deletion docs/templates/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -244,9 +244,13 @@ resource "kubernetes_pod" "podName" {

### Edit templates

You can edit a template using the coder CLI. Only [template admins and
You can edit a template using the coder CLI or the UI. Only [template admins and
owners](../admin/users.md) can edit a template.

Using the UI, navigate to the template page, click on the "three dots" button, and select the option "Edit files". In the template editor, you create, edit and remove files. After every change, you have to build the template with the new modifications, to test if they are valid, and after you can publish them make the new template version the active one (the version that is used by default) or not.

> **Tip**: By not publishing a version as active, you can try them in a workspace before making it default for everybody in your organization. This is helpful to debug new changes without impacting others.

Using the CLI, login to Coder and run the following command to edit a single
template:

Expand Down