Mr_Neezer
Mr_Neezer
Explore posts from servers
DDenoCCoder.com
PostsComments
CCoder.com
Created by Mr_Neezer on 10/14/2022 in #help
SSH Config for other apps?
No description
11 replies
CCoder.com
Created by Mr_Neezer on 10/7/2022 in #help
Custom button, like the code-server one?
I setup a resource block like I saw in some of the example Coder templates for a different service running in my workspace, Tilt: 
resource "coder_app" "tilt" {
  agent_id      = coder_agent.main.id
  name          = "tilt"
  icon          = "https://yt3.ggpht.com/ytc/AMLnZu_KBLJd3vBogFZfah1GLQHiB3LQmjL9t4ZKyVpR=s68-c-k-c0x00ffffff-no-rj"
  url           = "http://localhost:10350"
  subdomain     = false

  healthcheck {
    url       = "http://localhost:10350"
    interval  = 3
    threshold = 10
  }
}
resource "coder_app" "tilt" {
  agent_id      = coder_agent.main.id
  name          = "tilt"
  icon          = "https://yt3.ggpht.com/ytc/AMLnZu_KBLJd3vBogFZfah1GLQHiB3LQmjL9t4ZKyVpR=s68-c-k-c0x00ffffff-no-rj"
  url           = "http://localhost:10350"
  subdomain     = false

  healthcheck {
    url       = "http://localhost:10350"
    interval  = 3
    threshold = 10
  }
}
The button shows up on my workspace dashboard in Coder, and seems to accurately reflect the status (yay!). But trying to navigate to it and all my assets are broken; I think because they are relative to the root /asset/path and not relative ./asset/path. I saw https://github.com/coder/coder/pull/4263 was recently pushed, but I don't understand how this helps with relative_path going away... or is that not related? I tried changing subdomain = true but that made no discernible difference. Confused.
5 replies
CCoder.com
Created by Mr_Neezer on 10/7/2022 in #help
Prevent destroying and recreating home volume on workspace update
Using this example template: https://github.com/coder/coder/tree/main/examples/templates/do-linux When I make a change to cloud-config.tftpl, the volume that houses my user's home directory gets destroyed and recreated each time I update the workspace to the newest version of my template. How can I prevent this? I'd like to be able to push a new version of the template that, say, installs some additional program, and have the user be able to update their workspace to the new version without blasting whatever the user was working on in their home directory.
72 replies