@@ -61,14 +61,14 @@ by default.
61
61
62
62
### User
63
63
64
- A [ user] ( ../users.md ) is an individual who utilizes the Coder platform to
64
+ A [ user] ( ../admin/ users.md ) is an individual who utilizes the Coder platform to
65
65
develop, test, and deploy applications using workspaces. Users can select
66
66
available templates to provision workspaces. They interact with Coder using the
67
67
web interface, the CLI tool, or directly calling API methods.
68
68
69
69
### Workspace
70
70
71
- A [ workspace] ( ../../ workspaces.md ) refers to an isolated development environment
71
+ A [ workspace] ( ../workspaces.md ) refers to an isolated development environment
72
72
where users can write, build, and run code. Workspaces are fully configurable
73
73
and can be tailored to specific project requirements, providing developers with
74
74
a consistent and efficient development environment. Workspaces can be
@@ -82,20 +82,20 @@ Coder templates and deployed on resources created by provisioners.
82
82
83
83
### Template
84
84
85
- A [ template] ( ../../ templates/index.md ) in Coder is a predefined configuration
86
- for creating workspaces. Templates streamline the process of workspace creation
87
- by providing pre-configured settings, tooling, and dependencies. They are built
88
- by template administrators on top of Terraform, allowing for efficient
89
- management of infrastructure resources. Additionally, templates can utilize
90
- Coder modules to leverage existing features shared with other templates,
91
- enhancing flexibility and consistency across deployments. Templates describe
92
- provisioning rules for infrastructure resources offered by Terraform providers.
85
+ A [ template] ( ../templates/index.md ) in Coder is a predefined configuration for
86
+ creating workspaces. Templates streamline the process of workspace creation by
87
+ providing pre-configured settings, tooling, and dependencies. They are built by
88
+ template administrators on top of Terraform, allowing for efficient management
89
+ of infrastructure resources. Additionally, templates can utilize Coder modules
90
+ to leverage existing features shared with other templates, enhancing flexibility
91
+ and consistency across deployments. Templates describe provisioning rules for
92
+ infrastructure resources offered by Terraform providers.
93
93
94
94
### Workspace Proxy
95
95
96
- A [ workspace proxy] ( ../workspace-proxies.md ) serves as a relay connection option
97
- for developers connecting to their workspace over SSH, a workspace app, or
98
- through port forwarding. It helps reduce network latency for geo-distributed
96
+ A [ workspace proxy] ( ../admin/ workspace-proxies.md ) serves as a relay connection
97
+ option for developers connecting to their workspace over SSH, a workspace app,
98
+ or through port forwarding. It helps reduce network latency for geo-distributed
99
99
teams by minimizing the distance network traffic needs to travel. Notably,
100
100
workspace proxies do not handle dashboard connections or API calls.
101
101
@@ -212,11 +212,11 @@ resource "kubernetes_deployment" "coder" {
212
212
213
213
For sizing recommendations, see the below reference architectures:
214
214
215
- - [ Up to 1,000 users] ( 1k-users.md )
215
+ - [ Up to 1,000 users] ( ./ 1k-users.md)
216
216
217
- - [ Up to 2,000 users] ( 2k-users.md )
217
+ - [ Up to 2,000 users] ( ./ 2k-users.md)
218
218
219
- - [ Up to 3,000 users] ( 3k-users.md )
219
+ - [ Up to 3,000 users] ( ./ 3k-users.md)
220
220
221
221
### Networking
222
222
@@ -297,7 +297,7 @@ considerations:
297
297
active users.
298
298
- Enable High Availability mode for database engine for large scale deployments.
299
299
300
- If you enable [ database encryption] ( ../encryption.md ) in Coder, consider
300
+ If you enable [ database encryption] ( ../admin/ encryption.md ) in Coder, consider
301
301
allocating an additional CPU core to every ` coderd ` replica.
302
302
303
303
#### Resource utilization guidelines
@@ -320,26 +320,26 @@ could affect workspace users experience once the platform is live.
320
320
321
321
### Helm Chart Configuration
322
322
323
- 1 . Reference our [ Helm chart values file] ( ../../../ helm/coder/values.yaml ) and
323
+ 1 . Reference our [ Helm chart values file] ( ../../helm/coder/values.yaml ) and
324
324
identify the required values for deployment.
325
325
1 . Create a ` values.yaml ` and add it to your version control system.
326
326
1 . Determine the necessary environment variables. Here is the
327
- [ full list of supported server environment variables] ( ../../ cli/server.md ) .
327
+ [ full list of supported server environment variables] ( ../cli/server.md ) .
328
328
1 . Follow our documented
329
- [ steps for installing Coder via Helm] ( ../../ install/kubernetes.md ) .
329
+ [ steps for installing Coder via Helm] ( ../install/kubernetes.md ) .
330
330
331
331
### Template configuration
332
332
333
333
1 . Establish dedicated accounts for users with the _ Template Administrator_
334
334
role.
335
335
1 . Maintain Coder templates using
336
- [ version control] ( ../../ templates/change-management.md ) .
336
+ [ version control] ( ../templates/change-management.md ) .
337
337
1 . Consider implementing a GitOps workflow to automatically push new template
338
338
versions into Coder from git. For example, on Github, you can use the
339
339
[ Update Coder Template] ( https://github.com/marketplace/actions/update-coder-template )
340
340
action.
341
341
1 . Evaluate enabling
342
- [ automatic template updates] ( ../../ templates/general-settings.md#require-automatic-updates-enterprise )
342
+ [ automatic template updates] ( ../templates/general-settings.md#require-automatic-updates-enterprise )
343
343
upon workspace startup.
344
344
345
345
### Observability
@@ -351,13 +351,13 @@ could affect workspace users experience once the platform is live.
351
351
leverage pre-configured dashboards, alerts, and runbooks for monitoring
352
352
Coder. This includes integrations between Prometheus, Grafana, Loki, and
353
353
Alertmanager.
354
- 1 . Review the [ Prometheus response] ( ../prometheus.md ) and set up alarms on
354
+ 1 . Review the [ Prometheus response] ( ../admin/ prometheus.md ) and set up alarms on
355
355
selected metrics.
356
356
357
357
### User support
358
358
359
- 1 . Incorporate [ support links] ( ../appearance.md#support-links ) into internal
360
- documentation accessible from the user context menu. Ensure that hyperlinks
361
- are valid and lead to up-to-date materials.
359
+ 1 . Incorporate [ support links] ( ../admin/ appearance.md#support-links ) into
360
+ internal documentation accessible from the user context menu. Ensure that
361
+ hyperlinks are valid and lead to up-to-date materials.
362
362
1 . Encourage the use of ` coder support bundle ` to allow workspace users to
363
363
generate and provide network-related diagnostic data.
0 commit comments