Render

  1. Fork Flowise Official Repository

  2. Visit your github profile to assure you have successfully made a fork

  3. Sign in to Render

  4. Click New +

  1. Select Web Service

  1. Connect Your GitHub Account

  2. Select your forked Flowise repo and click Connect

  1. Fill in your preferred Name and Region.

  2. Select Docker as your Runtime

  1. Select an Instance

  1. (Optional) Add app level authorization, click Advanced and add Environment Variable

  • FLOWISE_USERNAME

  • FLOWISE_PASSWORD

Add NODE_VERSION with value 18.18.1 as the node version to run the instance.

There are list of env variables you can configure. Refer to Environment Variables

  1. Click Create Web Service

  1. Navigate to the deployed URL and that's it 🚀🚀

Persistent Disk

The default filesystem for services running on Render is ephemeral. Flowise data isn’t persisted across deploys and restarts. To solve this issue, we can use Render Disk.

  1. On the left hand side bar, click Disks

  2. Name your disk, and specify the Mount Path to /opt/render/.flowise

  1. Click the Environment section, and add these new environment variables:

  • DATABASE_PATH - /opt/render/.flowise

  • APIKEY_PATH - /opt/render/.flowise

  • LOG_PATH - /opt/render/.flowise/logs

  • SECRETKEY_PATH - /opt/render/.flowise

  • BLOB_STORAGE_PATH - /opt/render/.flowise/storage

  1. Click Manual Deploy then select Clear build cache & deploy

  1. Now try creating a flow and save it in Flowise. Then try restarting service or redeploy, you should still be able to see the flow you have saved previously.

Watch how to deploy to Render

PreviousDeploymentNextRailway

Last updated