hi

hello

I have a desktop PC with a GPU, and i would like to be able to use coder locally so that I might be able to access the compute from my desktop on my iPad or laptop. Is it possible to set up coder on local host so that other devices on the same wifi network can access workspaces? I don’t really wanna use the provided tunneling service because that adds a lot of latency for me.

you can try to set your CODER_ACCESS_URL to your Full computer name

for example like http://desktop.lan?

i tried doing that with code-server earlier and it worked (i could access code-server on my ipad) except that local host doesn’t have https so some things like displaying images didn’t work

yes

and to get https you can generate a certificate from

letsencrypt

and provide that to CODER

only if he has a registered domain though

you can’t register .lan

they just point to local ip of that device on the wifi network i think

i know, I am saying that letsencrypt will only give you certificates for "real" internet domains

hmm. For me my computer hasa FQN that ends with

*.*.bilkent.edu.tr

so I could get a cert from letsencrypt. Sorry for misguiding

a locally generated certificate can work but you have to install that to all end devices then

it's also because that is accessible from the outside

May be. But it is only resolved when using our local DNS

So without the IP its not possible

We plan to evaluate the coder enterprise version soon™. Currently, we use authentication via OIDC against our Gitlab, which gets filled with user-data from our LDAP. As we would prefer not to manage the group assignments in two places, I would like to have a conversation what would be the best option going forward with that. I currently see three options: 1. create a "cronjob" which uses the coder API to periodically update group memberships 2. Implement LDAP auth & group handling within coder 3. Use the OIDC data from Gitlab to manage group memberships within coder I'm aware of https://github.com/coder/coder/issues/4106 and would quite like to push this forward and contribute as much as I can as this would be an essential piece for us. What do you think would be the best way?

I personally think that 3 is the best out of them all, I don't know how the implementation is going with that though

The groups can simply read from the user info claims. The problem I see with that is: - it requires that the necessary groups are synchronized with the OIDC provider (our GitLab for example has only a few of our LDAP groups synchronized) - It might be an issue that too many groups get synchronized (we have a nested group and subgroup structure within GitLab which is only partially to organize RBAC behaviors and partially just to organize the repos into functional groups) - It updates group membership only on login-time - so it would be hard to "revoke" memberships. GitLab itself for example lets you decide for a group in GitLab if it shall be a GitLab group or managed by LDAP. If you select LDAP, you can choose an LDAP group to synchronize with, and it periodically fetches updates from that.

How can I create a volume mount that is not deleted when a workspace is deleted, that can also be re-mounted into a new workspace if I so require it? The use case I am thinking of here is accidentally deletions in my personal workspaces

We use host paths for that in one usecase. So a user has his home location on the terminal and no matter how many ws the user spawns. In general I think you have to create the volume outside of coder as TF would always clean up managed resources.

Okay.. I will look into it a bit more

i will be working on this issue in the next few days!

does anyone have any suggestions on doing user based persistence on an AMI backed EC2 EBS VM

What port does coder run on?

That's great news. If you want some input, feel free to poke me.

Is there anyone that have knowledge with kubernetes(minikube) can you DM me?

Hi all! I starting to implement coder for my team and I wonder if we can set the owner's password in the first creation of the coder deployment