Skip to content

ProfoundLogic/coderflow-reference-apps

Repository files navigation

CoderFlow Reference Apps

Minimal "hello world" applications that demonstrate the CoderFlow environment setup patterns. Each subdirectory is a self-contained reference app — a backend serving GET /api/hello and a front end that fetches and displays it — that you point a CoderFlow environment at. No local toolchain required.

Every combo follows the same shape, so only the per-stack values differ:

<backend>-<frontend>/
  api/               # backend, serves GET /api/hello on 0.0.0.0:3001
  web/               # front-end dev server, proxies /api -> :3001
  environment.json   # an importable CoderFlow environment (preconfigured to launch)
  AGENTS.md          # per-environment agent instructions (imported as CLAUDE.md)
  README.md          # how to run this combo

The matrix

The grid below is two-process (live reload): the API runs on :3001 and the front-end dev server proxies /api to it. This is the recommended model for actively iterating on a UI — edits reload the browser with no rebuild.

Backend ↓ / Front end → Angular React Vue
Node.js (Express) node-angular node-react node-vue
.NET (ASP.NET Core, .NET 8) dotnet-angular dotnet-react dotnet-vue
Java (Spring Boot, JDK 17) java-angular java-react java-vue
Python (FastAPI) python-angular python-react python-vue
PHP (built-in server) php-angular php-react php-vue

Two standalone examples sit alongside the grid:

  • php-html — the single-origin model: one PHP process serves both the page and the API on one port, with no front-end build and no proxy. The natural counterpart to the two-process grid.
  • static/ — plain HTML/CSS/JS, no backend.

Use it in CoderFlow

Import and launch (easiest): in CoderFlow, Import Environment → Git repository, paste this repo's URL, Load environments, pick a combo (e.g. node-react), Import, then build and launch. Each combo's environment.json is preconfigured — it clones this repo, installs the runtime (pre-clone) and dependencies (post-clone), and runs the application server(s). Nothing to wire up by hand.

Customize from there: adjust ports, start commands, or add connections in the Web UI, and capture a working environment back out with Export.

Run it locally

Each combo's README.md has the exact commands. The shape is always:

# install
cd api && <install>           # e.g. npm install / dotnet restore / pip install -r requirements.txt
cd ../web && npm install

# run (two terminals)
cd api && <start>             # API on 0.0.0.0:3001
cd web && <start>             # dev server, proxies /api -> :3001

The front end then shows "Hello from the <Backend> API!".

Maintaining

The combos are assembled by scripts/generate.sh from the hand-authored templates in templates/ (one per backend and front end) — maintainer tooling, not part of any reference app. The committed combos are the source of truth that CoderFlow clones; regenerate them all with scripts/generate.sh, or one with scripts/generate.sh node-react.

Versions

  • .NET — targets .NET 8 (LTS).
  • Java — Spring Boot 3 on JDK 17, built with Maven.
  • Python — FastAPI on Python 3.11+, served with uvicorn.
  • PHPPHP 8, built-in web server.
  • Angular — Angular 21 (standalone, no SSR/routing); React/Vue on Vite 5.

Match these to the runtime installed in each environment's pre-clone step.

About

Minimal hello-world reference apps for CoderFlow environments (backend x frontend matrix)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors