For optimal operation the FlowX.AI Designer should use a separate NGINX load balancer from the FlowX Engine. This routing mechanism handles API calls from the SPA (single page application) to the backend service, to the engine and to various plugins.Here’s an example/suggestion of an NGINX setup:
The FlowX.AI Designer is an SPA application that is packaged in a docker image with nginx:1.19.10. The web application allows an authenticated user to administrate the FLOWX platform.In order to configure the docker image you need to configure the next parameters:
Copy
Ask AI
flowx-process-renderer: env: BASE_API_URL: {{the one configured as host in the nginx}} PROCESS_API_PATH: {{something like /engine}} KEYCLOAK_ISSUER: {{openid provider - ex: https://something/auth/realms/realmName}} KEYCLOAK_REDIRECT_URI: {{url of the SPA}} KEYCLOAK_CLIENT_ID: {{client ID}} STATIC_ASSETS_PATH: {{mediaLibrary.s3.publicUrl }}/{{env}}