You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm not fully sure if this goes here, or if there is an error in my function parameters, but as the functions are running in my server but not with the new feature of running in local with the cli...
If I try to run locally a deno function, the docker container fails as the deno command it seems to be incorrect
👍 Expected behavior
It should run "Deno run " inside the container
👎 Actual Behavior
Is running "Deno start" which is not a valid command. I detected the error is in line 53 /lib/emulation/utils.js:
startCommand: "deno start",
As consequence, the console throws this error:
ℹ Info: Starting function using Docker ...
♥ Hint: Function automatically restarts when you edit your code.
✓ Success: Visit http://localhost:3000/ to execute your function.
Preparing for start ...
Starting ...
error: unrecognized subcommand 'start'
🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
Linux
🧱 Your Environment
Self-hosted 1.6
👀 Have you spent some time to check if this issue has been raised before?
👟 Reproduction steps
Hi, I'm not fully sure if this goes here, or if there is an error in my function parameters, but as the functions are running in my server but not with the new feature of running in local with the cli...
If I try to run locally a deno function, the docker container fails as the deno command it seems to be incorrect
👍 Expected behavior
It should run "Deno run " inside the container
👎 Actual Behavior
Is running "Deno start" which is not a valid command. I detected the error is in line 53
/lib/emulation/utils.js
:startCommand: "deno start",
As consequence, the console throws this error:
🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
Linux
🧱 Your Environment
Self-hosted 1.6
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: