Files
flow/deploy
zeekay 930ffbc5c5 refactor: /v1/ canonical paths (sweep)
Per global rule: /v1/ only, never /api/. Internal API calls + handler
comments + route registrations updated. External vendor APIs (OpenRouter,
LangWatch, etc.) left as-is.

- Backend: APIRouter prefix dropped from "/api" — router_v1 (prefix=/v1)
  and router_v2 (prefix=/v2) now mount at the root, subdomain (api.*)
  already namespaces.
- API_V1_STR: "/api/v1" → "/v1"
- Frontend constants: BASE_URL_API "/api/v1/" → "/v1/" and BASE_URL_API_V2
  "/api/v2/" → "/v2/"; vite proxy + Traefik routing labels updated.
- Source files (mcp_utils, mcp_projects, mcp, folders, vertex_types,
  load/utils, mcp_sse, schema/workflow): all internal URL builders.
- Tests + e2e specs + API-code-generator templates + AWS CDK behaviors
  updated to match.
2026-05-18 21:58:07 -07:00
..
2025-03-28 22:44:48 +00:00

Run Hanzoflow

Docker compose

To run Hanzoflow with Docker compose, you need to have Docker and Docker compose installed on your machine. You can install Docker and Docker compose by following the instructions on the official Docker documentation.

The docker-compose file uses latest tag; it's recommended to pull the latest version of the images before running the docker-compose file.

docker compose pull

To start the Hanzoflow services, run the following command:

docker compose up

After running the command, you can access the Hanzoflow services at the following url: http://localhost:80.

Edit the .env file to change the port or other configurations.