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

Enhancing the basic React app

In the Installing NodeJS for frontend development section of Chapter 1, Setting Up Our System for Development, we used the create-react-app tool to create a standard React app, which we can now configure for our usage.

First, as we are using a frontend development server, we will need to proxy API requests to our backend by adding the following to frontend/package.json:

  "proxy": "http://localhost:5050"

The highlighted ellipsis represents the existing code; note the additional trailing comma that has been added.

Next, we’ll configure the import system so that we can use full paths with src as the root (i.e., src/components/Component) rather than, for example, ../components/Component. This makes the imported file easier to find as we can always relate the path to the src directory. It also matches the type of import paths we’ve used already in the backend. To do so, we need to...