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

=== # ===

Location:

<syntaxhighlight>~/projects/wsi-website

</syntaxhighlight>

===== <syntaxhighlight>wsi-website/ =====
├── src/                 ← Your editable source (✔ CORRECT)
│   ├── index.html
│   ├── en/
│   ├── zh/
│   └── assets/
│        └── css/tailwind.css
├── site/                ← Auto-generated output (✔ CORRECT)
│   └── build-info.json  ← build-meta.sh writes this
├── tailwind.config.js
├── build-meta.sh
├── package.json
└── .github/workflows/
    ├── deploy-website.yml  ← NEW WEBSITE CI/CD
    └── deploy-mkdocs.yml   ← OLD DOCS CI/CD

</syntaxhighlight>

===== 1. npm run build ✔ builds Tailwind ✔ writes metadata to site/build-info.json ✔ regenerates site/ cleanly =====
# Local Git repo is valid: ``<code> git remote -v origin github.com:kce2ces/wsi-website.git <syntaxhighlight>3. Pushed successfully to main ✔ commit e2d3d98 (“Restructure project”)

Conclusion: LOCAL SIDE = PERFECT

=== # ===

Repository:
github.com<ref>{{cite web|title=github.com|url=https://github.com/kce2ces/wsi-website|publisher=github.com|access-date=2025-12-20}}</ref>

Contains:

✔ Clean source (src/)
✔ Clean build (site/)
✔ CI/CD workflows (deploy-website.yml)
✔ No broken files
✔ No duplicated folders

Deployment key setup:
* You generated key: /home/kce2ces/.ssh/github-deploy
* You added public key to the VPS
* You will add the private key into repo secrets as DEPLOY_KEY

Conclusion: GITHUB SIDE = READY

=== # ===

Workflow file (correct):

</syntaxhighlight>
.github/workflows/deploy-website.yml

<syntaxhighlight>
What it does:
# Runs on push to main
# Installs Node + dependencies
# Runs npm run build
# Uploads site/* to VPS folder
# Restarts Caddy container

===== |     |     |     | =====
| --- | --- | --- |
|     |     |     |
|     |     |     |
|     |     |     |
|     |     |     |

You must create them under:
GitHub → Settings → Secrets → Actions

Conclusion: CI/CD WORKFLOW = CORRECT

(Just add the 4 secrets.)

=== # ===

Your final production directory is:

</syntaxhighlight>
~/projects/wsi-website-prod

<syntaxhighlight>
Contents:

</syntaxhighlight>
Caddyfile
docker-compose.yml
site/

<syntaxhighlight>
This is correct, clean, and ready.

The Caddy root used inside container:

</syntaxhighlight>
/usr/share/caddy

<syntaxhighlight>
Your docker-compose.yml binds:

</syntaxhighlight>
./site:/usr/share/caddy

<syntaxhighlight>
Perfect.

Conclusion: VPS FOLDER = PERFECT

=== # ===

===== </syntaxhighlight> =====
wsi-caddy

<syntaxhighlight>
Running with:

</syntaxhighlight>
expose:
* "80"

<syntaxhighlight>
On network:

</syntaxhighlight>
npm-net

<syntaxhighlight>
Because Nginx Proxy Manager is reverse proxying TLS on ports 80/443.

Your Caddyfile (correct):

</syntaxhighlight>
{
    auto_https off
}

http://whitestoneintel.com {
    root * /usr/share/caddy
    file_server
}

http://www.whitestoneintel.com {
    redir http://whitestoneintel.com{uri}
}

http://wsi.whitestoneintel.com {
    root * /usr/share/caddy
    file_server
}

<syntaxhighlight>
Conclusion: CADDY CONFIG = PERFECT FOR NPM SETUP

=== # ===

===== </syntaxhighlight> =====
LOCAL → GIT → CI/CD BUILD → SCP UPLOAD → VPS → CADDY → HTTPS → USER

</code>``

===== 1. You edit any file in src/ on your local =====
# You run npm run build or let CI/CD run it for you
# git push
# GitHub Actions builds Tailwind
# GitHub Actions uploads site/* to VPS
# GitHub restarts wsi-caddy
# Within 2–3 seconds → whitestoneintel.com shows the update
# Footer contains the timestamp + commit ID

Everything is now aligned.