Skip to main content

Environment Setup

An environment is the reproducible container definition CoderFlow builds every task from — your repositories, the runtime and dependencies, and how the app runs and is tested. You configure it once in the Web UI, build an image, and every task in that environment starts from it. For the concept, see Core Concepts; for the full per-tab reference, see Environments.

Setup follows the same shape no matter what you're building:

  1. Create the environment and add your repositories.
  2. Configure it through the Web UI tabs — runtime, dependencies, how the app starts or is reached, and tests.
  3. Build the image, then create a task and exercise it from the Testing menu.

What differs is how your app runs and is served. Pick the path that matches your stack.

Web applications​

A backend paired with a browser front end — .NET, Node.js, Java, Python, or PHP with Angular, React, Vue, or plain HTML/CSS. The app runs inside the task container (or, occasionally, is proxied to one running elsewhere).

Start with Web Application Environments for the pattern and serving models, then the Stack reference for per-stack values and the Examples for complete walkthroughs.

IBM i​

Green-screen (5250) and Rich Display applications served by Profound UI Genie. Nothing runs in the task container — CoderFlow proxies to the running Genie server while the agent edits and compiles source on the IBM i.

See Setting up an IBM i environment, part of the IBM i section, which also covers connections, codermake builds, source import, and sync.