Render adopt
Create a reviewed Render Blueprint proposal from a Procfile or dashboard inventory.
When to use it
Create a reviewed Render Blueprint proposal from a Procfile or dashboard inventory.. Use this when you want to add the corresponding files or task to your workspace.
Usage
npm exec -- nx generate @megamono/nx-render:adopt --dry-runReplace angle-bracket placeholders with reviewed values. Nx's --dry-run previews generator writes; remove it only after reviewing the plan. Examples use npm; use your workspace's package manager if it differs.
Options
Use these options with @megamono/nx-render:adopt. Nx uses the camelCase names shown here; the CLI reference describes command-line aliases. Some options are required only for particular choices.
| Option | Required | Type | Default | Description |
|---|---|---|---|---|
procfile | No | string | — | Workspace-relative Procfile to convert when no dashboard inventory exists. |
inventory | No | string | — | Workspace-relative render.services.json dashboard inventory. |
serviceProjects | No | string | — | JSON adoption map containing service project roots and optional databases arrays of logical Prisma database names from megamono.json. Prisma services receive build generation dependencies and a migration pre-deploy proposal. |
output | No | string | — | Review-only Blueprint output path. |
force | No | boolean | false | Replace an existing proposal output. |
Next steps
Review changed files and run the affected project's checks. For options that accept structured values, run the generator's --help or consult the schema in the installed package.
