Fetch/store a pinSource:
These are low-level functions that power
pin_download(). They are needed primarily for folks
developing new board types, and should not generally be called directly.
pin_fetch(board, name, version = NULL, ...) pin_store(board, name, paths, metadata, versioned = NULL, x = NULL, ...)
Retrieve a specific version of a pin. Use
pin_versions()to find out which versions are available and when they were created.
Additional arguments passed on to methods for a specific board.
A character vector of file paths to upload to
A list containing additional metadata to store with the pin. When retrieving the pin, this will be stored in the
userkey, to avoid potential clashes with the metadata that pins itself uses.
Should the pin be versioned? The default,
NULL, will use the default for
An object (typically a data frame) to pin.
pin_fetch() is called primarily for its side-effect of downloading
remote pins into the local cache. It returns the same data as pin_meta.
pin_store() is called for its side-effect of uploading a local file
to a remote board. It invisibly returns the fully qualified pin name.
board <- board_temp() board %>% pin_upload(system.file("CITATION")) #> Guessing `name = 'CITATION'` #> Creating new version '20220924T171552Z-dec01' path <- board %>% pin_download("CITATION") path #>  "/tmp/Rtmpx9Qigs/pins-3c5a68da7a80/CITATION/20220924T171552Z-dec01/CITATION" readLines(path)[1:5] #>  "bibentry(\"Manual\"," #>  " title = \"R: A Language and Environment for Statistical Computing\"," #>  " author = person(\"R Core Team\")," #>  " organization = \"R Foundation for Statistical Computing\"," #>  " address = \"Vienna, Austria\","