Repository navigation
README docs for GCS has piping instead of using upload/download? #668
Copy link
Copy link
Closed
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
Description
Activity
- addedapi: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
on Jun 17, 2015 The point of showing the piping is to say "Look how Node we are!" By showing we use regular read/write streams lets developers see how they can integrate it with other libraries/architectures they may already be using.
Got it... Can we add the upload/download pieces though also? Maybe put them first, then also have the piping example?
Seems like people aren't discovering those methods like they should be.
Definitely. Good idea!
- added a commit that references this issue
on Sep 27, 2022 - added a commit that references this issue
on Jan 24, 2023 11 remaining items
- added a commit that references this issue
on Jan 28, 2026 - added a commit that references this issue
on Feb 2, 2026 - added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Mar 17, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
Metadata
Metadata
Assignees
Labels
api: storageIssues related to the Cloud Storage API.Issues related to the Cloud Storage API.
Seems liek this should use
bucket.uploadandfile.downloadright ?