Strapi Gatsby Tutorial #6 - Deploying Strapi to Render

We recap our current architecture and notice that running Strapi and Gatsby locally can be an issue for other users that want to edit or add new content because they won't have access to our local machine and source code. To solve this we will be deploying Strapi with Render: https://render.com/

GitHub link: https://github.com/GideonNeedleman/strapi-gatsby-youtube

Strapi is a headless CMS that enables you to easily author content and expose it through an API. The flexibility of Strapi allows you to choose any frontend option and seamlessly query the API to retrieve your content. Gatsby is a React-based Static Site Generator that can process a diverse range of content through its GraphQL data layer. By leveraging the Strapi API, Gatsby transforms the content into HTML pages to create a dynamic and responsive experience.

This video goes over the steps of deploying Strapi onto Render, including connecting your GitHub repository, setting up the correct build and start commands and entering the necessary .env variables.

It's not too difficult, but there is an issue we notice once deployed; all of our previously stored content is missing! The content types are present because they are stored in the Strapi code that's cloned from the repo, but the actual content is located in a SQLite database that's stored locally on our development computer, not on Render. We will fix this problem in our next video.

Timestamps
00:00 Recap current architecture
03:18 Log into Render.com
04:09 Web Service Settings
06:45 Deployed Strapi Server

Видео Strapi Gatsby Tutorial #6 - Deploying Strapi to Render канала Learning with Gideon