Tired of fighting Docker when you should be building Node.js in your container?

Be Insanely Productive With Docker

Write Code, Run Your Favorite Build Tools, and Never Worry About Memorizing Cryptic Commands, Again.

With the Docker Recipes for Node.js Development eBook, you'll have access to simple solutions for common problems – ready for you to use – instantly!

Don't Sweat The Details

Software development is moving quickly toward scalability through the use of many small applications with many instances each.

Tools like Docker help you encapsulate these apps and microservices. With it, you can keep application dependencies and configuration separate.

This means you may never have to face the “Work on My Machine” problem, again.

Docker is amazing – no doubt about that.

But, let's face it… The mental overhead it introduces is not insignificant.

With new code, new configuration, and new runtime environments for your development process, it can be overwhelming for even the most seasoned of developers.

Get back to building your application

With the upcoming Docker Recipes for Node.js Development ebook, you can stop worrying about memorizing configuration that you'll only touch a few times in a project's lifetime.

You don't need to waste precious brain power, wondering if you can use your favorite build tools, debugger or editor.

Instead, you can get back to solving the business needs, knowing that yes, you can continue to use your favorite tools and techniques.

Don't worry about re-typing code from a book

This ebook will give you the code and configuration to solve to the most common problems that you're facing when developing Node.js apps with Docker.

And you'll have copy-and-paste access to the source files and command-line examples, letting you quickly implement the solutions you need.

For example:

• Are you waiting more than a few seconds for npm install to finish? Recipe #4 will show you how to speed up npm when using a volume mount in a container. Cut the install time in half, and get back to coding and running your app.
• Is your container exiting before you can see the application error? Recipe #6 will show you how to start your application with the debugger already attached. Now you can find and fix thee errors that are preventing your app from starting!
• Having problems figuring out what's causing a certain bug? Recipe #7 will show you how to step into a Docker container and attach a debugger to already running code. Keep the application state intact, and find the error immediately.
• Want to use your favorite debugger, instead of the command-line? Recipe #8 gives you both Docker container and Visual Studio Code configuration, for debugging. You'll save hours of time and headache, by using your preferred tools!

The content goes far beyond just the recipe goals, as well. You'll get insight into how each step in the recipe is used, giving you additional tools to use as you see fit.

• Need to run a command other than the one your image specifies? Learn how to create a new container instance, supplying a different command to execute
• Want to run your tool in an existing container instance? Run any arbitrary tools or commands you want, in a running container.
• Looking for the “Process ID” of your running app? List all running processes, and get the PID you need.

The early release version of Docker Recipes for Node.js Development includes these recipes with additional detail, as well. It also promises to deliver a comprehensive set of Docker related code and configuration, when complete.

Docker Recipes for Node.js Development: Early Release

This book is not yet complete, but I am making it available starting now so that you can take advantage of the wealth of information already contained within.

When you purchase the early release eBook you'll get instant access to the content mentioned above and to all updates to the book as progress happens. You'll also receive the complete code for the book, as it becomes available. This will ensure you have a solid place from which you can start creating your own Docker projects for Node.js.

Who Should Read This Book

If you’re new to Docker, this book is not for you. I would recommend you start with the WatchMeCode Guide to Learning Docker if you need to learn Docker from the ground, up.

If you’re looking for a resource to show you the basics of configuring Docker to run a Node.js application, this book is not for you, either. The WatchMeCode Guide to Building Node.js Apps in Docker will show you how to configure a Docker container, run Node.js, get Express.js installed with npm install and more.

However, if you’re already using Docker, already know how to configure a basic Node.js and Express.js application in a container, but you find yourself running into difficult situations with debugging, reloading code, and running your tool set within Docker, this book is for you.

Within these recipes (chapters), you’ll find answers to the problems that plague developers beyond the basics of standing up a Docker container.

You’ll learn how to combine tools, command-line options, Dockerfile configuration items and more, into solutions for the unique problems that Node.js and JavaScript developers face when building applications within a Docker container. And you'll learn from experience in creating real-world Docker solutions for Node.js applications - not some theoretical application that could be useful somewhere.

A Solution For Developers, From A Developer

Dear developer, struggling to work with Node.js in Docker,

My name is Derick Bailey.

I'm a JavaScript and Node.js developer, like you. I write code and build applications, struggling to deal with production issues vs development needs.

I’m also a speaker and a published author. I've been writing code since 1988, have been a prolific blogger since 2004 and have been delivering world-class training to developers like yourself, through on-site classes, screencasts, ebooks and more.

I've spent a lifetime (more than 20 years) building software for leading financial organizations and airlines, the U.S. government, and more. I've created critical systems for large healthcare organizations, saving them millions of dollars a year. I've helped small-town, independently owned businesses improve their bottom line with simple software solutions and complex process automation.

And I've helped countless developers through sites like Stack Overflow, writing sample code for Microsoft's MSDN library, by publishing dozens of leading open source projects, including the most widely used add-on for Backbone.js (Marionette.js) and more.

Through my career, I have seen technologies come and go, frameworks grow and wither, and tools spring to life and die in abandon. I've also found that the core principles and patterns of software development are timeless – never dying, only changing implementation and form.

But one thing I don't see very often, is a technology so fundamentally better than what you had done in the past, that you wonder how we ever worked without it.

Docker is that level of technology.

Like the PC revolution of the 90's, the virtual machine revolution of early 2000's, or the cloud and cloud-scale, Docker is a tool set that encapsulate decades of best practices and solid fundamentals in a manner that is revolutionizing the way we work with software – both in development and in production.

But a new and growing technology is bound to have learning curves, rough edges and scenarios that are not yet developed into a collective best-practice. Docker is no exception. It can be difficult to learn and work around common problems.

Now, however, with my own experience in real-world development and debugging efforts, I want to show you just how smooth Docker can be with Node.js. I want to show you the tools, tricks and techniques that have made Docker a permanent – and simple – part of my development efforts.

With that, I present to you Docker Recipes for Node.js Development.

– Derick Bailey

– Creator of WatchMeCode.net

What Developers Say About Derick's Docker Training

“Thank you! Best docker resource I come across!” – sd

“[the Docker cheatsheet] was useful, even though I've been working with docker a while. Thanks for sharing that.” – Oliver A

“Thank you so much for this cheatsheet – it help in my start learning of docker.” – Evgeny S.

“Yes. It's very good table to remember the commands. Very useful! Cheers.” – Arthur A.

“Thank you for the tips and advice. Can't wait for more videos! keep it going! Thank you” – Fabio F.

“Thanks Derick! I liked all the docker cheatsheets with the graphic and short description it is perfect!” – S. Thomas

The security defaults of Docker are established to get you up and running ("just work") quickly, rather than being the most secure. There are many default configurations that can be improved upon. This book will help you do just that.

Covering the risks and countermeasures of Docker security, based on Kim's own personal experience with Docker environments and discussions with Docker Security Team Lead Diogo Mónica.

Discounts: If you would like a discount, please email me, letting me know how much you would be willing to pay. The less you pay, the more I may consult with you about your reader experience, etc.

Homepage: binarymist.io/publication/docker-security/

Blog Post with details of what's inside this book: binarymist.io/blog/2018/03/31/docker-security/

Authors Other Books: binarymist.io/publication/kims-selected-publications/

What Others Say About Docker Security: binarymist.io/blog/2018/03/31/docker-security/#comments

"The Docker security book saved me hours of time researching this myself. I was able to harden the security of our Docker images without wasting any time." - CR

Authors Homepage: binarymist.io