We should have a way to set at least the S3 credentials, bucket name and initial path prefix using the querystring and/or data- attributes on the top-level bagger element so this can be integrated into workflows where those values are known (but not secret) and where things like access keys may be ACLed to require uploads to certain paths.
We should have a way to set at least the S3 credentials, bucket name and initial path prefix using the querystring and/or
data-attributes on the top-level bagger element so this can be integrated into workflows where those values are known (but not secret) and where things like access keys may be ACLed to require uploads to certain paths.