How to handle WebSocket messages in an appmod using Yaws?

Probably, your appmod is not in PATH, or its module is not loaded in the yaws web server VM instance or shell. Try to call this method in the yaws shell once your web server starts:

1> mywebsocket:handle_message({text,"Some Data"}).

Now, in the yaws.conf file, edit it to include the ebin folder where the compiled file of your appmod exists. Actually make sure to add all PATHS to executable code that your appmod depends on. it should appear like this:

# This the path to a directory where additional
# beam code can be placed. The daemon will add this
# directory to its search path

ebin_dir = "F:/programming work/erlcharts-1.0/ebin"
ebin_dir = "C:/SomeFolder/another_library-1.0/ebin"
ebin_dir = "D:/Any/Folder/myappmods"

# This is a directory where application specific .hrl
# files can be placed. application specifig .yaws code can
# then include these .hrl files

include_dir = "C:\Program Files (x86)\Yaws-1.90/examples/include"
include_dir = "D:/Any/Folder/myappmods/include"

Now, enter the PATHs to all your code in the yaws conf file. Do not worry about the forward slashes or back slashes, yaws always gets its way around Paths. For UNIX/LINUX it remains the same e.g. ebin_dir = "/usr/local/lib/erlang/lib/myapp-1.0/ebin".

However, note that your modules will not be loaded yet until yaws web server fully initialises