## Tips & tricks

Setup an alias to start Node container and map the current folder for quick isolated Linux environment.
Add to `~/.alias` file

```
# Creates Node container with mapped current folder and runs Bash shell
alias node-box='docker run -v $PWD:/src -w /src -u node -it node /bin/bash'
```

## Additional information

* [Dockerizing a Node.js web app](https://nodejs.org/en/docs/guides/nodejs-docker-webapp/)
* [NodeUp Docker podcast episode](http://nodeup.com/ninetyeight)
* [Node Dockerhub images](https://hub.docker.com/_/node/) - list of Docker images with different Node versions
* [Docker cheat sheet](https://github.com/wsargent/docker-cheat-sheet)
* [fuge](https://github.com/apparatus/fuge) - Node microservices and sites with nice development workflow
  - [Microservices with fuge](https://glebbahmutov.com/blog/microservices-with-fuge/) - my blog post showing local development workflow
* [Run Node in a docker container with file access](https://gist.github.com/bahmutov/448f73b49914d1981643)
* If you have multiple Docker files, you can pick the one to use during build `docker build -f <name> .`
* Good video from NodeSource [Need to Node: Getting Started with Node.js, Docker and Kubernetes](https://vimeo.com/171803492)
* You can run very simple process for managing system signals inside the docker container
  and that can start your actual process. [yelp/dumb-init](https://github.com/yelp/dumb-init)
* [8 Protips to Start Killing It When Dockerizing Node.js](https://nodesource.com/blog/8-protips-to-start-killing-it-when-dockerizing-node-js/) includes how to make separate user, caching, etc.