Expand description
Static deploy over HTTPS: build a manifest from a directory, then upload it.
The client builds, hashes the output and uploads blobs the server does not have yet, using only an app-scoped deploy token. The server picks the target and publishes it; nothing here names a remote path or runs a command on the box.
Structs§
- Artifact
Manifest - Everything under a directory that should be published.
- Https
Artifact Transport - Uploads a directory as an artifact deployment and waits for it to go live.
- Manifest
File - A file to ship: its manifest entry plus where to read it from.
Constants§
- MAX_
FILES - Server-side quotas, checked here too so a refusal is local and early.
- MAX_
FILE_ BYTES - MAX_
TOTAL_ BYTES
Functions§
- build_
manifest - Walks
root, honouring.gitignoreand.smbignorefound inside it (not in parent directories), always skipping.gitand.smb, and refusing symlinks and special files. Entries are sorted by path so the manifest is stable.