Getting started
Two pages take you from nothing to a running single binary: receiving and installing the oee command-line tool, then scaffolding, validating, signing, building, inspecting and running your first binary.
The Executor is in early preview — message us for access.
In this section
Install
The platforms and packages of the
oeeCLI, and how to request access.Your first binary
The standard workflow, from
oee initto running the finished binary, in minutes.
Before you begin
- A built application: a compiled native binary, a Python project, a JAR or WAR, or a Node.js project. Runtimes and adapters lists what the Executor accepts.
- The exact command that starts it.
- A decision on what should end it, how much CPU and memory it may use, and whether it should scale out. The guided configuration asks for each in turn.