I found 2 bugs in documentation : https://coder.com/docs/v2/latest/admin/auth

''' coder: env: - name: CODER_OAUTH2_GITHUB_ALLOW_SIGNUPS value: true - name: CODER_OAUTH2_GITHUB_ALLOWED_ORGS value: "your-org" - name: CODER_OAUTH2_GITHUB_CLIENT_ID value: "533...des" - name: CODER_OAUTH2_GITHUB_CLIENT_SECRET value: "G0CSP...7qSM" - name: CODER_OAUTH2_GITHUB_ALLOW_EVERYONE value: true '''

1 - true velues need quotes

2 - you can't have both CODER_OAUTH2_GITHUB_ALLOWED_ORGS and CODER_OAUTH2_GITHUB_ALLOW_EVERYONE

If so I can host my public bot on it

why would you need to do that specifically in Coder? obviously, yes, you can, but Coder's point is to use workspaces as development environments so you can develop from anywhere/any device

I know

any source where i can see how to manage template variables

what do you mean by template variables ?

Is there a resource I can reference for using dotfiles properly? I don't quite understand how to use that feature.

i don't remember if there's one but you can simply run ``coder dotfiles -y `` in the template's ``startup_script``

by the way, your template should use rich parameters (``coder_parameter`` blocks) instead of ``variable``s

This is just the docker with dotfiles starter template, lol.

Is the URI something like "https://github.com/Bash-it/bash-it.git"

i swear it was updated

it is yes

``coder dotfiles`` clones that and runs the first script it finds with a specific name (I don't remember the name but it's something like ``setup.sh``)

That makes a lot more sense.

Thanks for the context.

I think there's a dotfiles section in the coder docs if you wanna look

Ahh, yes.. It links to the codespaces docs which explain what you just said.

I usually check the docs first, but never understood dotfiles.

is there a way to pre-build the docker image for all workspaces ?

every time I create a new workspace it's building the image again

here's my image definition

c
resource "docker_image" "basic_env" {
  name = "uwunet/basic-env:latest"

  build {
    context = "./docker"
    tag     = ["uwunet/basic-env", "uwunet/basic-env:latest", "uwunet/basic-env:v0.3"]
  }

  triggers = {
    dir_sha1 = sha1(join("", [for f in fileset(path.module, "docker/*") : filesha1(f)]))
  }
  
  keep_locally = true
}

your trigger might be causing it

as for prebuild, I guess you can deploy to a local registry

Is that specially built for the workspace? Is that necessary?