π Deployed Flowise twice to render.com: once using the free instance and once using the paid starter instance
π» Connected both instances to LangSmith for chat flow
π₯π Obtained LangSmith configuration data and API key
π Deploy Flowise to render.com
π Connect Flowise to LangSmith
π Choose region and runtime for the web service
βοΈ Set up environment variables for chat flows
Deploying Flowise to render.com and connecting to LangSmith
Creating a web service on render.com and logging in with Flowise credentials
Adding a conversation chain template, configuring the OpenAI API, and saving the flow
β The connection to LangSmith was successfully established and data is being sent in the background.
π‘ After a period of inactivity, the chat flow on the free instance will be lost, so it is recommended to upgrade to a paid instance on render.com.
π To maintain the configuration and environment variables, it is suggested to download the Flowise Repository and store the variables in the render instance.
To deploy Flowise on render.com and connect to LangSmith, we need to add the Flowise username, password, and language data as environment variables.
We can attach a disk to the instance to store data, and increase its size later if needed.
To ensure Flowise data is stored on the disk and not on the running instance, we need to add specific environment variables.
π§ Manually deploy Flowise and clear build cache on render.com.
π¬ Adjust components and assign Open AI key to create a chat flow on render.com.
π Test chat flow and obtain the answer about the capital of Canada from Chat GPT.
π Check associated projects on LangSmith and explore new run information.
π» Access and explore projects and data on LangSmith.
π Switching to render.com removes the chat flow from the free instance, but it remains in the paid version.
π‘ Render.com is a convenient solution for deploying Flowise chat flows.
π Chat flows deployed on render.com can be connected to LangSmith.