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
in a similar vein, instead of nango deploy dev, would be great to have (again, similar to Inngest) a locally running service, e.g. npx nango-cli@latest dev, that automatically watches for changes in the Nango folder and uses these when developing
another use case where it would be nice to have a local runtime: we're two people currently working on different branches adding new syncs separately. So we both need to deploy to dev to test them, which isn't possible without overriding each other's setup?
oh and another reason: to test locally, I need to have a tunnel setup so that Nango dev can trigger the webhook on localhost. This URL is set on the Nango dashboard and so each time a dev contributes they would need to change the callback URL on Nango to point to their machine.
I asked: What are your thoughts on trade-offs between a local runtime vs. an individual cloud environment? (like dev, but per user)
Would by far prefer a local dev runtime: nothing to setup, no tunnel URLs to maintain, automatically runs against code on my computer (no need to remember to do nango deploy dev)
The text was updated successfully, but these errors were encountered:
Could improve:
The text was updated successfully, but these errors were encountered: