
# Deployment configuration

Open the environment's **Build & Deployment** area to review configuration detected by the agent or entered by the user.

## Available fields

| Field | Purpose |
| --- | --- |
| **Root directory** | Path containing the application when the repository is a monorepo or the app is not at repository root. |
| **Pre-build commands** | Commands run before the main build. |
| **Post-build commands** | Commands run after the main build step. |
| **Procfile commands** | Process commands for web servers and workers. |
| **Port** | Port exposed by the web process. |
| **Dockerfile** | Container build instructions used for the workload. |

## Make changes safely

1. Compare the setting with the repository layout.
2. Update only the environment that needs the change.
3. Save the configuration.
4. Start or restart deployment through the supported dashboard action. By default, **Save & Deploy** saves the configuration and redeploys. If you ticked **Dockerfile & build settings** in [Manage Autodeploy](/docs/guides/manage-autodeploy), the button says **Save** and the change waits for the **Deploy** button in the header.
5. Follow **Build Logs** for the result.

Trial accounts can be restricted from editing root-directory, build-script, Dockerfile, and deployment settings until runtime credits are purchased.
