# Render One-Click
One-click installation guides are not updated by the Strapi documentation team anymore. Community contributions (opens new window) are most welcome.
The following documentation will guide you through the one-click creation of a new Strapi project hosted on Render (opens new window).
Render is a cloud provider with persistent disks and managed PostgreSQL databases, that offers multiple different ways to store content.
A Render account is necessary to follow this installation guide. Please visit the Render dashboard (opens new window) to create an account if you do not already have one.
# Creating a Strapi project
Render maintains 3 "Strapi on Render" example repositories (see Render's Deploy Strapi guide (opens new window) for more information), which differ based on the databased used and the storage location of uploaded media library files:
- Strapi with SQLite and uploads on disk (opens new window)
- Strapi with PostgreSQL and uploads on Cloudinary (opens new window)
- Strapi with PostgreSQL and uploads on disk (opens new window)
Once the choice between the 3 repositories is made:
- Fork the repository on GitHub.
- In the README file of your forked repository, click the Deploy on Render button.
- Make sure you granted Render the permission to access your forked repository.
When using Cloudinary, you will be prompted to enter your account credentials as environment variables. Render encrypts environment variables and stores them securely.
# Running Strapi
Your Strapi application on Render will be running in production mode, with
NODE_ENV=production. However, to add or edit content-types via the admin panel (see Content-Type Builder (opens new window) documentation), Strapi must be running locally in development mode.
To run Strapi locally:
- Clone the forked repository to your local machine.
- Still in terminal, access the repository using the
- Run the
yarn install && yarn developcommand to run your Strapi project.
When committing changes and pushing them to your remote repository, Render will automatically deploy these changes to your production application. A typical workflow (opens new window) would also include a staging environment for testing.