Skip to main content
Guided configuration is designed to ask the setup questions in a terminal UI and produce a configuration you can inspect and reuse. It is an alternative to authoring the file yourself, not a separate configuration system.

​
What to prepare

Identify the origin services your application calls, a supported backend for each and where the adapters will run. Prepare the target region, required resource information and the identities allowed to provision resources and serve requests. If you already have backend resources, know which ones may be reused and which data must be preserved. Selecting an existing database is not permission to replace it or migrate its contents.

​
The terminal experience

The guided flow helps you select supported choices, validates answers as you enter them and lets you revisit earlier decisions. Before proceeding, it presents a reviewable summary and saves the generated configuration. The UI distinguishes configuration questions from provisioning progress. Completed, active and failed work remain visible so an interrupted setup does not leave you guessing which actions ran. This is a guided terminal interface, not an AI requirement. A coding agent is optional and does not replace your review of identities, resource changes and secret handling.

​
Keep the generated file

Treat the output as the input to later review and configuration updates. The file-based workflow and guided setup must converge on the same validation and compatibility rules. Do not use an existing installation’s guided setup as an assumed migration tool. Changing the backend of a populated service still requires a supported migration, regardless of how the configuration was generated.