docs(zdeploy): stop naming the server's web root in a comment (#95)
Some checks failed
tests / test (push) Has been cancelled

* docs(zdeploy): describe the landing layout without naming the server's web root

A comment in the static-site deploy path named the landing container's
real web root. It now says the container serves each host from its own
directory, which is all the comment needs. Comment only; no behaviour
change. Ported by hand from evo.scripts#196, since this file is
hand-maintained in the mirror.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(checksums): record zdeploy.ps1's new hash

The comment change in the previous commit changed the file, so
CHECKSUMS.txt is regenerated with zchecksums -Update, as the suite requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kelly Michels 2026-09-30 15:34:52 -05:00 committed by GitHub
parent 57edc629c1
commit 5bc77f2de1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions

View File

@ -8,7 +8,7 @@ b407ef5b298cd6fe94af492e9254b4447e34333d22f8c29d3e9d4d2881651cf3 zbackup_ec2.cm
64bc3148b09e422ffe4890339fade2354a31f2c7ba004f2728c29a0a39c32f08 zchecksums.cmd
3e1c573e446238cae494d22d25376f278333dc25fdbc0a5abbdaa9349722b438 zchecksums.ps1
049f8e79fc8c3d8d96ae8ccb1155d191e2dbf2753f4d4d73ceca00aa1ab0481b zdeploy.cmd
e87c9fcd494fd2b8399b14c18a1dfa72805e5c52a38f132591b4d523b8806631 zdeploy.ps1
d2ead96436507c8efedc3c72045e623137a1f844940c4ff57c9c7ebe67645511 zdeploy.ps1
30918a9260cb6220d6e2140edcf319fc0fa1e75b7fe36d0efe68b0d10cdde241 zec2.cmd
695ec87ea6518933ee64524d369f1d0d5128bf6e54db31f555a888bdddcb9326 zec2.ps1
ce3209ed8eaab242286e76aeb11b1249239e2804e3de456a1609cc7caa780b43 zec2_rotatekeys.cmd

View File

@ -1176,8 +1176,8 @@ function Invoke-StaticDeploy {
param([string]$Key, $Proj)
# Plain static sites - no build, no container of their own. The landing
# container serves them straight off disk out of /srv/$host, so shipping
# the files IS the deploy: there is nothing to restart afterwards.
# container serves them straight off disk, one directory per host, so
# shipping the files IS the deploy: there is nothing to restart afterwards.
$root = Join-Path $Proj.localRoot $Proj.siteDir
$remotePath = $Proj.remote.path