Guided configuration
The Executor journey ends in exactly one deliverable: a single binary file that runs your application under every restriction you configured. oee init --interactive walks through the configuration in order, writes a complete oee.yaml, and prints the exact oee build command to run next.
oee init --interactive
Every answer can also be given without the wizard, by editing oee.yaml directly.
The eight steps
| Step | You provide | Section of oee.yaml |
|---|---|---|
| 1. Application | The path to the built application: a binary, a Python project, a JAR or WAR, or a Node.js project. | workload.<adapter> inputs and bundle_paths |
| 2. Runtime | The language and runtime version, detected automatically for you to confirm. | workload.adapter and the runtime's version |
| 3. Start command | The exact command line that starts the service, and whether extra command-line arguments pass through. | workload.entrypoint, passthrough_cli_args |
| 4. Exit events | Zero or more exit events of any category: time, utilization, external source, message or application, each with its parameters and optional authorization. | exit_events.rules |
| 5. Capping | CPU and memory limits, each as a percentage or an absolute amount, each strict or flexible. | resources |
| 6. Auto-scaling | Whether to scale out, the lower and upper thresholds, the replica bounds and the public port. | autoscale |
| 7. Sandbox | Whether to isolate the filesystem, the network and system calls. | sandbox |
| 8. Build | The target platform and the signing key. | oee build produces one binary file |
What the wizard guarantees
- Valid answers. Each answer is validated with the same rules as
oee validate: durations, cron expressions, JSONPath queries, sandbox paths and environment variable references. - No secrets in the file. The wizard never writes a secret into
oee.yaml, unless you explicitly choose a sealed static token. Credentials are read at run time withfrom_envorfrom_file. - The next command. It ends by printing the exact
oee buildcommand for your target and key.
After the wizard
oee validate -f oee.yaml --strict
oee keygen --out-dir ./certs
oee build -f oee.yaml --target linux-x86_64 --sign-key ./certs/oee.key -o ./dist/my-service
The guides cover each step in depth: Runtimes and adapters, Exit events, CPU and memory capping, Auto-scaling and load balancer and Sandboxing.