Difference between revisions of "Node"
| Line 14: | Line 14: | ||
==[http://openmymind.net/2012/2/3/Node-Require-and-Exports/ require, exports and module.exports]== | |||
====[http://stackoverflow.com/questions/5062614/how-to-decide-when-to-use-node-js?rq=1 when to use node]==== | ====[http://stackoverflow.com/questions/5062614/how-to-decide-when-to-use-node-js?rq=1 when to use node]==== | ||
Latest revision as of 12:35, 22 March 2016
websockets
http://stackoverflow.com/questions/13546424/how-to-wait-for-a-websockets-readystate-to-change\
http://stackoverflow.com/questions/17301269/can-websocket-addresses-carry-parameters
http://stackoverflow.com/questions/25904478/send-extra-information-on-websocket-connection-creation
https://github.com/einaros/ws/blob/master/lib/WebSocket.js#L272
http://gonzalo123.com/2014/08/25/playing-with-websockets-angularjs-and-socket-io/
http://g00glen00b.be/spring-angular-sockjs/
moving current nvm version to /usr/local
n=$(which node);n=${n%/bin/node}; chmod -R 755 $n/bin/*; sudo cp -r $n/{bin,lib,share} /usr/local
root@SBSiniz:~# sudo -s root@SBSiniz:~# which node /usr/local/bin/node
token authentication
http://www.kdelemme.com/2014/03/09/authentication-with-angularjs-and-a-node-js-rest-api/
forever
using a json file is flaky, instead in /root/forgone.sh
#!/bin/sh forever stopall sleep 2 fuser -KILL -k -n tcp 3002 forever --uid tokauth -a start /home/services/token-auth-server/server.js sleep 2 fuser -KILL -k -n tcp 3009 forever --uid bogged -a start /home/boggedbus/public_html/boggedbus/server/app.js sleep 2 fuser -KILL -k -n tcp 1883 # mqtt fuser -KILL -k -n tcp 3332 # express fuser -KILL -k -n tcp 3333 # wss forever --uid geniot -a start /home/services/geniot/lib/index.js sleep 2 fuser -KILL -k -n tcp 1642 forever --uid hellossl -a start /home/services/hello/hello.js sleep 2 forever list
and put it in @reboot of /var/spool/cron/crontab/root
@reboot /root/forgone.sh # m h dom mon dow command 0 2 * * * cd /usr/local/lib/tm/scripts; ./backup.sh 0 3 * * * find /var/backups/s3/*.gz -ctime +5 -type f -print | xargs rm -f 30 3 * * * rsync -avuz --exclude-from=/root/rsync_exclude.txt / root@iotup.stream:/ 30 04 25 Feb,Apr,Jun,Aug,Oct,Dec * /usr/bin/letsencrypt renew >> /var/log/le-renew.log 35 04 25 Feb,Apr,Jun,Aug,Oct,Dec * /bin/systemctl reload nginx
running servers info can be seen in /root/appsServers2start.json. You stop them and restart them all like this
forever stopall forever start ./appsServers2start.json
- /root/.forever/config.json has configuration for forever
- log files are in /root/.forever
/root/appsServers2start.json
[
{
//bogged down bus
"uid": "bogged",
"append": true,
"watch": true,
"script": "app.js",
"sourceDir": "/home/boggedbus/public_html/boggedbus/server"
},
{
//token-auth-server
"uid": "auth",
"append": true,
"watch": true,
"script": "server.js",
"sourceDir": "/var/www/token-auth-server"
}
]
forever start server2.js forever stop server2.js forever list info: Forever processes running data: uid command script forever pid logfile uptime data: [0] DykF /root/.nvm/v0.10.25/bin/node server2.js 28939 28944 /root/.forever/DykF.log 1:1:2:21.834
ps -Al kill -KILL pid
tail -f /root/.forever/DykF.log
finding port of address already in use
$ sudo netstat -nlp | grep 80 tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 125004/nginx
or
# sudo lsof -i :25 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME exim4 2799 Debian-exim 3u IPv4 6645 0t0 TCP localhost:smtp (LISTEN) exim4 2799 Debian-exim 4u IPv6 6646 0t0 TCP localhost:smtp (LISTEN)
require, exports and module.exports
when to use node
node cors
Nginx
quick up on server
letsencrypt
/root/README16.04.md in sitebuilt.net has the docs on letsencrypt commands that have been run
letsencrypt certonly -a webroot --webroot-path=/home/tryit/public_html -d tryit.sitebuilt.net
letsencrypt certonly -a webroot --webroot-path=/var/www/html -d sitebuilt.net -d tryit.sitebuilt.net
- put your code in some directory
- modify sites-available
- nginx -s reload
forward proxy
http://blog.abarbanell.de/raspberry/2016/01/09/arduino-nginx/
me: Doesn't the nginx proxy need crt's and key's? Will it just work like a browser and encrypt deencrypt automagically?
Tobias Abarbanell Hi Tim, in this process the nginx is a server receiving requests over http and then on the encrypted side it is a client, so it does not need to have certificates.
If you want traffic coming the other direction, from the outside to your devices you would need certificates on the nginx and I would recommend using letsencrypt (https://letsencrypt.org) for this purpose.
Hi Tobias,
Thanks. BTW I think I had already solved the "traffic coming the other direction" problem. I've been loving mqtt as a lightweight protocol to have my esp8266's converse with the world. On my outside nginx vps I am running mosca inside a node app. Mosca is a broker. Devices an clients subscribe and publish to topics and mosca routes them. So my guess is having the pi handle the tls stuff, I'd be able to get data in too.
Meanwhile if I've discovered (after lots of error and error) if I limit the ciphers and keysize I can get TLSv1.1 working rather reliably straight from the esp8266. I haven't dropped a handshake in an hour now. Having WiFiClientSecure just use a fingerprint of the certificate (512 bit certificate) it verifies and accepts the cert. Instead of letting node run with its TLSv1.2 super secure big bloated ciphers I start node like this: node --tls-cipher-list='TLS_RSA_WITH_AES_128_CBC_SHA:RC4-MD5' lib/index.js. Ok so I won't win any awards for TLS and can't use AWS IOT(req TLSv1.2 and big ciphers), but the sensors and relays all over my house and yard will be very hard to mess with nonetheless.
Mosca sends mqtt to web clients using websockets. That's the final piece of the puzzle for me to tackle, wss for apache(windows testmachine) and nginx(ubuntu16.04vps)
Your idea is brilliant and I can't wait to try it on a pi.
tcp proxy
http://yaoweibin.github.io/nginx_tcp_proxy_module/
https://serversforhackers.com/compiling-third-party-modules-into-nginx
https://github.com/imZack/docker-nginx-tcp-proxy
wget http://github.com/yaoweibin/nginx_tcp_proxy_module/tarball/master tar -xvf master cd yaoweibin-nginx_tcp_proxy_module-7d70702 cp -R yaoweibin-nginx_tcp_proxy_module-7d70702 /opt sudo apt-get install -y dpkg-dev sudo apt-get install libpcre++-dev sudo mkdir /opt/rebuildnginx cd /opt/rebuildnginx sudo apt-get source nginx cd /opt/rebuildnginx/nginx-1.10.0/ patch -p1 < /opt/yaoweibin-nginx_tcp_proxy_module-7d70702/tcp.patch ./configure --add-module=/opt/yaoweibin-nginx_tcp_proxy_module-7d70702 make make install
that puts it in the middle of nowhere with no systenctl or usr/sbinin
in ls -al /etc/systemd/system/multi-user.target.wants/ there should be nginx.service -> /lib/systemd/system/nginx.service and there should be the file nginx.service which looks like this
since you meessed with a systemd file
systemctl daemon-reload
# Stop dance for nginx # ======================= # # ExecStop sends SIGSTOP (graceful stop) to the nginx process. # If, after 5s (--retry QUIT/5) nginx is still running, systemd takes control # and sends SIGTERM (fast shutdown) to the main process. # After another 5s (TimeoutStopSec=5), and if nginx is alive, systemd sends # SIGKILL to all the remaining processes in the process group (KillMode=mixed). # # nginx signals reference doc: # http://nginx.org/en/docs/control.html # [Unit] Description=A high performance web server and a reverse proxy server After=network.target [Service] Type=forking PIDFile=/run/nginx.pid ExecStartPre=/usr/sbin/nginx -t -q -g 'daemon on; master_process on;' ExecStart=/usr/sbin/nginx -g 'daemon on; master_process on;' ExecReload=/usr/sbin/nginx -g 'daemon on; master_process on;' -s reload ExecStop=-/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid TimeoutStopSec=5 KillMode=mixed [Install] WantedBy=multi-user.target
and since nginx isn't there you need
ln -s /usr/local/nginx/sbin/nginx /usr/sbin/
websocket reverse proxy
https://www.nginx.com/blog/websocket-nginx/
restart nginx
nginx -s reload
allow directory reads
edit
/etc/nginx/sites-available/default
add autoindex on here
location / {
try_files $uri $uri/ =404;
autoindex on;
}
restart
nginx -s reload
install
https://anturis.com/blog/nginx-vs-apache/
SSL
sudo ln -s /etc/nginx/sites-available/example.com /etc/nginx/sites-enabled/example.com sudo ln -s /etc/nginx/sites-available/cascada.parleyvale.com /etc/nginx/sites-enabled/cascada.parleyvale.com
server {
listen 443;
server_name stuff2get.parleyvale.com;
root /home/stuff2get/www;
index index.html index.htm;
ssl on;
ssl_certificate /etc/nginx/ssl/stuff2get.parleyvale.com/server.crt;
ssl_certificate_key /etc/nginx/ssl/stuff2get.parleyvale.com/server.key;
}
server {
listen 443;
server_name stuff2get.parleyvale.com;
location / {
proxy_pass http://localhost:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
ssl on;
ssl_certificate /etc/nginx/ssl/stuff2get.parleyvale.com/server.crt;
ssl_certificate_key /etc/nginx/ssl/stuff2get.parleyvale.com/server.key;
}
express
http://expressjs-book.com/forums/topic/express-js-sessions-a-detailed-tutorial/
http://stackoverflow.com/questions/18708428/how-to-do-authentication-with-node-js-and-mean-stack
win7
https://github.com/joyent/node/wiki/Installation
64bit version: http://nodejs.org/dist/latest/x64/node.exe
- is in /wamp/bin/node
- installed npm there too
- added it to path
- to test: from git bash> node hellonode.js starts server, see page at http://127.0.0.1:8124/
homebuntu
http://ariejan.net/2011/10/24/installing-node-js-and-npm-on-ubuntu-debian/
