Porter is a Platform as a Service (PaaS) that runs in your own cloud provider. It brings the convenience of platforms like Heroku, Netlify, and Vercel into a cloud provider of your choice. Under the hood, Porter runs on top of a Kubernetes cluster but abstracts away its complexity to the extent that you don't even have to know that it's running on Kubernetes.
This is a quick guide on how to deploy Strapi to a Kubernetes cluster in AWS/GCP/DO using Porter. This guide uses PostgresDB by default - to customize your database settings, modify the files in
/app/config/env/production in the example repository.
- Create an account on Porter.
- One-click provision a Kubernetes cluster in a cloud provider of your choice, or connect an existing cluster if you have one already.
- Fork this repository.
- From the Launch tab, navigate to Web Service > Deploy from Git Repository. Then select the forked repository and
Dockerfilein the root directory.
- Configure the port to
1337and set environment variable to
NODE_ENV=production. Depending on your database settings, you might want to add more environment variables. More on this in the section below.
- Set the assigned resources to Strapi's recommended settings (i.e. 2048Mi RAM, 1000 CPU), then hit deploy!
- Strapi instance deployed through Porter connects to a PostgresDB by default. You can connect Strapi instance deployed on Porter to any external database, but it is also possible to connect to a database that is deployed on Porter. Follow this guide to deploy a PostgresDB instance to your cluster in one click.
- After the database has been deployed, navigate to the Environment Variables tab of your deployed Strapi instance. Configure the following environment variables:
NODE_ENV=production DATABASE_HOST= DATABASE_PORT=5432 DATABASE_NAME= DATABASE_USERNAME= DATABASE_PASSWORD=
To determine what the correct environment variables are in order to connect to the deployed database, see this guide.
To develop, clone the example repository to your local environment and run
npm install && npm run develop; from the
app directory. Porter will automatically handle CI/CD and propagate your changes to production on every push to the repository.
Join the Porter Discord community if you have any questions or need help.