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

Sending production emails

In the Sending emails section of Chapter 2, Creating a Reusable Backend with Quart, we configured our app to send emails via Postmark if a POSTMARK_TOKEN configuration value was present. We can now set up production so that there is a POSTMARK_TOKEN in the app’s configuration.

To do so, we first need approval from Postmark; this is done to ensure that we don’t intend to misuse their service. As we are using Postmark for transactional emails (e.g., password reset tokens), we should get permission. This is gained via the request approval button or by talking directly to their support.

With permission granted, we can add the relevant DNS records to prove to Postmark that we control the domain. These are available from your Postmark account and should be added as follows to infrastructure/

resource "gandi_livedns_record" "tozo_dev_DKIM" {
  zone   =