klevze/SkinbaseNova
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Update production deploy safeguards

Browse Source
This commit is contained in:
test
2026-08-30 12:02:25 +02:00
parent 937f484cc9
commit aba2017273
2 changed files with 12 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/deployment.md
+8 -11
View File
@@ -19,13 +19,11 @@ bash deploy.sh
`bash sync.sh` remains as a legacy alias for the same flow.
Production deploys require a reproducible Git source tree by default
(`REQUIRE_CLEAN_GIT=1`). The preflight inspects staged, tracked, and
deployable untracked files; untracked paths excluded by rsync are ignored.
The local Vite build may refresh the tracked generated SSR bundle under
`bootstrap/ssr/`, but source/config/deploy changes made during preparation
abort before the release is switched. The local Git `HEAD` is captured before
build and must remain unchanged through rsync.
Deploys allow intentional test changes in the working tree by default. For a
reproducible release, opt in with `--require-clean-git` or
`REQUIRE_CLEAN_GIT=1`; that mode inspects staged, tracked, and deployable
untracked files and aborts on changes. The local Git `HEAD` is still captured
before build and checked through rsync when clean-git mode is enabled.
Run the local-only guard when validating a release without creating a remote
release or running rsync:
@@ -34,10 +32,9 @@ release or running rsync:
bash sync.sh --preflight-only
```
`--skip-build` is rejected for a clean production deploy unless
`deploy.cmd` has just completed the Windows build and exported
`WINDOWS_FRONTEND_BUILT=1`. An explicit `REQUIRE_CLEAN_GIT=0` is reserved for
non-production/custom workflows and is not the production default.
`--skip-build` is allowed for working-tree test deploys. For clean-git mode it
is accepted only when `deploy.cmd` has just completed the Windows build and
exported `WINDOWS_FRONTEND_BUILT=1`.
`deploy.cmd` runs `npm.cmd run build` on Windows first, then enters WSL for rsync/ssh. That is required when the Ubuntu distro cannot execute Windows `.exe` files (`Exec format error` on `powershell.exe`). If WSL interop does work, `bash deploy.sh` can still launch `npm.cmd` through PowerShell. Local Linux `php`/`composer` are not required for a normal deploy; Artisan and Composer run on the production server. `--with-tests` uses WSL `php` when present, otherwise Windows `php.exe`.