Update image manifest (1 images)

README.md

@@ -6,20 +6,21 @@ clipboard when you click it. Built to be dropped onto an nginx server as plain
 static files.
 
 ```
-index.html                     the page
-assets/styles.css              styling (auto light/dark)
-assets/app.js                  search, rendering, clipboard logic
-scripts/generate-manifest.mjs  scans img/ -> images.json
-images.json                    generated manifest the page fetches
-img/                           put your images here
+index.html              the page
+assets/styles.css       styling (auto light/dark)
+assets/app.js           search, rendering, clipboard logic
+generate-manifest.py    scans img/ -> images.json, then commits
+pushAll                 regenerate + commit + push, in one command
+images.json             generated manifest the page fetches
+img/                    put your images here
 ```
 
 ## Why a manifest?
 
 A browser cannot list a directory on its own, and "no backend" rules out an API
 that would do it. So the file list is produced by a tiny build step:
-`scripts/generate-manifest.mjs` walks `img/` and writes `images.json`. The page
-fetches that file at runtime. Everything the server does is serve static files.
+`generate-manifest.py` walks `img/` and writes `images.json`. The page fetches
+that file at runtime. Everything the server does is serve static files.
 
 ## Quick start
 
@@ -27,8 +28,8 @@ fetches that file at runtime. Everything the server does is serve static files.
 # 1. Add images (subfolders are fine)
 cp ~/pictures/*.png img/
 
-# 2. Build the manifest
-node scripts/generate-manifest.mjs
+# 2. Build the manifest (and commit it)
+./generate-manifest.py
 
 # 3. Preview locally
 python3 -m http.server 8080
@@ -37,6 +38,32 @@ python3 -m http.server 8080
 
 Re-run step 2 whenever you add, rename, or delete images.
 
+## Publishing with `pushAll`
+
+`pushAll` does the whole publish flow in one command: regenerate the manifest,
+commit the changes, and push to the remote.
+
+```sh
+./pushAll
+```
+
+To run it as `pushAll` from anywhere, either add this folder to your `PATH`, or
+create a git alias once:
+
+```sh
+git config alias.pushAll '!./pushAll'
+# then:
+git pushAll
+```
+
+### `generate-manifest.py` options
+
+```sh
+./generate-manifest.py                 # generate + commit
+./generate-manifest.py --no-commit     # generate only
+./generate-manifest.py -m "Add logos"  # custom commit message
+```
+
 ## Features
 
 - **Search** — case-insensitive, multi-word with AND semantics. Every word must
@@ -54,13 +81,13 @@ and point a server block at it. See [`nginx.conf.example`](nginx.conf.example).
 
 ```sh
 # build the manifest locally, then upload everything
-node scripts/generate-manifest.mjs
+./generate-manifest.py --no-commit
 rsync -av --delete ./ user@server:/var/www/image-library/
 ```
 
-If you'd rather generate the manifest on the server, install Node there and run
-the script after uploading images. Node is only needed for that step — nginx
-never runs it.
+If you'd rather generate the manifest on the server, install Python 3 there and
+run the script after uploading images. Python is only needed for that step —
+nginx never runs it.
 
 ### Clipboard over plain HTTP