Ammar Bandukwala
Ammar Bandukwala
E.g we should require that the user enters their workspace name when deleting it, similar to GitHub. 
A helpful metric for each template is how long they take to build. Fortunately, we have this data already with build logs, so a semi-complex SQL query should suffice.
As a template admin, I only want certain users to access specific templates. For example, I have experimental templates I want to use myself. I also have contractors that should...
I have a complex startup script: ```hcl resource "coder_agent" "dev" { arch = "amd64" os = "linux" startup_script =
Yeah, you could `coder ls | head -n 1` to figure them out, but in the future we will have so many that some will not be shown by default,...
We should explain how to geographically distribute a Coder deployment. These documents should include how to troubleshoot network issues and how the DERPs work. Related #3227
We should add quickstarts for each of these major providers and then link directly to those quickstarts from coder.com. - [x] Docker (although it should be revisited and updated) -...
As a first time Coder user, I may not want to invest in Docker or some other compute substrate to enjoy remote development. I might be totally satisfied with setting...
As the cloud budget holder and admin, I want to quickly find all running workspaces to see if any should be shut down. I naturally reach for a filter.
Right now, only the `coderdtest` uses the live DB in `test/postgresql`. We should abstract it out the fake/live selection logic so the CLI and metricscache benefit from better testing.