Reporch IDE
Start a deployment
Choose the current workspace or a Git branch and commit, review build settings, and create a deployment.
Overview
A new Reporch IDE deployment combines the code source, build rules, and selected environment variables. The source can be the current workspace or a connected Git branch and commit.
Before you start
- Verify that the project installs, builds, and runs in the workspace terminal.
- For Git source, push the required changes to the intended branch or commit.
- Register the environment variables required by the project.
- Determine whether the output is a static site or a long-running web application.
Steps
1. Open deployment
From the active workspace, open Deployments and choose New Deployment. Without an active workspace, source and project settings cannot be completed.
2. Check the source
Current Workspace uses the workspace file state. For Git, confirm the repository, branch, and commit shown on screen.
3. Enter project defaults
Review the project name and Application Preset. For a monorepo, change Root Directory to the application folder. A single-project default is ./.
4. Review Build and Output Settings
Expand the section and check Build Command, Output Directory, and Install Command. Keep detected values when they match the actual scripts; override only when the project requires it.
5. Select environment variables
In Environment Variables, select only keys used by this application. Verify scope and target for the intended deployment.
6. Deploy once
Select Deploy once. Follow dependency installation, build, and release phases in the live log.
7. Verify the result
When complete, open the URL and test critical routes. Record Summary, Source, Deployment ID, and logs for later diagnosis.
Build settings reference
| Setting | Meaning | Verification |
|---|---|---|
| Application Preset | Framework-specific defaults | Matches the actual framework |
| Root Directory | Base folder of the deployed app | Contains configuration and source |
| Install Command | Dependency installation | Uses the package manager matching the lockfile |
| Build Command | Produces a production artifact | Succeeds in the IDE terminal |
| Output Directory | Location of static output | Matches framework output configuration |
Expected result
- The new record shows the selected Source and a unique Deployment ID.
- A successful installation and build produces a completed state and deployment URL.
- Critical pages and server behavior work at the provided URL.
Deployment states
- Queued/Preparing: Reporch prepares the recipe and execution environment.
- Building: Install and build commands are running. Diagnose the first failure in the log.
- Complete: A URL exists; verify the actual page and API rather than relying on status alone.
- Failed: Inspect the exit code and first failed command.
Troubleshooting
- Install fails: Match the lockfile and package manager in Install Command.
- Build command is missing: Check preset,
package.jsonscripts, and Root Directory. - Output is missing: Match the actual build artifact folder and Output Directory.
- Deployment succeeds but app fails: Check missing environment variables and runtime logs.
- Old code was deployed: Recheck the selected branch, commit, or saved workspace state.