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
I am trying to do development with https://github.com/mcknightg/flutterbum by running Meteor from the container and getting the following error (but only when I run meteor from the container, with regular installation of Meteor it works fine):
Error: Error invoking Method 'addCustomer':
Method not found [404]
The method is defined in the email.js file, in the server sub-directory using Meteor.Methods. None of the defined Meteor.Methods is accessible from the client by Meteor.call. I modified the code and copied all Meteor.Method definitions into a .js file and put in the root folder into an "isServer" if-condition. This way all methods are accessible.
As stated before I do not have this issue when I run the app from the local Meteor server, only when I run it from the docker container. It seems to me as if the "server" sub-directory is not accessible from the container.
Can you please advise?
The text was updated successfully, but these errors were encountered:
I am trying to do development with https://github.com/mcknightg/flutterbum by running Meteor from the container and getting the following error (but only when I run meteor from the container, with regular installation of Meteor it works fine):
Error: Error invoking Method 'addCustomer':
Method not found [404]
The method is defined in the email.js file, in the server sub-directory using Meteor.Methods. None of the defined Meteor.Methods is accessible from the client by Meteor.call. I modified the code and copied all Meteor.Method definitions into a .js file and put in the root folder into an "isServer" if-condition. This way all methods are accessible.
As stated before I do not have this issue when I run the app from the local Meteor server, only when I run it from the docker container. It seems to me as if the "server" sub-directory is not accessible from the container.
Can you please advise?
The text was updated successfully, but these errors were encountered: