Service Configuration

Service configuration controls how your application builds, starts, and runs. Open any service and go to Deployments → Build settings.

Build Settings

• Dockerfile path - Set the path if your Dockerfile is not in the repository root (e.g., backend/Dockerfile).
• Build context - By default, the repository root is used as the build context. If your Dockerfile is in a subdirectory and uses relative paths (e.g., COPY . .), enable "Use Dockerfile directory as build context" to use the Dockerfile's directory instead.
• Dependency vulnerability scan - Optionally scan every package-lock.json, pnpm-lock.yaml, yarn.lock, and bun.lock in the build context before building the image. At least one supported lockfile is required when enabled. Critical library vulnerabilities or scanner errors fail the build and block deployment. Open the deployment's Vulnerabilities tab to see scan progress, the passed summary, or findings by CVE and package.

See Dockerfile Requirements for examples of both approaches.

Runtime Settings

• Target URL - The first part of the URL is yours to edit. Changing it moves the service to the new URL and the old one stops working. To use your own domain instead, see Custom Domains.
• Port - The container port your app listens on. Must match your Dockerfile's EXPOSE directive.
• Replicas - How many copies of the service run behind the same URL. The maximum comes from your plan, see Plans & Usage.
• Environment variables - Key/value pairs and linked secrets, on the Env Vars tab. See Environment Variables.

Password Protection (Basic Auth)

Put a service behind an HTTP basic auth login. Available on the Earth plan and above.

1. Open the service and go to Deployments → Build settings.
2. Enable Password protect (HTTP basic auth).
3. Enter a Username and Password.
4. Save and redeploy - the credentials apply once the new deployment is live.

Anyone visiting the service is prompted for the username and password before the app loads. To change the password later, enter a new one. Leaving the password field blank keeps the current password. To remove protection, disable the checkbox and redeploy.

Custom Domains

Use your own domain for any service. See Custom Domains for setup instructions.

Uptime Monitoring

Repository services can register uptime monitoring from the Main environment overview. Select the platform domain or a verified custom domain, then choose a path such as /health. The Uptime card shows current availability, 30-day uptime, average response time, daily incident history, and the last check time.

Pending and failed custom domains remain visible but cannot be selected. Removing the selected custom domain also removes its uptime monitor.

Troubleshooting

Related

• Custom Domains
• Dockerfile Requirements
• Environment Variables
• How Rock8Cloud Works