Regalamiunsorriso/sync/www-deploy-manifest.md

47 lines
No EOL
1.6 KiB
Markdown

# WWW Deployment Manifest
This document lists the files under `www/` in the current FaceAI feature-flag rollout that should be copied to the remote staging path:
`/home/marco/regalamiunsorriso/incoming/www`
## Deployment Set
All files in this rollout are deployed from the current working tree.
## New Files
- None in this rollout.
## Updated Files
- `www/_js/rus-ecom-240621.js`
- `www/faceai_config.php`
- `www/faceai_handoff.php`
- `www/faceai_simulator_view.php`
- `www/fotoCR-en.jsp`
- `www/fotoCR.jsp`
## Remote Copy Target
- Source root: `K:\various\regalamiunsorriso`
- Remote host: `marco@83.149.164.4:410`
- Remote staging path: `/home/marco/regalamiunsorriso/incoming/www`
- Remote live path: `/home/sites/regalamiunsorriso/www`
- Total files in this manifest: `6`
## Transfer Method
- Stage by streaming a tar archive over SSH and extracting it into `/home/marco/regalamiunsorriso/incoming` so the `www/...` directory structure is preserved.
- Promote with `/home/marco/promote-file.sh` through `sudo tcsh` so the live destination keeps its required owner, group, and mode.
## Verification Expectations
- Verify staged files with `ls -l` and `cksum`.
- Verify live files with `ls -l`, `stat -f`, and `cksum`.
- Existing destination files should retain their original metadata after promotion.
## Known Shell Quirks
- The remote login shell behaves as `tcsh`, so POSIX shell loops fail unless run through `sh -c`.
- The server `sh` does not support `-l`, so use `sh -c`, not `sh -lc`.
- Direct SSH plus tar works reliably on this host; MCP SSH was previously unreliable and is avoided.