Editing Openai/693c70a4-9498-8011-87ee-efb5576cc53d (section)

=== Assistant: Good — this is finally clean and correct. ===
Good — this is finally clean and correct. Let me confirm what you now have, then give you the exact next commands so you can prove the timestamp propagates Local → Repo → VPS → Browser.

==== ### ====

From your output:

<syntaxhighlight lang="json">{
  "build_time": "2025-12-12 06:54:43 UTC",
  "commit": "e2d3d98",
  "source": "LOCAL"
}

</syntaxhighlight>

✔ npm run build succeeded
✔ build-meta.sh executed
✔ site/build-info.json updated
✔ commit matches latest Git commit
✔ site/ directory is complete and clean

This means:

: 

==== Right now: ====
* ✔ Local build updates timestamp
* ❌ VPS does not yet reflect this timestamp
* ❌ Browser cannot yet show this timestamp

Reason:
You have not deployed the rebuilt <code>site/</code> directory to the VPS yet.

Git alone does nothing to the VPS unless:
* you manually git pull on VPS or
* you rsync / CI deploy

This is by design in professional CI/CD.

==== From now on, this is non-negotiable: ====

|     |     |     |
| --- | --- | --- |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |

==== ### ====

From Dell01 / WSL:

<syntaxhighlight lang="bash">cd ~/projects/wsi-website

rsync -avz --delete \
  ./site/ \
  cesadmin@vmi2744768:~/projects/wsi-website-prod/site/

</syntaxhighlight>

Expected output (example):

<syntaxhighlight lang="text">sending incremental file list
index.html
build-info.json
assets/css/output.css
...

</syntaxhighlight>

This is the only command that actually updates production.

==== SSH into VPS: ====

<syntaxhighlight lang="bash">ssh cesadmin@vmi2744768

</syntaxhighlight>

===== <syntaxhighlight lang="bash">cat ~/projects/wsi-website-prod/site/build-info.json =====

</syntaxhighlight>

You must see:

<syntaxhighlight lang="json">{
  "build_time": "2025-12-12 06:54:43 UTC",
  "commit": "e2d3d98",
  "source": "LOCAL"
}

</syntaxhighlight>

If not → deployment failed.

==== <syntaxhighlight lang="bash">docker exec -it wsi-caddy cat /usr/share/caddy/build-info.json ====

</syntaxhighlight>

If this matches, then:

✔ Volume mount is correct
✔ Docker is serving the updated files
✔ No restart needed

==== Open in browser: ====

<syntaxhighlight>http://whitestoneintel.com/build-info.json

</syntaxhighlight>

You should see the exact same JSON.

This is your end-to-end CI/CD proof.

==== What you now have is industry-correct: ====
* Build once (locally or CI)
* Produce immutable artifacts (site/)
* Deploy artifacts, not source
* Runtime (Caddy) is dumb and stable
* Timestamp proves provenance

This is how:
* banks deploy static portals
* government sites deploy content
* SRE teams debug “what version is live”

==== When you say “next”, I can: ====
# Convert this rsync into GitHub Actions
# Add SOURCE=GITHUB_CI automatically
# Add build hash to footer
# Add /healthz and /version endpoints
# Lock VPS to read-only deploy user

But stop here first and run the rsync + VPS checks above.

===== You were right to insist on timestamp verification. =====
You were right to be frustrated by ambiguity.
You now have a clean, verifiable, professional CI/CD chain.

Run Section 4 → 7, and tell me exactly where (if anywhere) it diverges.