# Render deployments

Connect Render service configuration to the projects it deploys.


Use your Render Blueprint to connect build and startup commands to Nx projects. Megamono reads `render.yaml`, `render.yml`, or a `render.services.json` inventory without changing your deployed services.

## Add to your workspace

Check the [Node.js and Nx requirements](/docs/workflows/requirements#platform-plugins) for this plugin before installing.

Install `@megamono/nx-render` as a development dependency using your workspace's package manager. Merge this entry into the existing `plugins` list in `nx.json`:

```json
{
  "plugins": [
    "@megamono/nx-render"
  ]
}
```

Run `npm exec -- nx show projects` to find your project, then `npm exec -- nx show project <project>` to see its tasks. Replace `<project>` with the name from the list.

## Map services to projects

Services with a `rootDir` can be connected to the project at that location. For services defined at the repository root, use the plugin’s `serviceProjects` option to name the owning project and root explicitly.

Build, startup, and pre-deploy tasks are available when the corresponding service commands exist. Check the resolved project before running a task, especially a pre-deploy command that may apply migrations.

## Prepare a Blueprint

The [Render adoption generator](/docs/generators/nx-render-adopt) creates `render.proposed.yaml` from a Procfile or service inventory. Review that proposal before incorporating it into your deployment configuration. It does not replace your active Blueprint or deploy services.