Upgrading Strapi

Strapi Migration

I started this journey with Strapi early on with v3.0.0 Beta 18. I had to migrate multiple times to get it running correctly. I do like the new way they handle environments with the .env file much better. However, updating is much to be desired. With multiple issues from reformatting config folder and file structure to crippling plugins and extensions. I would recommend, if you have not done much, to just start new and rebuild everything locally.

I did however, went through all migration steps. Thankfully they do have a guide at https://strapi.io/documentation/v3.x/migration-guide/#guides. This guide seems to have most of what you need, but is not easy for non-developers. Granted Strapi is mainly focused at developers. However, it would be nice to migrate into the territory of regular consumers to install and use this software as it is pretty powerful.

Features

• Multi-databases support
• GraphQL or RESTful
• Webhooks
• Auto-generated documentation
• Authentication & Permissions
• Customizable API
• Media Library
• Built-in sorting and filtering
• User-friendly interface
• JWT authentication
• Built-in Emailing

Conclusion

Strapi is still a great Headless CMS! The website you see this article on is was built with Strapi using GraphQL. If you don’t mind the migration process which could take awhile, depending on your knowledge with Node.