.gitpod/automations.yaml (5)

5-7: Make the long‑running dev server a Service, keep install/prepare as a Task.

pnpm play is likely a long‑running server. Best practice: model it as a Service and keep setup as a short‑lived Task, improving observability and lifecycle control.

Apply this rewrite:

-tasks:
-  install-and-dev:
-    name: Install dependencies and start dev
-    command: |
-      pnpm install
-      pnpm dev:prepare
-      pnpm play
-    triggeredBy:
-      - postDevcontainerStart
-      - manual
+services:
+  dev:
+    name: Nuxt Dev Server
+    commands:
+      start: pnpm play
+    triggeredBy:
+      - postDevcontainerStart
+tasks:
+  setup:
+    name: Install dependencies and prepare workspace
+    command: |
+      pnpm install --frozen-lockfile
+      pnpm dev:prepare
+    triggeredBy:
+      - postDevcontainerStart
+      - manual

Note: Services are intended for long‑running processes; Tasks are short‑lived and one‑off. (ona.com)

---

8-10: Consider adding postEnvironmentStart to cover runner resume scenarios.

On AWS runners, resumes may not re‑trigger postDevcontainerStart. If you want setup to re‑run on every environment start/resume, include postEnvironmentStart.

Example:

     triggeredBy:
-      - postDevcontainerStart
+      - postDevcontainerStart
+      - postEnvironmentStart
       - manual

Source: (ona.com)

---

5-6: Lock installs for reproducibility.

Use pnpm install --frozen-lockfile to prevent drift from the committed lockfile.

---

1-10: Replicate old port 3000 “open-preview” behaviour via devcontainer.json.

Since the Classic ports config is removed, add this to .devcontainer/devcontainer.json to auto‑forward 3000 and open a preview/browser:

{
  "appPort": [3000],
  "portsAttributes": {
    "3000": {
      "onAutoForward": "openPreview"
    }
  }
}

Sources: (code.visualstudio.com, git.lance1416.com)

---

10-10: Add a newline at end of file.

Fixes the YAML lint error.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro