Deploy a New Strapi App
Strapi is an open-source headless CMS built with NodeJS. Using Strapi you can easily design and publish the content consumed by your apps via API. Strapi provides a great admin UI portal where you can design your data models, create and manage content.
The benefits of using Microtica for your Strapi projects are the simplicity of setup and low maintenance while having the infrastructure on your own AWS account. We are following the GitOps and declarative infrastructure approach for stable, more reliable, and predictable deployments.
With this approach, Strapi can coexist with your existing AWS infrastructure and you always have the flexibility to extend this setup with additional cloud resources.
Microtica uses Strapi v4 as a default version for the Strapi Serverless template.
The Strapi infrastructure will be provisioned on your own AWS account. You retain full control over your infrastructure and data while getting all the benefits of infrastructure automation.
Microtica provides a built-in template that provisions the necessary infrastructure to run Strapi on your AWS account in a scalable, secure, and reliable way with zero downtime deployment.
To deploy the infrastructure you need to select the Strapi Serverless Template.
Follow the steps in the template to deploy the Strapi app on your AWS account.
As a first step, you need to connect a Git account (GitHub, Bitbucket, or GitLab). Microtica defines a repository name by default for each template, but you can change it. If you already have a Git account connected to Microtica, you can choose it from the list. We will create a new repository on your account with the provided name, and every Git push will be deployed automatically in Microtica.
The second step is to configure the environment variables for this template. Variables provide a way to customize a template to meet your requirements. For example, here is where you configure the scaling parameters for your Strapi app. You can scale your app vertically and horizontally. For vertical scaling, update the CPU and Memory configuration in this section. For horizontal scaling, update the number of desired replicas in the same section.
In this section you can also choose the database client - sqlite is the default option.
You can update the configuration later as well.
After configuring the template, you will need to select an environment where the template will reside. Environments are a great way to separate your development and production applications. If you need to create a new environment, you can enter the environment name and description and click the Select button. You can also choose an existing environment if you have created one previously.
Next, you need to configure the target AWS account where your Strapi infrastructure will be provisioned. Here is a quick guide on How to Connect your AWS account.
Once your AWS account is connected and configured in the environment, click on the Deploy button to trigger the deployment.
It takes up to 10 mins to create a live Strapi environment.
You can follow the pipeline logs inline, and monitor your deployment in real-time.
Once the template deployment finishes, you can find the access URL in Environment > Infrastructure > Strapi (Strapi is the AppName we provided in the template configuration step), under Resource outputs, the AccessUrl parameter. Copy-paste it in the browser to see your Strapi Demo app.