The root directory to upload to remote storage. (default: current
directory). Paths in the printed manifest will be relative to this.
A glob matching files in
--root that should be uploaded and thrown
in the manifest. (default: all files in all subdirectories).
A prefix to the key used on the remote storage instance. This can be
something pathlike with
/ indicating a directory, but note that it
is just a prefix prepended to the front of the relative paths found in
--glob, so you’ll have to add a trailing slash
if you want this to be a containing directory. (default:
The storage bucket to upload to. For DigitalOcean Spaces, this is just
the name of the directory in that space’s top-level directory.
Upload this file privately, leaving no public link. You probably don’t
want to do this unless you’re just dumping data onto a storage space to
deal with later.
If specified, then the relative path of files from
become part of their key on the remote object store, sandwiched between
--prefix and the file’s sha256sum. Use this if you are manually
uploading something to the object store that you want to keep track of
outside of source-code, e.g. one-off build artifacts and the like. You
should AVOID using this flag if you’re just interested in throwing
files in an object store and organizing them with the returned manifest
in a version-controlled way, since objects are by default only named
after their hash. This lets you use the manifest to specify where files
go on the filesystem without duplicating files on the remote object