Skip to main content

Module artifact

Module artifact 

Source
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§

ArtifactManifest
Everything under a directory that should be published.
HttpsArtifactTransport
Uploads a directory as an artifact deployment and waits for it to go live.
ManifestFile
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 .gitignore and .smbignore found inside it (not in parent directories), always skipping .git and .smb, and refusing symlinks and special files. Entries are sorted by path so the manifest is stable.