Environments and kendor.yaml
Every coding challenge runs in its own sandbox, and a kendor.yaml file at the root of the project
says what that sandbox contains: the language and version, any databases, and the commands that
install, start and test each service. These articles cover every key the file accepts, the languages
and versions you can pick, PostgreSQL, MySQL, MongoDB and Valkey inside the sandbox, and projects
with more than one service.
kendor.yaml referenceEvery key kendor.yaml accepts, from runtime and services to routing, databases and sandbox, with types, defaults and the rules checked on save.Which languages and versions can a coding challenge useNode.js 22, Python 3.12, Go 1.27 and 1.26, Java 21, Rust 1.98, C++ (Clang 23) and PHP 8.3 and 8.4. Pick one with runtime.version in kendor.yaml.How to add a PostgreSQL, MySQL, MongoDB or Redis database to a coding challengeList PostgreSQL 18, MySQL 8.4, MongoDB 8.0 or Valkey 9 under databases in kendor.yaml. They run inside the sandbox, and code connects with DATABASE_URL, MONGODB_URI or REDIS_URL.How to run a frontend and an API together in one coding challengeDefine each part as a service in kendor.yaml with its own folder, commands and port, pick the preview service, and route paths like /api to the API.What happens to localhost URLs in a coding challenge's previewBrowser code that calls http://localhost:4000 is sent to port 4000 in the sandbox, with CORS, redirects and cookies handled. For the few cases it can't reach, use a relative path or routing.<service>.url.