Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Node.js Web Development

You're reading from  Mastering Node.js Web Development

Product type Book
Published in Jun 2024
Publisher Packt
ISBN-13 9781804615072
Pages 778 pages
Edition 1st Edition
Languages
Author (1):
Adam Freeman Adam Freeman
Profile icon Adam Freeman
Toc

Table of Contents (26) Chapters close

1. Putting Node.js in Context
2. Getting Ready 3. Working with the Node.js Tools 4. JavaScript and TypeScript Primer 5. Understanding Node.js Concurrency 6. Handling HTTP Requests 7. Using Node.js Streams 8. Using Bundles and Content Security 9. Unit Testing and Debugging 10. Node.js in Detail
11. Creating the Example Project 12. Using HTML Templates 13. Handling Form Data 14. Using Databases 15. Using Sessions 16. Creating RESTful Web Services 17. Authenticating and Authorizing Requests 18. SportsStore
19. SportsStore: A Real Application 20. SportsStore: Navigation and Cart 21. SportsStore: Orders and Validation 22. SportsStore: Authentication 23. SportsStore: Administration 24. SportsStore: Deployment 25. Other Books You May Enjoy
26. Index

Toggling the application environment

The SportsStore application will be deployed in a Docker container, which will be configured to set the application environment to production. It is helpful to be able to switch to the production environment outside of the container in order to prepare the application for deployment. One way to do this is to set an environment variable named NODE_ENV using the command prompt used to start Node.js, but that can be difficult to do consistently when there are multiple developers, each with their own command prompt or shell preferences, each of which deals with environment variables in its own way. A more reliable way is to rely on the dotenv package, which reads environment variables from files.

Add a file named overrides.env to the sportsstore folder, with the content shown in Listing 21.7. This is a temporary file, just to confirm that the application behaves as it should before it is prepared for deployment.

Listing 21.7: The contents...

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 €14.99/month. Cancel anytime