For some reason after the 1.4.2 update i cannot simply create a nodejs runtime function through the console. The only availiable runtimes can be seen below in the picture. Also the template-starter page presents 5 different runtimes(including node-18), but when using the CLI to init functions(because the console doesnt work), i can only pick node-16 runtime.
Summary
User is encountering an issue when trying to create a node function from the console. They tried updating the function runtime in the function settings and it seemed to work, but then the appwrite console broke with a gateway timeout. User found a solution in a GitHub thread and needs to update the .env file. They also discovered a Discord thread mentioning the need to enable node-18. User wants to know if they should change the value of `_APP_FUNCTIONS_RUNTIMES` in the .env file to `node-18.0`.
Meldiron
Sep 11, 2023, 10:36
Weird 🤔 Can you pls open your .env file and provide me with your value for _APP_FUNCTIONS_RUNTIMES? That might give me some direction towards finding the bug
I jumped the gun, after changing the .env, the appwrite console breaks. I get gateway timeout
Osman
Rank 2: Process
Sep 11, 2023, 11:08
Okay, it seems to work now. However i have an existing function created with node-16.0 runtime. How can i update this to use node-18.0 instead, so i dont have to delete it?
Drake
Sep 11, 2023, 21:11
You'll have to recreate to use the new function syntax. otherwise you can try to update the function runtime in the function settings