fix: address PR review threads and add regressions

Author: flyingrobots

.github/workflows/ci.yml

@@ -27,6 +27,12 @@ jobs:
       - name: Verify Dependency Integrity (Post-Install)
         run: npm run check:deps
 
+      - name: Configure Git User
+        run: |
+          git config --global user.email "ci@git-cms.local"
+          git config --global user.name "CI Bot"
+          git config --global init.defaultBranch main
+
       - name: Run Local Integration Tests
         run: npm run test:local
 

.github/workflows/test-setup.yml

@@ -21,14 +21,14 @@ jobs:
 
     steps:
       - name: Checkout code
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Run BATS tests
         run: npm run test:setup
 
       - name: Upload test results
         if: always()
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: bats-test-results
           path: test-results/

.gitignore

@@ -9,7 +9,17 @@ git-cms-test-*/
 .obsidian/
 
 # LaTeX artifacts
-*.aux 
+*.aux
 *.log
 *.out
 *.toc
+*.synctex.gz
+*.fls
+*.fdb_latexmk
+*.bbl
+*.blg
+*.idx
+*.ind
+*.ilg
+*.lof
+*.lot

Dockerfile

@@ -3,11 +3,12 @@
 # Base stage
 FROM node:22-slim AS base
 ENV NODE_ENV=production
