Prompt the user for their NODE_VERSION
complete
M
Matt Gale
Hi Render friends!
I run a blog about render and when I'm looking for topics to help people with, one of the very common things I see (using node as an example) is that people don't know to include
NODE_VERSION
as an env variable when they deploy a service (afaict, this happens when using the dashboard to create a service and not a blueprint). Despite the documentation about all the different ways of specifying the runtime version, this oversight happens, as you probably already know, constantly.A thought: if someone selects the Node runtime during service definition, if they don't have a .nvmrc/.node-version/engine defined, it might help to either create a default
NODE_VERSION
env variable or popup/prompt to tell the user: "Hey! I see you don't have a version defined, here's a link you should know about" to inform them of this pretty essential config.Log In
A
Alex Bi
complete
A
Alex Bi
Matt Gale We recently updated default Node version to Node 20 (LTS). Does this largely resolve the problem of specifying a Node version?
M
Matt Gale
Alex Bi: I saw this! I'm willing to bet this will largely reduce the instances of node version confusion for new uers.
IMO I still think the correct fix is communicating with the user to tell them what's happening, but I'm willing to accept this as done until data presents differently.
Thanks!
A
Alex Bi
Matt Gale: Makes sense! I'll mark this as complete for now, but please comment here if you still see this happening. If so I can take another look. Thanks for the feedback!