@dedesfr/prompter 0.8.21 → 0.8.23

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # CHANGELOG
 
+## [0.8.23] - 2026-05-08
+
+### 🔄 Changed
+- **project-orchestrator Skill**: Refined Caddy installation approach to host-based setup
+  - Changed from Docker-embedded or standalone host-level to direct OS installation via package manager
+  - Caddy installed directly on host via apt (Ubuntu/Debian) instead of running in Docker
+  - Rationale: avoids Docker network overhead, survives Docker daemon restarts, managed by systemd automatically
+  - Updated all Caddyfile paths to `/etc/caddy/Caddyfile`
+  - Changed reload command to `sudo systemctl reload caddy`
+  - Added detailed install commands for new Caddy installations (Cloudsmith repo setup)
+  - Updated VPS check to ask whether Caddy is "installed" (not just "running")
+
+### ✨ Added
+- **project-orchestrator Skill**: New Caddy VPS setup guide reference
+  - New `assets/caddy-vps-setup.md` with step-by-step installation instructions
+  - Covers SSH connection, apt installation, firewall setup, domain configuration
+  - Includes common troubleshooting for HTTPS, 502 errors, port conflicts
+  - Reference file can be shared with users unfamiliar with VPS operations
+
+## [0.8.22] - 2026-05-08
+
+### 🔄 Changed
+- **project-orchestrator Skill**: Added VPS Caddy existence check to deployment guidance
+  - During Step 9 (Deployment), now asks whether Caddy is already running on the VPS
+  - If Yes: skip Caddy install, just add domain block to existing Caddyfile and run `caddy reload`
+  - If No: include full Caddy install and setup in recommended next steps
+  - Updated final plan summary to reflect appropriate Caddy setup based on existing infrastructure
+
 ## [0.8.21] - 2026-05-08
 
 ### 🔄 Changed

package/dist/cli/index.js

@@ -16,7 +16,7 @@ const program = new Command();
 program
     .name('prompter')
     .description('Enhance prompts directly in your AI coding workflow')
-    .version('0.8.21');
+    .version('0.8.23');
 program
     .command('init')
     .description('Initialize Prompter in your project')

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@dedesfr/prompter",
-    "version": "0.8.21",
+    "version": "0.8.23",
     "description": "Enhance prompts directly in your AI coding workflow",
     "type": "module",
     "main": "dist/index.js",

package/skills/project-orchestrator/SKILL.md

