Book Image

A Blueprint for Production-Ready Web Applications

By : Dr. Philip Jones
Book Image

A Blueprint for Production-Ready Web Applications

By: 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)
1
Part 1 Setting Up Our System
3
Part 2 Building a To-Do App
8
Part 3 Releasing a Production-Ready App

Securing and Packaging the App

In the previous chapter, we deployed our app to tozo.dev, allowing users to use our web app via a browser on any device, and added monitoring so that we know when things go wrong.

In this chapter, we will focus on how we can keep our app secure, both in terms of the code we use and the methods users use to authenticate. We’ll also package our app so that users can use our app via the app stores.

It is important to view the app’s security as a continual process, whereby the practices and packages must be continually updated and improved. In this chapter, I’ll demonstrate my process for managing package updates, which you can adopt and improve upon. We’ll also adopt current best practices to secure the app.

We’ll also make a major change to support multifactor authentication. While this will allow users to opt-in for greater security, it will also show how to make large changes to the app; specifically, it will...