Add zero-config build path for Node.js apps

.github/workflows/test.yml

@@ -0,0 +1,36 @@
+name: Test
+
+on:
+  pull_request:
+  push:
+    branches: [main]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Validate action metadata
+        run: |
+          find . -maxdepth 2 -name action.yml -not -path './.github/*' -print0 |
+            while IFS= read -r -d '' f; do
+              echo "::group::$f"
+              npx --yes --package=@action-validator/cli action-validator "$f"
+              echo "::endgroup::"
+            done
+
+      - name: Lint workflows
+        run: |
+          bash <(curl -fsSL https://raw.githubusercontent.com/rhysd/actionlint/main/scripts/download-actionlint.bash)
+          ./actionlint -color
+
+  build-test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: docker/setup-buildx-action@v3
+
+      - name: Run build test
+        run: ./test/build-test.sh

README.md

@@ -1,11 +1,35 @@
 # MIEWeb LaunchPad
 
-GitHub Action that deploys Docker/OCI images as LXC containers on an [opensource-server](https://github.com/mieweb/opensource-server) Proxmox cluster via the Container API. It derives a container name from your repository and branch, decides when to create/recreate/delete, and delegates every API call to the reusable composite actions in [mieweb/opensource-server/.github/actions](https://github.com/mieweb/opensource-server/tree/main/.github/actions).
+GitHub Action that deploys your repository as an LXC container on an [opensource-server](https://github.com/mieweb/opensource-server) Proxmox cluster via the Container API. Point it at a Node.js repo with zero configuration and it builds a systemd-enabled image, pushes it to ghcr.io, and deploys it — or hand it a pre-built image via `template_name`. It derives a container name from your repository and branch, decides when to create/recreate/delete, and delegates every API call to the reusable composite actions in [mieweb/opensource-server/.github/actions](https://github.com/mieweb/opensource-server/tree/main/.github/actions).
 
 ## Prerequisites
 
-- A Docker/OCI image published to a container registry (GHCR, Docker Hub, etc.)
 - An API key for the create-a-container server (request one from your site admin)
+- **Build mode** (no `template_name`): a public repository — the image package inherits the repo's visibility at first publish, and the cluster pulls anonymously. Private repos need a one-time manual package visibility flip on ghcr.io.
+- **Traditional mode**: a Docker/OCI image published to a public container registry (GHCR, Docker Hub, etc.)
+
+## Application Lifecycle (Build Mode)
+
+When `template_name` is omitted on a manage event, LaunchPad builds the checked-out repository with a default Dockerfile that models a standard application lifecycle, assuming a Node.js app by default:
+
+| # | Stage | Input | Default |
+|---|-------|-------|---------|
+| 1 | Dependencies | `dependency_command` | `npm ci --no-audit --no-fund` |
+| 2 | Configure | `build_command` | *(empty — skipped)* |
+| 3 | Build | `build_command` (same input, e.g. `./configure && make`) | *(empty — skipped)* |
+| 4 | Install | built into the image: repo copied to `working_directory`, systemd unit installed and enabled | — |
+| 5 | Run | `run_command`, executed by `app.service` | `npm start` |
+
+The image is based on `base_image` (systemd + Docker-in-Docker enabled), tagged `ghcr.io/<owner>/<repo>/launchpad:<commit sha>` (override with `image`), and pushed with the workflow's `GITHUB_TOKEN`. The generated `app.service` sets `Documentation=` to your repository URL, runs in `working_directory`, and loads container environment variables from `/etc/environment`.
+
+Requirements and limits:
+
+- Run `actions/checkout` before this action, and grant the job `permissions: contents: read, packages: write`.
+- A `run_command` containing single quotes or newlines breaks the generated unit — commit a script to your repo and use that instead (or use the traditional path with your own Dockerfile).
+- A custom `base_image` must be systemd-enabled and provide `envsubst` (Debian package `gettext-base`).
+- The `image` override must be under `ghcr.io/<owner>/` so `GITHUB_TOKEN` can push it.
+
+> **Breaking change:** previously, omitting `template_name` on a manage event reused an existing container as-is. It now builds and deploys from the repository. Cleanup-only jobs (PR close / branch delete) are unaffected — they never build.
 
 ## Repository Secrets
 
@@ -22,10 +46,24 @@ Add these in **Settings > Secrets and variables > Actions**:
 |-------|----------|---------|-------------|
 | `api_key` | Yes | — | Bearer token for authenticating with the Container API |
 | `api_url` | Yes | — | Base URL of the create-a-container server |
-| `template_name` | No | — | Docker/OCI image reference to deploy (e.g., `ghcr.io/org/app:tag`). When provided and a container already exists, it is deleted and recreated with the new template. When omitted, an existing container is reused as-is. |
+| `template_name` | No | — | Docker/OCI image reference to deploy (e.g., `ghcr.io/org/app:tag`). When provided, an existing container is deleted and recreated with the new template. **When omitted on a manage event, LaunchPad builds the repository instead (build mode).** |
 | `container_env_vars` | No | — | Environment variables to set inside the container (JSON string, e.g., `'{"NODE_ENV": "production"}'`) |
 | `services` | No | — | Services configuration (JSON array string) |
 | `site_id` | No | `1` | Site ID for the container management system |
+| `image` | No | `ghcr.io/<owner>/<repo>/launchpad:<sha>` | Build mode: full image reference to build and push. Must be under `ghcr.io/<owner>/` |
+| `base_image` | No | `ghcr.io/mieweb/opensource-server/docker-nodejs:latest` | Build mode: base image for the default Dockerfile |
+| `working_directory` | No | `/workspace` | Build mode: where the repository is copied inside the image |
+| `dependency_command` | No | `npm ci --no-audit --no-fund` | Build mode: dependency install command |
+| `build_command` | No | *(empty — skipped)* | Build mode: configure/build command (e.g. `./configure && make`) |
+| `run_command` | No | `npm start` | Build mode: command `app.service` runs |
+
+Build-mode inputs are ignored when `template_name` is provided.
+
+## Outputs
+
+| Output | Description |
+|--------|-------------|
+| `image` | The image reference built and pushed by build mode (empty on the traditional `template_name` path) |
 
 ## Supported Workflow Events
 
@@ -48,21 +86,21 @@ Containers are named `<owner>-<repo>-<branch>`, lowercased, with any character o
 sequenceDiagram
     participant GH as GitHub Workflow
     participant LP as LaunchPad
+    participant REG as ghcr.io
     participant API as Container API
     participant Prox as Proxmox Cluster
 
     GH->>LP: push / create / pull_request / delete
+    alt Manage event, no template_name (build mode)
+        LP->>REG: build default Dockerfile, push ghcr.io/owner/repo/launchpad:sha
+    end
     LP->>API: get-container (by hostname)
 
-    alt Manage event (push, create, PR open/sync)
-        alt Container exists and template_name provided
+    alt Manage event
+        alt Container exists
             LP->>API: delete-container
-            LP->>API: create-container
-        else Container exists, no template_name
-            LP->>LP: Reuse existing container
-        else No container
-            LP->>API: create-container
         end
+        LP->>API: create-container (template = built image or template_name)
         API->>Prox: Enqueue creation job
         LP->>API: wait-for-job (poll until done)
         LP->>API: get-container (final status)
@@ -72,11 +110,51 @@ sequenceDiagram
     end
 ```
 
-Each API call is a thin composite action: [get-container](https://github.com/mieweb/opensource-server/tree/main/.github/actions/get-container), [create-container](https://github.com/mieweb/opensource-server/tree/main/.github/actions/create-container), [delete-container](https://github.com/mieweb/opensource-server/tree/main/.github/actions/delete-container), [wait-for-job](https://github.com/mieweb/opensource-server/tree/main/.github/actions/wait-for-job).
+The action is a dispatcher over three sub-actions in this repository — [build](https://github.com/mieweb/launchpad/tree/main/build), [manage](https://github.com/mieweb/launchpad/tree/main/manage), and [delete](https://github.com/mieweb/launchpad/tree/main/delete) — which delegate each API call to a thin composite action: [get-container](https://github.com/mieweb/opensource-server/tree/main/.github/actions/get-container), [create-container](https://github.com/mieweb/opensource-server/tree/main/.github/actions/create-container), [delete-container](https://github.com/mieweb/opensource-server/tree/main/.github/actions/delete-container), [wait-for-job](https://github.com/mieweb/opensource-server/tree/main/.github/actions/wait-for-job).
 
 The action fails if the container is not found after creation or its final status is not `running`.
 
-## Basic Usage
+## Basic Usage — Zero-Config Build & Deploy
+
+For a Node.js repository, this is all you need. On every push, LaunchPad builds the repo into a systemd-enabled image, pushes it to ghcr.io, and deploys it:
+
+```yaml
+name: Deploy
+
+on:
+  push:
+
+permissions:
+  contents: read
+  packages: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: mieweb/launchpad@main
+        with:
+          api_key: ${{ secrets.API_KEY }}
+          api_url: ${{ secrets.API_URL }}
+```
+
+Override any lifecycle stage as needed:
+
+```yaml
+      - uses: mieweb/launchpad@main
+        with:
+          api_key: ${{ secrets.API_KEY }}
+          api_url: ${{ secrets.API_URL }}
+          dependency_command: npm ci --no-audit --no-fund && pip install -r requirements.txt
+          build_command: npm run build
+          run_command: node dist/server.js
+```
+
+## Basic Usage — Pre-Built Image
+
+Build and push the image yourself (any Dockerfile, any workflow), then hand LaunchPad the reference:
 
 ```yaml
 - uses: mieweb/launchpad@main
@@ -122,7 +200,7 @@ jobs:
           api_url: ${{ secrets.API_URL }}
 ```
 
-`template_name` is not needed for cleanup — the closed PR event triggers deletion of the container associated with the PR head branch.
+`template_name` is not needed for cleanup — the closed PR event triggers deletion of the container associated with the PR head branch. Omitting `template_name` triggers build mode only on manage events; `closed` events go straight to deletion.
 
 ## Complete Example: Build + Deploy