I have the amazon ami server, through this i want to achieve socket communication by using nodejs, redis server.
I follwed the below to install nodejs and redis server, npm
https://www.metachris.com/2015/10/how-to-install-nodejs-5-on-centos-and-ubuntu/
https://gist.github.com/dstroot/2776679
Even i installed socket server and socket express also.
when i was try to know the express version this i got this error please see the attached screenshot
Can anyone please suggest me what i can do to achieve socket communication in amazon ami server.
Use node package manager commands. npm -v packagename
Related
I have a node.js server an I'm trying to install Roundeube to it but I've only found Roundcube installations for CPanel and Docker. I'm using google firebase to host a static website that I want a function inbox on. It is a node.js with their own functional CLI and I've tried to install CPanel and docket but it seem to work. Any advice on how I could get Roundcube to function on node.js?
FYI I have a fully functional SMTP server.
i have setup wsl in my windows server machine and started the redis service there.
from the windows command prompt i can use wsl redis-cli and run the redis commands.
but my node application is not able to detect the redis inside wsl. i am using redis in my node project.
is there any third party module i need to add to able to connect, this answer showed to add it in python.
the wsl's redis port was readily available.
const client = redis.createClient(); just kept the createClient() config blank and it connected.
I write my server file with node.js and has successfully test in my local , i install node.js and mongoDB plugin on my server , that is windows, but when i type server url instead of my ip in my android app I can't find server and get error server not found
Please help me
An overview of my setup:
A socket.io/node server is being hosted/ran on a computer in my local network.
An Ionic app is attempting to connect to the socket.io/node server to send/receive messages.
If I run the app in the browser with 'ionic serve', I am able to connect to the socket.io/node server successfully.
If I run the app in the emulator or on my device, I am only able to connect to the socket.io/node server if I add the -l (livereload) flag (ionic run android -l).
Originally, I hosted the node server on a heroku instance. I had no troubles connecting with this setup from browser, phone, or emulator. I had to switch to running the node server on a local computer so I have access to a local database.
Any ideas what is going on?
I fixed it by adding 'http://' to the beginning of the connection string.
Not sure why Ionic's livereload enabled me to connect without the 'http'
Im using Node.js 0.6.2 on Windows 7
I managed to get the dependencies solved on Win7 for socket io, now when i launch one of the example apps it doesnt throw any errors.
however, for the IP and listener it reports its listening on , when i launch that in the browser, the connection times out.
Any ideas?
I've tried setting app.listen to different ports and IP addresses, but no luck.
Just for reference, i've tried the famous "hello world" Node.js example which works fine.
Things i've already checked
Other services running on the same ports or same listener IP
Different IP addresses and ports
Firewall / Port blocking
Restarting of the machine
dependencies in node_modules
Different browsers
Telnetting to the listener port (which shows a response so the listener must be working?)
So this works for me (running msysGit and node.js, both latest versions; both Windows installers):
$ cd c:\msysgit\msysgit\cmd
$ git clone git://github.com/ry/node_chat.git
$ cd node_chat
$ "c:\progra~1\nodejs\node.exe" server.js
I can open 127.0.0.1:8001 now and run it. The fact that you have to cd into the directory is a bug in node_chat, same behavior is in OS/X.
I managed to solve this problem with some outside help.
I downloaded Node 0.6.3 which comes with NPM.
I created a test folder and then ran NPM Install socket.io express within the test folder and then tested the example app from the Socket IO website in the how-to-use section.
Socket IO emitted the events fine and it all seems to be working well. Thanks everyone for the help and guidance.