Łukasz Szewczak lukaszewczak

Read Me

In order to access a server hosted within a vm (guest), for development purposes from the host OS, which is restricted to same origin / localhost only requests, I set up a siple nginx reverse proxy to forward my requests.

Steps

To install in a Windows VM, download and install nginx from the current, stable release; I installed to C:\nginx\
Edit the <install path>/conf/nginx.conf file with the marked changes in the file of the same name in this gist.
Start the nginx executable, located in your install path. There are service wrappers for Windows, or you can just kill the process to stop the nginx instance.

Commands for Windows

Here's how to save and load docker images:

Example scenario: To save a docker image from a docker repository and save it as a tar file locally.

Save the image as a tarball

docker save repositoryname:tag > repotag.tar

Zip the image

Docker - How to cleanup (unused) resources

Once in a while, you may need to cleanup resources (containers, volumes, images, networks) ...

delete volumes

// see: https://github.com/chadoe/docker-cleanup-volumes

$ docker volume rm $(docker volume ls -qf dangling=true)

$ docker volume ls -qf dangling=true | xargs -r docker volume rm

Free disk space when `/boot` is full (Ubuntu)

TL;DR

dpkg -l linux-image*
uname -r
sudo apt-get remove linux-image-2.6.32-{21,37,38,39,40,41,42,43,44}-server
sudo apt-get autoremove

Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.

Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.

Paths and URLs

On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation

From my Pluralsight course: https://app.pluralsight.com/library/courses/asynchronous-javascript-reasoning/table-of-contents

Weather http://plnkr.co/edit/ZOAaSdtnfvR6WwiuVZ6s
Avoid Blocking – Red Background http://plnkr.co/edit/z29VyH5BPvC4oc40EyOu
setTimeout Pyramid Challenge http://plnkr.co/edit/DGiHFQOQfnipCcpex2RH
Drag and Drop Red Box http://plnkr.co/edit/SmSpPS5ZgPvkgn8RE6y1
Timer onReady http://plnkr.co/edit/gafgKCrxnDIJ6YaG9Jpx
Timer measure http://plnkr.co/edit/kPOgzEuIvUmN4o6Jenem
Progress Number Crunching - Web Worker https://plnkr.co/edit/Yy7BOZU9sIa8EyrxJwGH
Event Listeners Are Synchronous http://plnkr.co/edit/mDvSHpF3HcTjtvltGmQn

	Secure sessions are easy, but it's not very well documented, so I'm changing that.
	Here's a recipe for secure sessions in Node.js when NginX is used as an SSL proxy:

	The desired configuration for using NginX as an SSL proxy is to offload SSL processing
	and to put a hardened web server in front of your Node.js application, like:

	[NODE.JS APP] <- HTTP -> [NginX] <- HTTPS -> [CLIENT]

	To do this, here's what you need to do:

	const { assert } = require('chai');

	function isError(e) {
	if (typeof e === 'string') {
	return Promise.reject(new Error(e));
	}
	return Promise.resolve(e);
	}

	'use strict';

	angular.module('guiApp')
	.service('Websocket', function Websocket($q, $rootScope, PubSub) {

	var Service = {}; // Object to return for the service
	var callbacks = {}; // Keep all pending requests here until they get responses
	var currentCallbackId = 0; // Create a unique callback ID to map requests to responses
	var ws = null; // Initialize our websocket variable
	var connectStatus = false; // Is the websocket connected?

	# Assuming an Ubuntu Docker image
	$ docker run -it <image> /bin/bash