How to verify that 'frappe.publish_realtime()' has actually published something?

[MartinHBramwell]

I have successfully got a functioning NodeJS/Express app situated in a properly functioning Frappe app.

The next step was to get going with…

frappe.publish_realtime('my_event', {etc})

… in the Frappe app and with …

var subscriber = redis.createClient();
subscriber.on("my_event", function (channel, message) {  etc, etc })

… running in the NodeJS app.

I used this article to get started : How to get Realtime Updates in your App from ERPNext via Socket.io and Redis, but it has a bunch of errors, so I don’t think the author (@joshiparthin ?? ) ever tested to be sure he was describing something that functions as advertised.

Meanwhile, I can’t find any evidence in my system that publish_realtime() is actually doing anything at all.

I searched the code and found that chat and blog post both use subscriber.on, but in my development environment neither of those work.

There are hints from several years ago that publish_realtime() only works in production mode.

There’s this Github Issue : [ frappe.async.realtime_publish not working] (frappe.async.realtime_publish not working · Issue #1963 · frappe/frappe · GitHub) and there’s this post : Frappe.publish_realtime

My questions are:

How can I see, with logging messages, or similar, if frappe.publish_realtime() is actually publishing my event?

Does publish_realtime() NOT work in development mode?

[Antony_Praveenkumar]

are you running in the debugger mode start the bench using this command

bench start

Its working for me

@MartinHBramwell

Does publish_realtime() NOT work in development mode?

[519_Hamza_Habeeb]

WebSocket is closed before the connection is established.

This is the error i see in the console. websocket is on 9000 port
working on development server
please help

[Antony_Praveenkumar]

Please check this tutorial

[Tutorial] Realtime (socket.io)

Summary This section going to explain how socket.io is used in frappe and we can use the frappe Realtime Feature in ERPNext. Reference Document Realtime (socket.io) Get Started You can code from the Custom App, Server Script & Client Script its depends on the requirement. Here is the scenario Assume you have a doctype with the name of Less Hour Request from that context the below code will be there. you can implement this any doctype have to change the values accordingly. frappe.publish_pr…

And share some screen shot its help me to understand the error

Which Version ERPNext your using?

@519_Hamza_Habeeb

WebSocket is closed before the connection is established.

This is the error i see in the console. websocket is on 9000 port
working on development server
please help

[519_Hamza_Habeeb]

sure i just read that thread but i didnt find anything that could help me

[Antony_Praveenkumar]

• Is your machine self hosted?
• Which version ERPNext your using?
• Is it running in Docker?

@519_Hamza_Habeeb

sure i just read that thread but i didnt find anything that could help me

[519_Hamza_Habeeb]

selfhosted
v14 erpnext
manual install (not docker)

[Antony_Praveenkumar]

I’m using Docker For development its working fine for me. make sure the redis running fine or not

@MartinHBramwell

How can I see, with logging messages, or similar, if frappe.publish_realtime() is actually publishing my event?

Does publish_realtime() NOT work in development mode?

Why your using the redis try the tutorial once i attached above. one more importand. try to run in

bench start

Because I worked without docker also its working fine that time also.

@MartinHBramwell

var subscriber = redis.createClient();
subscriber.on("my_event", function (channel, message) {  etc, etc })

[nextgen]

to make realtime working in devlopent instance dont call the app from ip
go to windows hosts file and add belwo

168.230.189.126 sitename

and then call your app like this by site name and the port you are use
sitename:8080