@specific.dev/cli 0.1.42 → 0.1.44

package/dist/docs/index.md

@@ -28,6 +28,7 @@ The following is a list of common frameworks and libraries with guidance on how
 - [Next.js](/integrations/nextjs): full-stack React framework
 - [Drizzle ORM](/integrations/drizzle): TypeScript ORM with type safety
 - [Prisma](/integrations/prisma): TypeScript ORM with auto-generated client
+- [Temporal](/integrations/temporal): durable workflow engine for background tasks, AI agents, cron jobs, batch jobs and more
 
 ## Adding Specific to existing projects / migrating to Specific
 

package/dist/docs/integrations/nextjs.md

@@ -32,6 +32,24 @@ service "web" {
 
 Next.js reads `PORT` from the environment automatically, so no additional configuration is needed.
 
+## Migrating existing secrets
+
+If the project has existing secrets in `.env`, `.env.local`, or similar files, move them to `specific.local` so they don't need to be re-entered when running `specific dev`:
+
+```hcl
+# specific.local
+secrets {
+  stripe_api_key = "sk_test_..."
+  database_password = "..."
+}
+
+configs {
+  api_url = "https://api.example.com"
+}
+```
+
+If there are secrets that are not defined in `specific.hcl` but exist in `.env`, ask the user about it and perhaps add configs/secrets for them.
+
 ## Important note on pre-rendering during builds
 
 During a build, Next.js will load a lot of code to perform pre-rendering. That code can not reference any environments variables from `specific.hcl`, like database URLs or API keys from secrets, as those are not available during the build and will cause it to fail. Ensure all code that relies on these env vars DOES NOT get executed during the build phase.

package/dist/docs/integrations/temporal.md

@@ -0,0 +1,89 @@
+# Temporal
+
+Temporal is a durable workflow engine. This guide covers running Temporal locally during development and connecting to Temporal Cloud in production.
+
+Temporal has extensive SDK support across many languages including TypeScript, Python, Go, Java, .NET, and PHP. See the [Temporal documentation](https://docs.temporal.io/) for language-specific guides on implementing workers, workflows, and activities. This document only covers integration with Specific.
+
+## Configuration
+
+Define a dev-only Temporal service that runs locally, along with configs and secrets for production Temporal Cloud.
+
+```hcl
+build "app" {
+  base = "node"
+}
+
+# Dev-only service: runs local Temporal server during development
+# No top-level command means it's excluded from production deployment
+#
+service "temporal" {
+  endpoint "grpc" {}
+  endpoint "ui" { public = true }
+
+  dev {
+    command = "temporal server start-dev --port $GRPC_PORT --ui-port $UI_PORT --db-filename /tmp/temporal.db"
+    env = {
+      GRPC_PORT = endpoint.grpc.port
+      UI_PORT   = endpoint.ui.port
+    }
+  }
+}
+
+# Temporal Cloud address (e.g., your-namespace.tmprl.cloud:7233)
+config "temporal_address" {}
+
+# Namespace - uses "default" in dev, must be set for production
+config "temporal_namespace" {
+  dev {
+    default = "default"
+  }
+}
+
+# API key for Temporal Cloud - not required in dev
+secret "temporal_api_key" {
+  dev {
+    required = false
+  }
+}
+
+service "app" {
+  build = build.app
+  command = "node index.js"
+  expose {}
+
+  env = {
+    PORT               = port
+    TEMPORAL_ADDRESS   = config.temporal_address
+    TEMPORAL_NAMESPACE = config.temporal_namespace
+    TEMPORAL_API_KEY   = secret.temporal_api_key
+  }
+
+  dev {
+    command = "node --watch index.js"
+    env = {
+      # Override to use local Temporal service instead
+      TEMPORAL_ADDRESS = ""
+      TEMPORAL_HOST    = service.temporal.endpoint.grpc.host
+      TEMPORAL_PORT    = service.temporal.endpoint.grpc.port
+    }
+  }
+}
+```
+
+## Development
+
+Running `specific dev` automatically starts a local Temporal server. The user must install the Temporal CLI for this: https://temporal.io/setup/install-temporal-cli. The Temporal Web UI is available at the public endpoint URL shown in the output.
+
+Your app connects to the local Temporal server using the service endpoint environment variables (`TEMPORAL_HOST` and `TEMPORAL_PORT`).
+
+## Production
+
+In production, the dev-only `temporal` service is excluded from deployment. Your app connects to Temporal Cloud using:
+
+1. `temporal_address` - Your Temporal Cloud address (e.g., `your-namespace.tmprl.cloud:7233`)
+2. `temporal_namespace` - Your Temporal Cloud namespace
+3. `temporal_api_key` - API key for authentication
+
+Set these with `specific secrets set` before deploying.
+
+## SDK support

package/dist/docs/migrations/supabase.md

@@ -53,6 +53,24 @@ There is currently no equivalent to Supabase Cron available in Specific. It will
 - Replace all Supabase client calls with standard `fetch` requests to your backend API service
 - Pass auth tokens via request headers (e.g., `Authorization: Bearer <token>`) to the backend service for authenticated endpoints
 
+## Migrating existing secrets
+
+If the project has existing secrets in `.env`, `.env.local`, or Supabase configuration files, move them to `specific.local` so they don't need to be re-entered when running `specific dev`:
+
+```hcl
+# specific.local
+secrets {
+  stripe_api_key = "sk_test_..."
+  jwt_secret = "..."
+}
+
+config {
+  api_url = "https://api.example.com"
+}
+```
+
+Note: Only secrets and configs that are declared in `specific.hcl` need to be added to `specific.local`. The Supabase-specific environment variables (like `SUPABASE_URL` and `SUPABASE_ANON_KEY`) are no longer needed after migration.
+
 ## Data migration
 
 Data migration out of Supabase Postgres and Storage (S3) into Specific is currently a manual process. Help guide the user through this if they want it.

package/dist/docs/secrets-config.md

@@ -9,7 +9,7 @@ Secrets and config let you parameterize values that services need. Use them to a
 
 ## Secrets
 
-Declare secrets that your application needs. Values are stored separately from configuration in `specific.secrets` (gitignored).
+Declare secrets that your application needs in `specific.hcl`:
 
 ```hcl
 secret "stripe_api_key" {}
@@ -40,17 +40,18 @@ service "api" {
 
 ### Setting secret values
 
-For local development with `specific dev` or `specific exec`, use the CLI:
+For local development, add secrets to the `secrets` block in `specific.local`:
 
-```bash
-specific secrets set stripe_api_key
+```hcl
+# specific.local
+secrets {
+  stripe_api_key = "sk_test_..."
+}
 ```
 
-This prompts for the value interactively and stores it in `specific.secrets`. Production secrets are configured separately during deployment.
-
 ### Generated vs manual secrets
 
-- **Manual secrets** (no `generated` flag) - Must be set via `specific secrets set`. Error on startup if missing.
+- **Manual secrets** (no `generated` flag) - Must be set in `specific.local`. Error on startup if missing.
 - **Generated secrets** (`generated = true`) - Auto-created on first run if not set. You can still override manually.
 
 ## Config
@@ -80,9 +81,20 @@ service "api" {
 
 - `default` - Default value used if not overridden by an environment.
 
+### Setting config values locally
+
+For local development, you can override config defaults in the `config` block of `specific.local`:
+
+```hcl
+# specific.local
+config {
+  log_level = "debug"
+}
+```
+
 ### Environment overrides
 
-Override config values per environment:
+Override config values per environment in `specific.hcl`:
 
 ```hcl
 config "log_level" {
@@ -102,9 +114,28 @@ environment "staging" {
 }
 ```
 
+## Local values file
+
+For local development, secrets and config values are stored in `specific.local` (gitignored). The user does not have to fill this out manually. When running, `specific dev`, they will be asked for any missing secrets and config values. The file. This file uses HCL format with separate blocks for secrets and configs:
+
+```hcl
+# specific.local
+secrets {
+  stripe_api_key = "sk_test_..."
+}
+
+config {
+  log_level = "debug"
+}
+```
+
+This file is automatically gitignored and not included in deployments. Production secrets are configured separately during deployment.
+
 ## Example
 
 ```hcl
+# specific.hcl
+
 # External API key - must be set manually, sensitive
 secret "stripe_api_key" {}
 
@@ -139,3 +170,16 @@ environment "production" {
   }
 }
 ```
+
+And the corresponding local values file:
+
+```hcl
+# specific.local (gitignored)
+secrets {
+  stripe_api_key = "sk_test_..."
+}
+
+config {
+  log_level = "debug"
+}
+```

package/dist/docs/services.md

@@ -116,14 +116,14 @@ service "worker" {
   command = "./worker"
 
   env = {
-    API_URL = service.api.url  # http://localhost:PORT in dev, http://api:80 in prod
+    API_URL = service.api.url  # localhost:PORT in dev, api:80 in prod
   }
 }
 ```
 
 Available service reference attributes:
 
-- `service.<name>.url` - Full URL (e.g., `http://localhost:3000`)
+- `service.<name>.url` - Full URL without scheme (e.g., `localhost:3000`)
 - `service.<name>.host` - Host only (e.g., `localhost`)
 - `service.<name>.port` - Port only (e.g., `3000`)
 
@@ -233,6 +233,7 @@ secret "temporal_url" {}
 ```
 
 Dev-only services:
+
 - Cannot have a `build` reference (they run arbitrary commands)
 - Are automatically excluded from production deployment
 - Can define endpoints that other services reference during development
@@ -320,6 +321,7 @@ service "frontend" {
 ---
 
 Related topics:
+
 - Run `specific docs builds` for build configuration
 - Run `specific docs exec` for running one-off commands during development
 - Run `specific docs postgres` for database configuration

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@specific.dev/cli",
-  "version": "0.1.42",
+  "version": "0.1.44",
   "description": "CLI for Specific infrastructure-as-code",
   "type": "module",
   "main": "dist/cli.js",
@@ -34,7 +34,9 @@
     "node": ">=18"
   },
   "dependencies": {
+    "@specific/config": "file:../config",
     "chokidar": "^5.0.0",
+    "hcl2-json-parser": "^1.0.1",
     "commander": "^14.0.2",
     "http-proxy": "^1.18.1",
     "ink": "^6.5.1",
@@ -42,14 +44,20 @@
     "node-forge": "^1.3.1",
     "open": "^11.0.0",
     "posthog-node": "^5.24.1",
-    "react": "^19.2.3",
+    "react": "^19.0.0",
     "s3rver": "^3.7.1",
     "tar-vern": "^1.3.0"
   },
   "devDependencies": {
     "@types/http-proxy": "^1.17.17",
+    "@types/node": "^25.0.1",
     "@types/node-forge": "^1.3.11",
     "@types/react": "^19.2.7",
-    "esbuild": "^0.24.0"
+    "esbuild": "^0.24.0",
+    "tsx": "^4.21.0",
+    "typescript": "^5.9.3"
+  },
+  "pnpm": {
+    "onlyBuiltDependencies": ["esbuild"]
   }
-}
+}