TitiMoby
TitiMoby
CCoder.com
Created by TitiMoby on 11/22/2024 in #help
One Kubernetes cluster for Coder and one for the workspaces: how do I specify the ~/.kube/config for
/close
13 replies
CCoder.com
Created by TitiMoby on 11/22/2024 in #help
One Kubernetes cluster for Coder and one for the workspaces: how do I specify the ~/.kube/config for
for now, I did not find a easy way and we decided to have dedicated nodepool for workspace with a nodeSelector on a label
13 replies
CCoder.com
Created by TitiMoby on 11/22/2024 in #help
One Kubernetes cluster for Coder and one for the workspaces: how do I specify the ~/.kube/config for
this week is a bit overloaded but I have to check quickly for another coming workshop
13 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
/close
22 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
I don't know if it's the right place to explain my point of view, but let's give it a try. At first, you have the create command. Documentation says: Usage
coder create [flags] [name]
coder create [flags] [name]
And then you have: Description:
- Create a workspace for another user (if you have permission):

$ coder create <username>/<workspace_name>
- Create a workspace for another user (if you have permission):

$ coder create <username>/<workspace_name>
I would prefer a clear explanation for the name parameter which can be either workspace or user/workspace. Let's say, I have the information needed if I read the create documentation. On the other hand, the delete documentation says: Usage
coder delete [flags] <workspace>
coder delete [flags] <workspace>
And there is no description afterwards explaining the "with or without user" So there is a discrepancy between the two documentation: one is using a parameter name and have clues on what you can put in name, the other one is using workspace and has no detail. I know it might sounds minor, but an old fox like me felt in the trap 😉
22 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
Considering my initial question, I think I got all I needed. 💞
22 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
So I can confirm that: - @Phorcys spotted I forgot to include user$i/ - The documentation is a not coherent between create and delete and maybe describe the parameter
name
name
as either <workspace name> or <user name>/<workspace name> in both case (even if I should have though of it by my API version in the near future
22 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
I can confirm that point: you do have to delete workspaces from a user before deleting it.
22 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
Ohhhhh you mean
coder delete user$i/workspace$i
coder delete user$i/workspace$i
I’ll have to test it. Did I misread the documentation? It was not really clear. If you want, after my two last events for 2024, I’ll have some time to make some feedback on what I found during my usage of Coder
22 replies
CCoder.com
Created by TitiMoby on 11/13/2024 in #help
delete a workspace from cli fails when it was created on behalf of another user
In the meantime I tried to implement this with API calls. but I got 405, DELETE is not allowed on this route
22 replies
CCoder.com
Created by TitiMoby on 11/12/2024 in #help
different behaviour between desktop VSCode and code-server using gradio app
/close
11 replies
CCoder.com
Created by TitiMoby on 11/12/2024 in #help
different behaviour between desktop VSCode and code-server using gradio app
due to time constraint, we are going to use a trick from gradio which host temporary our app. I'll get back but it will imply to understand how the internals of Gradio works which is...
11 replies
CCoder.com
Created by TitiMoby on 11/12/2024 in #help
different behaviour between desktop VSCode and code-server using gradio app
If you need I also implemented serving with uvicorn that allows more control
11 replies
CCoder.com
Created by TitiMoby on 11/12/2024 in #help
different behaviour between desktop VSCode and code-server using gradio app
That’s what I’m  looking for. But I saw a lot of routes properly served. And I don’t blame coder itself, there is some magic in Gradio to serve a front end from backend code. I am currently experimenting with streamlit to see if I have a better result. The idea is to know what I can do in data science workshops
11 replies
CCoder.com
Created by TitiMoby on 10/25/2024 in #help
how to use files in script after cloning a repository?
thanks a lot, I now have a lot of readings 😉
38 replies
CCoder.com
Created by TitiMoby on 10/25/2024 in #help
how to use files in script after cloning a repository?
I'm available for the next 20 minutes, I don't know if it is possible for you
38 replies
CCoder.com
Created by TitiMoby on 10/25/2024 in #help
how to use files in script after cloning a repository?
being able to have those variable is the base for our workshop. do you think this is possible with the devcontainer approach?
38 replies
CCoder.com
Created by TitiMoby on 10/25/2024 in #help
how to use files in script after cloning a repository?
If this useful, I can describe the compete use case to you or any interested product manager or tech lead
38 replies
CCoder.com
Created by TitiMoby on 10/25/2024 in #help
how to use files in script after cloning a repository?
yes, this was the way we were able to provide the attendee a full environment for the workshop with specific env variables as API token and such
38 replies
CCoder.com
Created by TitiMoby on 10/25/2024 in #help
how to use files in script after cloning a repository?
I understood this but you won't be able to have env variable in the end except if coder_script has a syntax to
source setup.sh
source setup.sh
38 replies