@@ -305,13 +305,13 @@ When Docker is used and a web server or reverse proxy is needed (e.g., for Larav
 - For local development, Caddy serves HTTP by default -- no certificate setup needed.
 - Mention Caddy in the final plan summary under the Docker/web server row and in the recommended next steps.
 
-**Always use a standalone host-level Caddy** -- do NOT embed Caddy inside a project's `docker-compose.yml`. Even for a single project today, users commonly add more projects later, and a per-project Caddy would conflict on ports 80/443.
+**Always install Caddy directly on the host** (via the OS package manager) -- do NOT run Caddy inside Docker. Running Caddy on the host avoids Docker network overhead, survives Docker daemon restarts, and is managed by systemd automatically. Do NOT embed Caddy in any project's `docker-compose.yml`.
 
 The correct setup:
 
-1. **One standalone Caddy on the host** (installed directly or in its own `docker-compose.yml` folder) owns ports 80/443 and terminates TLS for all domains.
+1. **Caddy installed on the host** via `apt install caddy` (Ubuntu/Debian) or equivalent. Systemd manages it -- starts on boot, restarts on failure.
 2. **Each project exposes only an internal port** (e.g., `3001`, `3002`) -- no `ports: - "80:80"` in their `docker-compose.yml`.
-3. The host Caddyfile routes by domain:
+3. The host Caddyfile (`/etc/caddy/Caddyfile`) routes by domain:
 
 ```caddy
 project-a.com {
@@ -323,7 +323,20 @@ project-b.com {
 }
 ```
 
-Include this setup in the final plan summary and recommended next steps.
+4. After editing the Caddyfile, reload with `sudo systemctl reload caddy`.
+
+During Step 9 (Deployment), ask whether Caddy is already installed on the VPS:
+
+- **Yes** -- skip installing Caddy. Just add a new block to `/etc/caddy/Caddyfile` for the new domain, then run `sudo systemctl reload caddy`. Include only this step in the recommended next steps.
+- **No** -- include the full Caddy install in the recommended next steps:
+  ```bash
+  sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl
+  curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
+  curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
+  sudo apt update && sudo apt install caddy
+  ```
+
+Include the appropriate Caddy setup in the final plan summary and recommended next steps.
 
 ### Laravel + Docker Guidelines
 
@@ -471,3 +484,4 @@ If the user agrees, read `prompter/core/proposal.md` and `prompter/AGENTS.md` an
 ## Resources
 
 - **Plan summary template**: [plan-summary-template.md](assets/plan-summary-template.md) -- Structured output format for the final verified plan
+- **Caddy VPS setup guide**: [caddy-vps-setup.md](assets/caddy-vps-setup.md) -- Step-by-step guide for installing and managing Caddy on a VPS (share this with users who are unfamiliar with VPS operations)

package/skills/project-orchestrator/assets/caddy-vps-setup.md

@@ -0,0 +1,180 @@
+# Caddy Setup on a VPS (Step-by-Step)
+
+This guide walks you through installing and managing Caddy as a reverse proxy on a Ubuntu/Debian VPS. Caddy automatically handles HTTPS for all your domains — no manual SSL certificate setup needed.
+
+---
+
+## Prerequisites
+
+Before starting, make sure:
+
+1. You have a VPS running **Ubuntu 22.04 or Debian 12** (or newer).
+2. You have SSH access to the VPS as a user with `sudo` privileges.
+3. Your domain's **A record points to your VPS IP address** (set this in your domain registrar's DNS panel). DNS changes can take up to 30 minutes to propagate.
+
+---
+
+## Step 1: Connect to Your VPS
+
+Open a terminal and connect via SSH:
+
+```bash
+ssh your-user@your-vps-ip
+```
+
+---
+
+## Step 2: Install Caddy
+
+Run these commands one by one:
+
+```bash
+sudo apt install -y debian-keyring debian-archive-keyring apt-transport-https curl
+
+curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' \
+  | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
+
+curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' \
+  | sudo tee /etc/apt/sources.list.d/caddy-stable.list
+
+sudo apt update && sudo apt install caddy
+```
+
+Verify the install:
+
+```bash
+caddy version
+```
+
+You should see a version number like `v2.x.x`.
+
+---
+
+## Step 3: Check That Caddy Is Running
+
+Caddy starts automatically after install. Confirm it's active:
+
+```bash
+sudo systemctl status caddy
+```
+
+Look for `Active: active (running)`. If it's not running, start it:
+
+```bash
+sudo systemctl start caddy
+sudo systemctl enable caddy   # make it start on boot
+```
+
+---
+
+## Step 4: Open Firewall Ports
+
+Allow HTTP and HTTPS traffic:
+
+```bash
+sudo ufw allow 80
+sudo ufw allow 443
+sudo ufw allow 22    # keep SSH open
+sudo ufw enable
+sudo ufw status
+```
+
+---
+
+## Step 5: Configure Your First Domain
+
+The Caddy config file lives at `/etc/caddy/Caddyfile`. Open it:
+
+```bash
+sudo nano /etc/caddy/Caddyfile
+```
+
+Replace the default content with:
+
+```caddy
+your-domain.com {
+    reverse_proxy localhost:3001
+}
+```
+
+> Replace `your-domain.com` with your actual domain, and `3001` with the port your app is running on.
+
+Save and close: press `Ctrl+X`, then `Y`, then `Enter`.
+
+---
+
+## Step 6: Reload Caddy
+
+Apply the new config without downtime:
+
+```bash
+sudo systemctl reload caddy
+```
+
+Caddy will automatically obtain an SSL certificate for your domain. Visit `https://your-domain.com` — it should work with HTTPS out of the box.
+
+---
+
+## Adding a New Project Later
+
+When you deploy a new project on the same VPS, just add a new block to the Caddyfile:
+
+```bash
+sudo nano /etc/caddy/Caddyfile
+```
+
+Add below the existing block:
+
+```caddy
+your-domain.com {
+    reverse_proxy localhost:3001
+}
+
+another-project.com {
+    reverse_proxy localhost:3002
+}
+```
+
+Then reload:
+
+```bash
+sudo systemctl reload caddy
+```
+
+Each project gets its own SSL certificate automatically.
+
+---
+
+## Common Commands
+
+| Task | Command |
+|------|---------|
+| Check Caddy status | `sudo systemctl status caddy` |
+| Reload after config change | `sudo systemctl reload caddy` |
+| Restart Caddy | `sudo systemctl restart caddy` |
+| View live logs | `sudo journalctl -u caddy -f` |
+| Validate config before reload | `caddy validate --config /etc/caddy/Caddyfile` |
+| View current config | `cat /etc/caddy/Caddyfile` |
+
+---
+
+## Troubleshooting
+
+**HTTPS not working / certificate error**
+- Check that your domain's A record points to the VPS IP: `dig your-domain.com`
+- Make sure ports 80 and 443 are open: `sudo ufw status`
+- Check Caddy logs for errors: `sudo journalctl -u caddy -f`
+
+**502 Bad Gateway**
+- Your app is not running or not listening on the expected port.
+- Check that your Docker containers are up: `docker compose ps`
+- Verify the port in your Caddyfile matches the port your app exposes.
+
+**Port already in use**
+- Another process (e.g., Apache or Nginx) may be using port 80/443.
+- Check: `sudo ss -tlnp | grep -E ':80|:443'`
+- Stop the conflicting service: `sudo systemctl stop nginx` or `sudo systemctl stop apache2`
+
+**Config change not taking effect**
+- Always run `sudo systemctl reload caddy` after editing the Caddyfile.
+- Validate first to catch syntax errors: `caddy validate --config /etc/caddy/Caddyfile`

package/src/cli/index.ts

@@ -18,7 +18,7 @@ const program = new Command();
 program
   .name('prompter')
   .description('Enhance prompts directly in your AI coding workflow')
-  .version('0.8.21');
+  .version('0.8.23');
 
 program
   .command('init')