-RUN apt-get update && apt-get install -y git python3 make g++ && rm -rf /var/lib/apt/lists/*
+RUN apt-get update && apt-get install -y --no-install-recommends git && rm -rf /var/lib/apt/lists/*
 WORKDIR /app
 
 # Deps stage
 FROM base AS deps
+RUN apt-get update && apt-get install -y --no-install-recommends python3 make g++ && rm -rf /var/lib/apt/lists/*
 COPY package.json package-lock.json* ./
 RUN npm ci --include=dev
 
@@ -16,17 +17,17 @@ FROM base AS dev
 ENV NODE_ENV=development
 COPY --from=deps /app/node_modules ./node_modules
 COPY . .
-RUN git config --global user.email "dev@git-cms.local"
-RUN git config --global user.name "Git CMS Dev"
-RUN git config --global init.defaultBranch main
+RUN git config --global user.email "dev@git-cms.local" \
+ && git config --global user.name "Git CMS Dev" \
+ && git config --global init.defaultBranch main
 CMD ["npm", "run", "serve"]
 
 # Test stage
 FROM base AS test
 ENV NODE_ENV=test
 COPY --from=deps /app/node_modules ./node_modules
 COPY . .
-RUN git config --global user.email "bot@git-cms.local"
-RUN git config --global user.name "Git CMS Bot"
-RUN git config --global init.defaultBranch main
+RUN git config --global user.email "bot@git-cms.local" \
+ && git config --global user.name "Git CMS Bot" \
+ && git config --global init.defaultBranch main
 CMD ["npm", "run", "test:local"]

GETTING_STARTED.md

@@ -1,111 +1,73 @@
 # Getting Started with Git CMS
 
-Welcome to **Git CMS**! This tool allows you to write and manage blog posts using Git—the same technology developers use to track code—but with a simple interface that works like a regular app.
-
-Follow these steps to get up and running.
+This quick guide is the lightweight entry point. For the full walkthrough, use [`docs/GETTING_STARTED.md`](docs/GETTING_STARTED.md).
 
 ---
 
-## 1. Prerequisites
-
-Before you start, you need two things installed on your computer:
+## Prerequisites
 
-1.  **Git**: [Download and install Git here](https://git-scm.com/downloads). (Choose the default options during installation).
-2.  **Node.js**: [Download and install Node.js here](https://nodejs.org/). (Choose the "LTS" version).
+- Git
+- Node.js 22+
+- Docker Desktop (recommended for safe testing)
 
 ---
 
-## 2. Installation
-
-You can install Git CMS directly on your computer or run it using **Docker**.
-
-### Option A: Direct Installation
-1.  Open your **Terminal** (on Mac/Linux) or **Command Prompt/PowerShell** (on Windows).
-2.  Type the following commands one by one:
-    ```bash
-    # Download the tool
-    git clone https://github.com/clduab11/git-cms.git
-    
-    # Enter the folder
-    cd git-cms
-    
-    # Install the helper files
-    npm install
-    
-    # Make the 'git-cms' command available everywhere on your computer
-    npm link
-    ```
-
-### Option B: Using Docker (Recommended for isolation)
-If you have [Docker Desktop](https://www.docker.com/products/docker-desktop/) installed, you can run the CMS without installing Node.js:
-1.  Download the tool: `git clone https://github.com/clduab11/git-cms.git`
-2.  Enter the folder: `cd git-cms`
-3.  Run with Docker: `docker compose up app`
-    *Note: By default, this will save posts inside the `git-cms` folder. See Section 3 to change this.*
+## Installation
 
----
+### Option A: Local CLI Install
 
-## 3. Setting Up Your "Content Home"
+```bash
+git clone https://github.com/flyingrobots/git-cms.git
+cd git-cms
+npm install
+npm link
+```
 
-Git CMS doesn't save your posts inside the tool itself; it saves them in a "Repository" (a special folder) of your choice.
+### Option B: Docker (Recommended)
 
-1.  Create a new folder for your blog posts (e.g., `my-awesome-blog`).
-2.  Enter that folder in your terminal and "initialize" it:
-    ```bash
-    mkdir my-awesome-blog
-    cd my-awesome-blog
-    git init
-    ```
-3.  **Crucial Step**: Tell Git CMS to use this folder. You do this by setting an "Environment Variable" named `GIT_CMS_REPO` to the path of this folder.
-    *   **Mac/Linux**: `export GIT_CMS_REPO=/Users/yourname/my-awesome-blog`
-    *   **Windows**: `$env:GIT_CMS_REPO="C:\Users\yourname\my-awesome-blog"`
+```bash
+git clone https://github.com/flyingrobots/git-cms.git
+cd git-cms
+npm run setup
+npm run dev
+```
 
----
+Open the UI at [http://localhost:4638/](http://localhost:4638/).
 
-## 4. Running the CMS
+---
 
-Now you are ready to start the interface!
+## First Article
 
-1.  In your terminal, type:
-    ```bash
-    git-cms serve
-    ```
-2.  You will see a message: `[git-cms] Admin UI: http://localhost:4638/`
-3.  Open your web browser (Chrome, Safari, or Edge) and go to **http://localhost:4638/**.
+1. Click `+ New Article`.
+2. Set a slug like `my-first-post`.
+3. Add title + body content.
+4. Click `Save Draft`.
+5. Click `Publish` when ready.
 
 ---
 
-## 5. Writing Your First Post
+## CLI Basics
 
-1.  Click the **+ New Article** button on the left.
-2.  **Slug**: Enter a short ID for your post (e.g., `my-first-post`). No spaces!
-3.  **Title**: Enter the title of your article.
-4.  **Content**: Type your post in the large box. You can use [Markdown](https://www.markdownguide.org/basic-syntax/) to add formatting like **bold** or *italics*.
-5.  Click **Save Draft**.
+```bash
+# Draft reads content from stdin
+echo "# Hello" | git cms draft hello-world "Hello World"
 
-### To Make it Public:
-When you are happy with your post, click the **Publish** button. This marks the post as "live."
+# List drafts
+git cms list
 
----
-
-## 6. Managing Images and Files
+# Publish
+git cms publish hello-world
 
-You can add images to your posts easily:
-1.  In the editor, click the **Attach File** button at the bottom.
-2.  Select an image from your computer.
-3.  Git CMS will "chunk" the image, store it safely in Git, and automatically add the code to your post so the image shows up.
+# Show article
+git cms show hello-world
+```
 
 ---
 
-## 7. Advanced: CLI Power (Optional)
+## Safety Notes
 
-If you prefer using the terminal instead of the web browser, you can use these commands:
-*   `git-cms list`: See all your drafts.
-*   `git-cms show <slug>`: Read a post in the terminal.
-*   `git-cms publish <slug>`: Publish a draft.
-
----
+- Prefer Docker workflows while learning.
+- Use a dedicated test repository for local CLI experimentation.
+- Avoid running low-level Git plumbing in repositories you care about.
 
-### Troubleshooting
-*   **"Command not found"**: Ensure you ran `npm link` in the `git-cms` folder.
-*   **"Not a git repository"**: Ensure you ran `git init` inside your content folder and that your `GIT_CMS_REPO` path is correct.
+See [`TESTING_GUIDE.md`](TESTING_GUIDE.md) for safety and cleanup procedures.