Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying A Blueprint for Production-Ready Web Applications
  • Table Of Contents Toc
  • Feedback & Rating feedback
A Blueprint for Production-Ready Web Applications

A Blueprint for Production-Ready Web Applications

By : Philip Jones, Dr. Philip Jones
5 (7)
close
close
A Blueprint for Production-Ready Web Applications

A Blueprint for Production-Ready Web Applications

5 (7)
By: Philip Jones, Dr. Philip Jones

Overview of this book

A Blueprint for Production-Ready Web Applications will help you expand upon your coding knowledge and teach you how to create a complete web application. Unlike other guides that focus solely on a singular technology or process, this book shows you how to combine different technologies and processes as needed to meet industry standards. You’ll begin by learning how to set up your development environment, and use Quart and React to create the backend and frontend, respectively. This book then helps you get to grips with managing and validating accounts, structuring relational tables, and creating forms to manage data. As you progress through the chapters, you’ll gain a comprehensive understanding of web application development by creating a to-do app, which can be used as a base for your future projects. Finally, you’ll find out how to deploy and monitor your application, along with discovering advanced concepts such as managing database migrations and adding multifactor authentication. By the end of this web development book, you’ll be able to apply the lessons and industry best practices that you’ve learned to both your personal and work projects, allowing you to further develop your coding portfolio.
Table of Contents (13 chapters)
close
close
1
Part 1 Setting Up Our System
3
Part 2 Building a To-Do App
8
Part 3 Releasing a Production-Ready App

Making the app production-ready

As our production infrastructure will run containers, we need to containerize our app. To do so, we’ll need to decide how to serve the frontend and backend, and how to build the container image.

Serving the frontend

So far in development, we’ve used npm run start to run a server that serves the frontend code. This is called server-side rendering (SSR), and we could continue to do this in production. However, it is much easier to utilize client-side rendering (CSR), as this does not require a dedicated frontend server. CSR works by building a bundle of frontend files that can be served by any server (rather than a dedicated frontend server), and we’ll use the backend server.

To build the frontend bundle, we can use the npm run build command. This command creates a single HTML file (frontend/build/index.html) and multiple static files (css, js, and media) in the following structure:

tozo
└── frontend...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY