The Complete Strapi™ Course with Plugins and Deployment - Deployment Architectures: An Overview

This video tutorial guides viewers through deploying a project using Strappy, focusing on configuring it for production environments. It covers setting up a database, email plugin, and deploying Strappy as a Node JS server. The tutorial also explains setting up custom domains, using third-party media storage, and creating flexible infrastructure. Two architectural scenarios are explored: one with a combined admin and API server, and another with separate servers. The video emphasizes using environment variables for configuration flexibility.

What is the primary focus of the initial setup in deploying a Strappy project?

• Preparing Strappy for a production environment

• Configuring a custom domain

• Deploying the admin panel as a static site

• Setting up a third-party media storage

Which service is used for media file storage in the deployment process?

• Cloudinary

• Amazon S3

• Dropbox

• Local server storage

How is the admin panel deployed in the second architecture?

• As a plugin within the Strappy server

• As a microservice

• As a static site on a separate server

• As a dynamic site on the same server

What is the benefit of using environment variables in the deployment process?

• They reduce deployment time

• They improve server performance

• They enable configuration flexibility without code changes

• They allow for code changes without redeployment

Why is internal communication between the Node server and the Postgres database considered a good practice?

• It simplifies the deployment process

• It enhances security

• It reduces server load

• It improves database performance