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
My production server is a ubuntu 16 managed by Plesk Onyx, which uses Phusion Passenger to manage different nodejs apps. Remotedev-Server does not work on this setup.
I'm not very acquainted with server technology, but what I've concluded is that SocketCluster is a somewhat "competitor" with Passenger in the clustering part.
Nonetheless, I've tried putting remotedev-server to work with Passenger but it does not seem to pickup the SocketCluster port listening. My guess is that SocketCluster does not use the node http server listen() method which is the pickup entry point for Passenger.
What are your thoughts on this?
My solution would be to rewrite the worker.js so it does not use SocketCluster, but then I guess Redux Devtools will not be able to read a report from it, am I right? If so, I would be using this modified remotedev-server to only collect the reports and then manually transfer them to a development setup where I would use the normal (with SocketCluster) version.
Thank you
The text was updated successfully, but these errors were encountered:
I'm sorry for answering after 1.5 years. Socketcluster creates separate from the current process workers, which is nice for complex apps, but I agree that it's not much needed for our use case. I'm open to replace it to just ws if someone needs it. Alternatively, you can decouple only express part, we could move it to a separate file to be easily imported.
My production server is a ubuntu 16 managed by Plesk Onyx, which uses Phusion Passenger to manage different nodejs apps. Remotedev-Server does not work on this setup.
I'm not very acquainted with server technology, but what I've concluded is that SocketCluster is a somewhat "competitor" with Passenger in the clustering part.
Nonetheless, I've tried putting remotedev-server to work with Passenger but it does not seem to pickup the SocketCluster port listening. My guess is that SocketCluster does not use the node http server listen() method which is the pickup entry point for Passenger.
What are your thoughts on this?
My solution would be to rewrite the worker.js so it does not use SocketCluster, but then I guess Redux Devtools will not be able to read a report from it, am I right? If so, I would be using this modified remotedev-server to only collect the reports and then manually transfer them to a development setup where I would use the normal (with SocketCluster) version.
Thank you
The text was updated successfully, but these errors were encountered: