@specific.dev/cli 0.1.50 → 0.1.51

package/dist/docs/builds.md

@@ -16,6 +16,8 @@ build "api" {
 ## Optional fields
 
 - `command` - Build command to run after dependencies are installed (e.g., `npm run build`, `go build -o api`).
+- `root` - Working directory for build commands, relative to `specific.hcl`. Defaults to `"."`. Sets the `WORKDIR` in the generated Dockerfile. Services that reference this build inherit its root. Dependency detection (e.g., `package.json`) also looks in this directory.
+- `context` - Docker build context scope, relative to `specific.hcl`. Defaults to `"."`. Controls what files are available to `COPY` in the Dockerfile and what's included in the deployment tarball. Use this when you need to include files outside of `root` (e.g., shared libraries in a monorepo).
 - `env` - Environment variables available during the build. Supports string literals and `service.<name>.public_url` references. These are passed as Docker build args.
 
 ## Automatic dependency installation
@@ -73,6 +75,46 @@ Supported reference types:
 - String literals (e.g., `"production"`)
 - `service.<name>.public_url` - The public domain of another service
 
+## Monorepo support
+
+Use `root` to specify where build commands run in a monorepo. This sets the working directory for both the build command and dependency installation.
+
+```hcl
+build "backend" {
+  base = "node"
+  root = "packages/backend"
+  command = "npm run build"
+}
+
+build "frontend" {
+  base = "node"
+  root = "packages/frontend"
+  command = "npm run build"
+}
+```
+
+Without `root`, you would need to prefix commands with `cd packages/backend &&`, and dependency detection would look for `package.json` in the wrong directory.
+
+Services that reference a build inherit its `root` automatically, so service commands also run from the correct directory.
+
+### `root` vs `context`
+
+`root` and `context` are orthogonal:
+
+- `root` = where commands run (working directory)
+- `context` = what files are available (Docker build context / tarball scope)
+
+By default, `context` is `"."` (the `specific.hcl` directory), which includes all files in the project. You only need to set `context` when you want to widen the scope beyond the default, for example to include a parent directory:
+
+```hcl
+# specific.hcl is in apps/myapp/, but shared libs are in libs/
+build "api" {
+  base = "node"
+  root = "packages/api"
+  context = "../"          # Include parent dir so shared libs are available
+}
+```
+
 ## Dev configuration
 
 Override the build command for local development. If no `dev` block is defined, the build is skipped in development.

package/dist/docs/services.md

@@ -46,6 +46,7 @@ service "api" {
 ```
 
 - `command` - Command to start the server
+- `root` - Working directory for service commands, relative to `specific.hcl`. Defaults to the referenced build's `root`, or `"."` if no build. In development, this sets the working directory for the spawned process. In production, the working directory is set by the build's `root` in the Dockerfile.
 - `endpoint` - Defines a network endpoint (see Endpoints below)
 - `port` - Reference to the auto-assigned port (pass this to your server)
 
@@ -190,6 +191,39 @@ service "api" {
 }
 ```
 
+## Monorepo support
+
+For monorepos, use `root` on builds to set the working directory. Services inherit the build's root, so commands like `npm start` run from the correct directory:
+
+```hcl
+build "backend" {
+  base = "node"
+  root = "packages/backend"
+  command = "npm run build"
+}
+
+service "backend" {
+  build = build.backend
+  command = "node dist/index.js"
+
+  dev {
+    command = "npm run dev"
+  }
+}
+```
+
+Dev-only services can set their own root:
+
+```hcl
+service "docs" {
+  root = "packages/docs"
+
+  dev {
+    command = "npm run dev"
+  }
+}
+```
+
 ## Workers
 
 Background processes that don't expose HTTP endpoints.

package/dist/postinstall.js

@@ -111,7 +111,7 @@ function trackEvent(event, properties) {
     event,
     properties: {
       ...properties,
-      cli_version: "0.1.50",
+      cli_version: "0.1.51",
       platform: process.platform,
       node_version: process.version,
       project_id: getProjectId(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@specific.dev/cli",
-  "version": "0.1.50",
+  "version": "0.1.51",
   "description": "CLI for Specific infrastructure-as-code",
   "type": "module",
   "main": "dist/cli.js",
@@ -66,4 +66,4 @@
       "esbuild"
     ]
   }
-}
+}