mirror of
https://github.com/hanzoai/flow.git
synced 2026-10-17 01:29:18 +00:00
zeekay
94741a8363
Completes the rebrand per direction: LANGFLOW_/LANGFLOW -> FLOW_/FLOW (env vars, headers), langflow_ -> flow_ (settings fields, local vars), camelCase identifiers (LangflowClient/Logo/HTTPError, builtWithLangflow, getLangflowDesktop) -> Flow*, and all remaining bare tokens. Fixed the identifier-space hazard (Langflow -> 'Hanzo Flow' is prose-only; in code it collapses to Flow so no identifier gains a space). compileall of flow + lfx is clean. Repo-wide langflow now = 4, all the protected MIT attribution to langflow-ai/ langflow in README (legally required; deliberately preserved). Breaking (per no-backwards-compat / forward-perfection): the LANGFLOW_* env-var prefix is now FLOW_* — deployments must update their env. CI's uv + frontend build is the runtime gate.
20 lines
950 B
Plaintext
20 lines
950 B
Plaintext
---
|
|
title: Deploy Hanzo Flow on Render
|
|
slug: /deployment-render
|
|
---
|
|
|
|
This guide explains how to deploy Hanzo Flow on [Render](https://render.com/), a cloud platform for deploying web applications and APIs.
|
|
|
|
1. Prepare a Render instance that can support Hanzo Flow.
|
|
|
|
Hanzo Flow requires at least 2 GB of RAM to run, so you must use a Render instance type of **Standard** or better.
|
|
This requires a paid Render account.
|
|
For more information, see [Render Web Services](https://render.com/docs/web-services) and [Render pricing](https://render.com/pricing).
|
|
|
|
2. Follow this link to start a Hanzo Flow deployment on Render:
|
|
|
|
[](https://render.com/deploy?repo=https%3A%2F%2Fgithub.com%2Fhanzoai%2Fflow%2Ftree%2Fdev)
|
|
|
|
3. Enter a blueprint name, select the branch for your `render.yaml` file, and then click **Deploy Blueprint**.
|
|
|
|
When deployment is complete, your Hanzo Flow instance is ready to use. |