|
| 1 | +#Screenshots |
| 2 | + |
| 3 | +##Log in |
| 4 | + |
| 5 | + |
| 6 | + |
| 7 | +Install Coder in your cloud or air-gapped on-premises. Developers simply log in |
| 8 | +via their browser to access their Workspaces. |
| 9 | + |
| 10 | +##Templates |
| 11 | + |
| 12 | + |
| 13 | + |
| 14 | +Developers provision their own ephemeral Workspaces in minutes using pre-defined |
| 15 | +Templates that include approved tooling and infrastructure. |
| 16 | + |
| 17 | + |
| 18 | + |
| 19 | +Template administrators can either create a new Template from scratch or choose |
| 20 | +a Starter Template. |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +Template administrators build Templates using Terraform. Templates define the |
| 25 | +underlying infrastructure that Coder Workspaces run on. |
| 26 | + |
| 27 | +##Workspaces |
| 28 | + |
| 29 | + |
| 30 | + |
| 31 | +Developers create and delete their own workspaces. Coder administrators can |
| 32 | +easily enforce Workspace scheduling and autostop policies to ensure idle |
| 33 | +Workspaces don’t burn unnecessary cloud budget. |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +Developers launch their favorite web-based or desktop IDE, browse files, or |
| 38 | +access their Workspace’s Terminal. |
| 39 | + |
| 40 | +##Administration |
| 41 | + |
| 42 | + |
| 43 | + |
| 44 | +Coder administrators can access Template usage insights to understand which |
| 45 | +Templates are most popular and how well they perform for developers. |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | +Coder administrators can control_every_ aspect of their Coder deployment. |
| 50 | + |
| 51 | + |
| 52 | + |
| 53 | +Coder administrators and auditor roles can review how users are interacting with |
| 54 | +their Coder Workspaces and Templates. |
| 55 | + |
| 56 | + |
| 57 | + |
| 58 | +Coder administrators can monitor the health of their Coder deployment, including |
| 59 | +database latency, active provisioners, and more. |