Get started

What you’ll need

• Java 17+ — jgen and the generated services are Java/Spring Boot.
• Maven (mvn) — to build jgen and the generated project.
• git and a shell — bash, zsh or PowerShell.

(No Node required — jgen is a Java program.)

1 · Install jgen

git clone https://github.com/rajakolluru/chenile-gen.git
cd chenile-gen
make clean all            # builds jgen (and stm-cli) and the CLI wrapper scripts
source setpath.sh         # puts `jgen` and `stm-cli` on your PATH

make all builds the multi-module jgen project and prepares the launcher at jgen/jgen-cli/bin/jgen.sh. source setpath.sh adds that (and stm-cli) to your PATH for the session — add the same line to your ~/.zshrc / ~/.bashrc to make it permanent.

2 · (Optional) create a local config

jgen ships sensible defaults (package com.mycompany.myorg, version 0.0.1-SNAPSHOT, output ./output). To customise them for your company:

jgen -e                   # emits the default config into ./config

Edit config/config.json — set company, org and the Chenile version. jgen offers any file in config/ as a choice at startup, and resolves placeholders like ${defaultVersion} from it.

3 · Generate a service

Run jgen with no arguments for the interactive flow:

jgen
# 1) pick your config (or the bundled default)
# 2) choose the blueprint:  chenile-service
# 3) service name:          orders
#    accept the defaults for version (0.0.1-SNAPSHOT) and output (./output)
#    jpa: y   security: n   cloudSwitch: n   MCP: n

You now have output/orders/ — the service, split into orders-api (the definition) and orders-service (the implementation).

Prefer scripted/non-interactive generation? jgen -g chenile-service -o orders.json writes a sample input file showing exactly which fields the blueprint expects; edit it, then run jgen -f orders.json.

4 · Generate a mini-monolith to host it

A service module is a library — it’s deployed by a mini-monolith. Generate one and add your service as a dependency:

jgen
# choose the blueprint:  minimonolith
# monolith name:         ordersdeploy
# add "orders" under the dependencies prompt (and enable H2 console / query controller if you like)

This produces output/ordersdeploy/ — a runnable Spring Boot deployable that hosts one or more Chenile services.

5 · Build & run

cd output/orders       && make build     # builds the api + service libraries (mvn install)
cd ../ordersdeploy     && make build     # builds the deployable
cd ../ordersdeploy     && make run       # starts it — call your endpoint with the scripts in scripts/

More blueprints

jgen ships a blueprint for almost every kind of Chenile module — a workflow service, a MyBatis query, an interceptor, a batch job, integration tests, even a blueprint that generates blueprints. Explore them all: