@@ -63,7 +63,7 @@ The following filters are supported:
63
63
After updating the default version of the template that a workspace was created
64
64
from, you can update the workspace.
65
65
66
- ![ Updating a workspace] ( ../../ images/workspace-update.png )
66
+ ![ Updating a workspace] ( ../images/workspace-update.png )
67
67
68
68
If the workspace is running, Coder stops it, updates it, then starts the
69
69
workspace again.
@@ -86,7 +86,7 @@ Note: If a template is updated such that new parameter inputs are required from
86
86
the user, autostart will be disabled for the workspace until the user has
87
87
manually updated the workspace.
88
88
89
- ![ Automatic Updates] ( ./images/workspace-automatic-updates.png )
89
+ ![ Automatic Updates] ( .. /images/workspace-automatic-updates.png )
90
90
91
91
## Bulk operations (enterprise)
92
92
@@ -99,7 +99,7 @@ The start and stop operations can only be applied to a set of workspaces which
99
99
are all in the same state. For update and delete, the user will be prompted for
100
100
confirmation before any action is taken.
101
101
102
- ![ Bulk workspace actions] ( ../../ images/user-guides/workspace-bulk-actions.png )
102
+ ![ Bulk workspace actions] ( ../images/user-guides/workspace-bulk-actions.png )
103
103
104
104
## Starting and stopping workspaces
105
105
@@ -109,10 +109,10 @@ schedule a workspace to start and stop automatically.
109
109
To set a workspace's schedule, go to the workspace, then ** Settings** >
110
110
** Schedule** .
111
111
112
- ![ Scheduling UI] ( ./images/schedule.png )
112
+ ![ Scheduling UI] ( .. /images/schedule.png )
113
113
114
114
Coder might also stop a workspace automatically if there is a
115
- [ template update] ( ./admin/templates/index.md#Start/stop ) available.
115
+ [ template update] ( .. /admin/templates/index.md#Start/stop ) available.
116
116
117
117
Learn more about [ workspace lifecycle] ( ./workspace-lifecycle.md ) and our
118
118
[ scheduling features] ( ./workspace-scheduling.md ) .
@@ -125,7 +125,7 @@ available.
125
125
126
126
Resources are often destroyed and re-created when a workspace is restarted,
127
127
though the exact behavior depends on the template. For more information, see
128
- [ Resource Persistence] ( ./admin/templates/extending-templates/resource-persistence.md ) .
128
+ [ Resource Persistence] ( .. /admin/templates/extending-templates/resource-persistence.md ) .
129
129
130
130
## Repairing workspaces
131
131
@@ -146,7 +146,7 @@ Coder's filter query:
146
146
- To find workspaces that are currently running, use the filter
147
147
` status:running ` .
148
148
149
- ![ Re-entering template variables] ( ../../ images/templates/template-variables.png )
149
+ ![ Re-entering template variables] ( ../images/templates/template-variables.png )
150
150
151
151
You can also do this in the CLI with the following command:
152
152
0 commit comments