Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Node.js Web Development

You're reading from   Node.js Web Development Server-side web development made easy with Node 14 using practical examples

Arrow left icon
Product type Paperback
Published in Jul 2020
Publisher Packt
ISBN-13 9781838987572
Length 760 pages
Edition 5th Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
David Herron David Herron
Author Profile Icon David Herron
David Herron
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Section 1: Introduction to Node.js
2. About Node.js FREE CHAPTER 3. Setting Up Node.js 4. Exploring Node.js Modules 5. HTTP Servers and Clients 6. Section 2: Developing the Express Application
7. Your First Express Application 8. Implementing the Mobile-First Paradigm 9. Data Storage and Retrieval 10. Authenticating Users with a Microservice 11. Dynamic Client/Server Interaction with Socket.IO 12. Section 3: Deployment
13. Deploying Node.js Applications to Linux Servers 14. Deploying Node.js Microservices with Docker 15. Deploying a Docker Swarm to AWS EC2 with Terraform 16. Unit Testing and Functional Testing 17. Security in Node.js Applications 18. Other Books You May Enjoy

Using Docker Swarm to manage test infrastructure

One advantage Docker gives is the ability to install the production environment on our laptop. In Chapter 12, Deploying Docker Swarm to AWS EC2 Using Terraform, we converted a Docker setup that ran on our laptop so that it could be deployed on real cloud hosting infrastructure. That relied on converting a Docker Compose file into a Docker Stack file, along with customization for the environment we built on AWS EC2 instances.

In this section, we'll repurpose the Stack file as test infrastructure deployed to a Docker Swarm. One approach is to simply run the same deployment, to AWS EC2, and substitute new values for the var.project_name and var.vpc_name variables. In other words, the EC2 infrastructure could be deployed this way:

$ terraform apply --var project_name=notes-test --var vpc_name=notes-test-vpc

This would deploy a second VPC with a different name that's explicitly for test execution and that would not disturb the production...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image