Workspace unhealthy + Advise on big picture
This is my for setting template on gcp vm - when i manually create workspace in the UI, it says, Agent is unhealthy
Big picture
1. I want to provision repos (both public repos and private repos that I have with me) to developers when they click a button in my platform UI
2, They are presented with a code editor where they can work, raise PR (Like CodePen - instantaneously)
3. I don't want to present them with coder account screen -decouple all of this and give them the option to only start or stop workspaces quickly. 4. Finally, when I use key.json in my .tf file, I can see my key exposed in the Template source code in coder UI - can you suggest best practices? Kindly help me with my workspace setup Thanks!!!!!
3. I don't want to present them with coder account screen -decouple all of this and give them the option to only start or stop workspaces quickly. 4. Finally, when I use key.json in my .tf file, I can see my key exposed in the Template source code in coder UI - can you suggest best practices? Kindly help me with my workspace setup Thanks!!!!!
10 Replies
Category: Help needed
Product: Coder OSS (v2)
What platform are you hosting Coder OSS (v2) on?
hey @bicboi5622 did you base this template on any of our examples?
for the key, I would recommend using an environment variable instead, but it will always have to be exposed to the template in some way
you should just make sure that your API key has just the right permissions to avoid issues
i think i got in a github repo
can you show me an example using the current template- how do i specify repo url
Reg: api key, not a big deal now, i just want to make a poc for now .
am i in the correct route ? This is what i need to spin up a code editor correct? @Phorcys Kindly give me some pointers, thanks mate 🙂
hey @bicboi5622 sorry for the delayed answer, is your Coder deployment accessible from the outside?
okay, do you have a
coder.example.com domain where Coder is accessible?
basically, I think you need to replace CODER_ACCESS_URL in your config with something that is available to the outside, because GCP does not know how to reach your Coder deployment at the moment, hence why the unhealthy agentOk i will try this, thanks
hey @bicboi5622, any luck?
do i need to purchase a domain for this ? does it work, any name i give?
since you are using GCP, your Coder instance needs to be accessible from the outside world
the access URL is what is being passed to GCP, so it has to be something that you can access from the outside
so you should set your
CODER_ACCESS_URL to http://<IP>, but I would advise that you quickly replace the http traffic with https using a self-signed cert