You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/about/screenshots.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -2,19 +2,19 @@
2
2
3
3
## Log in
4
4
5
-

5
+

6
6
7
7
Install Coder in your cloud or air-gapped on-premises. Developers simply log in
8
8
via their browser to access their Workspaces.
9
9
10
10
## Templates
11
11
12
-

12
+

13
13
14
14
Developers provision their own ephemeral Workspaces in minutes using pre-defined
15
15
Templates that include approved tooling and infrastructure.
16
16
17
-

17
+

18
18
19
19
Template administrators can either create a new Template from scratch or choose
20
20
a Starter Template.
@@ -26,25 +26,25 @@ underlying infrastructure that Coder Workspaces run on.
26
26
27
27
## Workspaces
28
28
29
-

29
+

30
30
31
31
Developers create and delete their own workspaces. Coder administrators can
32
32
easily enforce Workspace scheduling and autostop policies to ensure idle
33
33
Workspaces don’t burn unnecessary cloud budget.
34
34
35
-

35
+

36
36
37
37
Developers launch their favorite web-based or desktop IDE, browse files, or
38
38
access their Workspace’s Terminal.
39
39
40
40
## Administration
41
41
42
-

42
+

43
43
44
44
Coder administrators can access Template usage insights to understand which
45
45
Templates are most popular and how well they perform for developers.
46
46
47
-

47
+

48
48
49
49
Coder administrators can control *every* aspect of their Coder deployment.
0 commit comments